Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/lkuczborski/CodeckInstalling this writes the configuration, not the program: `/bin/bash` has to be on your PATH already, or the server will not start.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lkuczborski/codeck/codeck-codeck-workspace)<a href="https://agentmods.dev/mcp/lkuczborski/codeck/codeck-codeck-workspace"><img src="https://agentmods.dev/badge/mcp/lkuczborski/codeck/codeck-codeck-workspace/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lkuczborski/codeck/codeck-codeck-workspace"><img src="https://agentmods.dev/badge/mcp/lkuczborski/codeck/codeck-codeck-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codeck-workspace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"codeck-workspace": {
"command": "/bin/bash",
"args": [
"./scripts/run-server.sh"
],
"cwd": "."
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 9 lines scan A 38c37df1dd45
codeck-workspace is an MCP server published in the GitHub repository lkuczborski/Codeck (39 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.
Other mcp servers, from other repositories
universal-memory
MCP server "universal-memory", hosted remotely at localhost, as configured in goldenwo/universal-memory.
tela
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki. Runs locally from the tela-mcp npm package. Needs 2 environment variables to run.
context-server
Lightweight MCP server for semantic search over organizational markdown. Runs locally from the context-server Python package.
exomem
MCP server "exomem", hosted remotely at exomem.substratesystems.io, as configured in Artexis10/exomem.
uk-tenders
MCP server "uk-tenders", hosted remotely at tenders.run.cns.me, as configured in tractorjuice/arckit-codex.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.