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/MarcusJellinghaus/mcp-workspaceWrote 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/marcusjellinghaus/mcp-workspace/mcp-tools-py)<a href="https://agentmods.dev/mcp/marcusjellinghaus/mcp-workspace/mcp-tools-py"><img src="https://agentmods.dev/badge/mcp/marcusjellinghaus/mcp-workspace/mcp-tools-py.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-tools-py 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 8d 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
{
"mcp-tools-py": {
"type": "stdio",
"command": "${MCP_CODER_VENV_PATH}\\mcp-tools-py.exe",
"args": [
"--project-dir",
"${MCP_CODER_PROJECT_DIR}",
"--python-executable",
"${MCP_CODER_VENV_PATH}\\python.exe",
"--venv-path",
"${MCP_CODER_VENV_PATH}\\..",
"--test-folder",
"tests",
"--log-level",
"DEBUG"
],
"env": {
"PYTHONPATH": "${MCP_CODER_PROJECT_DIR}/src"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 21 lines scan A dd131476f259
mcp-tools-py is an MCP server published in the GitHub repository MarcusJellinghaus/mcp-workspace (50 stars, last pushed yesterday), 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-08-30.
Other mcp servers, from other repositories
filesystem-mcp
Secure filesystem MCP server for reading, writing, searching, diffing, and patching files. Runs locally from the @j0hanz/filesystem-mcp npm package. Needs 1 environment variable to run.
ellmos-filecommander-mcp
Filesystem MCP server: files, processes, sessions, async search, OCR, archives, safe delete. Runs locally from the ellmos-filecommander-mcp npm package.
job-search-mcp
Claude searches real job boards, scores each job 0-100 for fit, and shows a ranked board. Runs locally from the @servation/job-search-mcp npm package. Needs 3 environment variables to run.
server
Stateless, internet-connected MCP server for UI/UX design inspiration, live component discovery, and modern web micro-effects. Powered by Serper. Runs locally from the @kromamcp/server npm package.
srcbridge
MCP server "srcbridge" as configured in kerwinkao/srcbridge. Runs locally from the srcbridge npm package.
pccheck-mcp
MCP server "pccheck-mcp" as configured in jjackk0k/pccheck-mcp. Runs locally from the pccheck-mcp npm package.