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/stoa-platform/stoaInstalling this writes the configuration, not the program: `python3` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/stoa-platform/stoa/stoa-impact)<a href="https://agentmods.dev/mcp/stoa-platform/stoa/stoa-impact"><img src="https://agentmods.dev/badge/mcp/stoa-platform/stoa/stoa-impact/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/stoa-platform/stoa/stoa-impact"><img src="https://agentmods.dev/badge/mcp/stoa-platform/stoa/stoa-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stoa-impact 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 2mo 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
{
"stoa-impact": {
"command": "python3",
"args": [
"docs/scripts/stoa_impact_mcp.py"
],
"disabled": false
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. 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.
- 2mo ago First seen · 9 lines scan A c38d5963a9ac
stoa-impact is an MCP server published in the GitHub repository stoa-platform/stoa (9 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-08-31.
Other mcp servers, from other repositories
toolmesh
Self-hosted MCP gateway. Turn any REST API into MCP tools via YAML (DADL). Authz, audit, policies. Remote server at {host}.
mcp-gateway
MCP server "mcp-gateway" as configured in MikkoParkkola/mcp-gateway. Runs in Docker (ghcr.io/mikkoparkkola/mcp-gateway:3.5.1).
mcp-gtw
A generic MCP gateway whose tools are registered and executed asynchronously by browser applications over WebSocket. Runs locally from the mcp-gtw Python package.
mcp-llm-bridge
MCP server that routes LLM calls through CLI subscriptions (Claude, Gemini, Codex, Copilot). Runs locally from the mcp-llm-bridge npm package.
mcp-anything
Meta-MCP gateway: search, inspect and call any MCP server from the public registries. Runs locally from the mcp-anything npm package.
mcp-server-template
Production-grade MCP Server Template for TypeScript and Node.js. Runs locally from the @qmmughal/mcp-server-template npm package.