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/fopost/fopost-mcp/mcpgit clone --depth 1 https://github.com/fopost/fopost-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/fopost/fopost-mcp/mcp)<a href="https://agentmods.dev/mcp/fopost/fopost-mcp/mcp"><img src="https://agentmods.dev/badge/mcp/fopost/fopost-mcp/mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
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 5d 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
{ "mcp": { "command": "npx", "args": [ "-y", "@fopost/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.
- 5d ago First seen · 9 lines scan A b7ee94d7f9bb
mcp is an MCP server published in the GitHub repository fopost/fopost-mcp (0 stars, last pushed yesterday), 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-31.
Other mcp servers, from other repositories
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
filesystem
Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package. Needs 1 environment variable to run.
weather
MCP server "weather", hosted remotely at mcp.example.com, as configured in archestra-ai/archestra.
winnow
Winnow — an embedded TypeScript SDK that lets an agent use many MCP servers without context bloat. Runs locally from the mcp-winnow npm package.
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
salva
MCP server "salva" as configured in 0xRyanlee/salva. Runs apps.mcp with /Volumes/Astoria/Projects/salva/.venv/bin/python.