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/willianpinho/large-file-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/willianpinho/large-file-mcp/sentry)<a href="https://agentmods.dev/mcp/willianpinho/large-file-mcp/sentry"><img src="https://agentmods.dev/badge/mcp/willianpinho/large-file-mcp/sentry/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/willianpinho/large-file-mcp/sentry"><img src="https://agentmods.dev/badge/mcp/willianpinho/large-file-mcp/sentry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sentry 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 1mo 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
{
"sentry": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_ACCESS_TOKEN": "${SENTRY_ACCESS_TOKEN}"
}
}
}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.
- 1mo ago First seen · 12 lines scan A 1ed9a9b95fd8
sentry is an MCP server published in the GitHub repository willianpinho/large-file-mcp (18 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-30.
Other mcp servers, from other repositories
ideal-harness-guard
MCP server "ideal-harness-guard" as configured in bharat3645/The-Ideal-Harness. Runs dist/guard/cli/index.js with node.
mcp-server
Model Context Protocol server for Frontal. Runs locally from the @frontal-labs/mcp-server npm package.
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay 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.
bumpguard
Guard your dependency bumps: an MCP server that tells your AI agent exactly which parts of YOUR code break when you upgrade a dependency, and verifies AI-written code against the API that's actually installed — by static analysis, never by running third-party code. Runs locally from the bumpguard-mcp Python package.
sanction
The wallet an AI agent carries — mandate, budget, vault, and audit. Counterparties verify first. Runs locally from the sanction-mcp npm package. Needs 3 environment variables to run.