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/fieldcure/fieldcure-mcp-outboxWrote 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/fieldcure/fieldcure-mcp-outbox/outbox)<a href="https://agentmods.dev/mcp/fieldcure/fieldcure-mcp-outbox/outbox"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-outbox/outbox/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/fieldcure/fieldcure-mcp-outbox/outbox"><img src="https://agentmods.dev/badge/mcp/fieldcure/fieldcure-mcp-outbox/outbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
outbox 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 8d 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
{
"outbox": {
"command": "fieldcure-mcp-outbox"
}
}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.
- 8d ago First seen · 5 lines scan A 88232719c2b9
outbox is an MCP server published in the GitHub repository fieldcure/fieldcure-mcp-outbox (0 stars, last pushed 3mo ago), 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
awesome-copilot
MCP server "awesome-copilot" as configured in microsoft/mcp-dotnet-samples. Runs in Docker (ghcr.io/microsoft/mcp-dotnet-samples/awesome-copilot:1.0.2026082702).
mcp-server-powerpoint
MCP server "mcp-server-powerpoint" as configured in sbroenne/mcp-server-powerpoint. Launched with Sbroenne.PowerPointMcp.McpServer.
sqlaugur
MCP server "sqlaugur" as configured in mbentham/SqlAugur. Launched with SqlAugur.
orchestrator
MCP server "orchestrator" as configured in Byggarepop/dotnet-mcp-orchestrator. Launched with dotnet run --project C:/Users/sebas/Projects/MCP/McpOrchestrator/McpOrchestrator. Needs 1 environment variable to run.
dotnet-mcp-orchestrator
MCP server "dotnet-mcp-orchestrator" as configured in Byggarepop/dotnet-mcp-orchestrator. Launched with McpOrchestrator.
neuron
MCP server for Neuron — the WhatsApp automation platform. 120+ tools for AI chatbots, broadcasts, campaigns, contacts, knowledge bases, newsletters, and more. Runs locally from the neuron-mcp-server npm package.