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/manykarim/rf-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/manykarim/rf-mcp/robotmcp)<a href="https://agentmods.dev/mcp/manykarim/rf-mcp/robotmcp"><img src="https://agentmods.dev/badge/mcp/manykarim/rf-mcp/robotmcp/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/manykarim/rf-mcp/robotmcp"><img src="https://agentmods.dev/badge/mcp/manykarim/rf-mcp/robotmcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
Grade A, and why
robotmcp 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 yesterday.
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
{
"robotmcp": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"-m",
"robotmcp.server"
],
"env": {
"ROBOTMCP_TOKENIZER": "auto",
"ROBOTMCP_OUTPUT_MODE": "auto",
"ROBOTMCP_MAX_INLINE_TOKENS": "300",
"ROBOTMCP_ARTIFACT_TTL": "3600"
}
}
}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.
- yesterday First seen · 17 lines scan A 9637bb04f142
robotmcp is an MCP server published in the GitHub repository manykarim/rf-mcp (114 stars, last pushed today), 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-09-21.
Other mcp servers, from other repositories
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
yaml-workflow
A lightweight workflow engine for CI/CD pipelines, data processing, and DevOps automation — define tasks in YAML, run anywhere. Runs locally from the yaml-workflow Python package.
n8n-workflow-builder
A Python library for building, managing, and deploying n8n workflows with configuration-driven templates. Runs locally from the n8n-workflow-builder Python package.
vmware-avi
AVI (NSX Advanced Load Balancer) management and AKO Kubernetes operations tool. Runs locally from the vmware-avi Python package.
iac-mcp
MCP server "iac-mcp" as configured in jsavin/iac-mcp. Runs /absolute/path/to/iac-mcp/dist/index.js with node. Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.