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-tools-pyWrote 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-tools-py/mcp-workspace)<a href="https://agentmods.dev/mcp/marcusjellinghaus/mcp-tools-py/mcp-workspace"><img src="https://agentmods.dev/badge/mcp/marcusjellinghaus/mcp-tools-py/mcp-workspace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-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 4d 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-workspace": {
"type": "stdio",
"command": "${MCP_CODER_VENV_PATH}\\mcp-workspace.exe",
"args": [
"--project-dir",
"${MCP_CODER_PROJECT_DIR}",
"--log-level",
"INFO",
"--file-size-limit",
"750",
"--reference-project",
"name=mcp_coder,path=${USERPROFILE}\\Documents\\GitHub\\mcp_coder,url=https://github.com/MarcusJellinghaus/mcp_coder",
"--reference-project",
"name=mcp-config,path=${USERPROFILE}\\Documents\\GitHub\\mcp-config,url=https://github.com/MarcusJellinghaus/mcp-config",
"--reference-project",
"name=mcp-workspace,path=${USERPROFILE}\\Documents\\GitHub\\mcp-workspace,url=https://github.com/MarcusJellinghaus/mcp-workspace",
"--reference-project",
"name=mcp-coder-utils,path=${USERPROFILE}\\Documents\\GitHub\\mcp-coder-utils,url=https://github.com/MarcusJellinghaus/mcp-coder-utils",
"--reference-project",
"name=obsidian-dev-wiki,path=${USERPROFILE}\\Documents\\GitHub\\obsidian-dev-wiki,url=https://github.com/MarcusJellinghaus/obsidian-dev-wiki"
],
"env": {
"PYTHONPATH": "${MCP_CODER_VENV_DIR}\\Lib\\"
},
"alwaysLoad": true
}
}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.
- 4d ago Changed · +2 lines 9e24a965a589
- 8d ago First seen · 26 lines scan A dac86a151946
mcp-workspace is an MCP server published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 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
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
oxylabs-mcp
Oxylabs MCP server. Runs locally from the oxylabs-mcp Python package. Needs 3 environment variables to run.
python
Structured Python tool output (ruff, mypy, pip-audit, pip-install) as typed JSON. Runs locally from the @paretools/python npm package.
intervals-icu-mcp
Model Context Protocol server for Intervals.icu — access training data, wellness metrics, and performance analysis from Claude, ChatGPT, and other LLMs. Runs locally from the intervals-icu-mcp Python package. Needs 2 environment variables to run.
d365fo-client
Microsoft Dynamics 365 Finance & Operations client and MCP server. Runs locally from the d365fo-client Python package. Needs 4 environment variables to run.
wet-mcp
Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG. Runs locally from the wet-mcp Python package. Needs 2 environment variables to run.