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/selfpatch/ros2_medkit_mcpWrote 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/selfpatch/ros2_medkit_mcp/ros2-medkit-mcp)<a href="https://agentmods.dev/mcp/selfpatch/ros2_medkit_mcp/ros2-medkit-mcp"><img src="https://agentmods.dev/badge/mcp/selfpatch/ros2_medkit_mcp/ros2-medkit-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ros2-medkit-mcp 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 7d 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
{ "ros2-medkit-mcp": { "command": "uvx", "args": [ "ros2-medkit-mcp" ] } }
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.
- 7d ago First seen · 8 lines scan A 7306424494ac
ros2-medkit-mcp is an MCP server published in the GitHub repository selfpatch/ros2_medkit_mcp (6 stars, last pushed 5d ago), licensed Apache-2.0. 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-31.
Other mcp servers, from other repositories
unraid
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows. Runs locally from the @dinglebear/unraid npm package. Needs 6 environment variables to run.
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.
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 2 environment variables to run.
pare-python
Pare Python ג€” Structured Python tool output (ruff, mypy, pip, uv, black, pytest) as typed JSON. Runs locally from the @paretools/python npm package.
python
Structured Python tool output (ruff, mypy, pip-audit, pip-install) as typed JSON. Runs locally from the @paretools/python npm package.
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.