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/MaximilianoColoma/missionWrote 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/maximilianocoloma/mission/mission-public)<a href="https://agentmods.dev/mcp/maximilianocoloma/mission/mission-public"><img src="https://agentmods.dev/badge/mcp/maximilianocoloma/mission/mission-public/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/maximilianocoloma/mission/mission-public"><img src="https://agentmods.dev/badge/mcp/maximilianocoloma/mission/mission-public.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mission-public 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 10d 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
{ "mission-public": { "command": "uvx", "args": [ "mission-public" ] } }
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.
- 10d ago First seen · 8 lines scan A 526c56a39e66
mission-public is an MCP server published in the GitHub repository MaximilianoColoma/mission (0 stars, last pushed 19d 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
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
mnemos-core
MCP server "mnemos-core" as configured in ncz-os/mnemos. Runs locally from the mnemos-core Python package.
twining
MCP server "twining" as configured in daveangulo/twining-mcp. Launched with twining-mcp --project ..
fcop
stdio MCP server for the FCoP Python library: exposes the fcop package's Project, task, report, issue, GAL alert, and audit APIs to MCP clients (Cursor, Claude Desktop, …). Optional bridge, not a second protocol; depends on fcop 3.x, FastMCP, websockets. Runs locally from the fcop-mcp Python package. Needs 1…
fleetpost-mcp
MCP server for Fleetpost — offline-tolerant, server-less agent coordination over any rclone remote. Runs locally from the fleetpost-mcp Python package. Needs 2 environment variables to run.
llm-bus
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks. Remote server at mcp.llm-bus.com.