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.
npx agentmods add mcp/akanthed/secureai-scan/mcp-remote-toolsgit clone --depth 1 https://github.com/akanthed/SecureAI-ScanWrote 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/akanthed/secureai-scan/mcp-remote-tools)<a href="https://agentmods.dev/mcp/akanthed/secureai-scan/mcp-remote-tools"><img src="https://agentmods.dev/badge/mcp/akanthed/secureai-scan/mcp-remote-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
remote-tools 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 6d 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
{
"remote-tools": {
"url": "https://tools.example.com/mcp"
}
}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.
- 6d ago First seen · 5 lines scan A 9fcf89a1e5ea
remote-tools is an MCP server published in the GitHub repository akanthed/SecureAI-Scan (19 stars, last pushed today), 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
stripe-mcp
MCP server "stripe-mcp" as configured in apisec-inc/AI-Surface. Runs locally from the @stripe/mcp-server npm package.
github-mcp
MCP server "github-mcp", hosted remotely at mcp.github.com, as configured in apisec-inc/AI-Surface.
koma-gate-mcp
Classifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it. Runs locally from the koma-gate-mcp npm package. Needs 6 environment variables to run.
koma-core-mcp
Protected RAG storage — agents discover public metadata, content only by access token. Runs locally from the koma-core-mcp npm package. Needs 1 environment variable to run.
scenario-assistant
MCP server "scenario-assistant" as configured in prime-radiant-inc/scenarios. Runs locally from the ../../tools/mcp_server.py Python package.
assay
MCP server "assay" as configured in chawdamrunal/assay. Launched with assay mcp --transport stdio.