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/jonigata/FramePlanner2Wrote 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/jonigata/frameplanner2/sentry)<a href="https://agentmods.dev/mcp/jonigata/frameplanner2/sentry"><img src="https://agentmods.dev/badge/mcp/jonigata/frameplanner2/sentry.svg" alt="Measured on agentmods" 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 2d 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.
This is a copy
100% identical to sentry — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 2d ago First seen · 6 lines scan A f7e776d1448e
sentry is an MCP server published in the GitHub repository jonigata/FramePlanner2 (43 stars, last pushed 15d 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. It is 100% identical to sentry, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
codeindex
MCP server "codeindex" as configured in GetKlai/klai. Launched with bash .claude/scripts/codeindex-mcp-launcher.sh.
dbgprobe-mcp-server
Debug probe Model Context Protocol server for AI agents and developer tooling. Runs locally from the dbgprobe-mcp-server Python package. Needs 9 environment variables to run.
repo-lens-mcp
MCP server for multi-repository AST-based symbol search and API route discovery. Runs locally from the repo-lens-mcp npm package.
broken-link-checker-mcp
MCP server "broken-link-checker-mcp" as configured in davinoishi/BLC-ground. Runs locally from the broken-link-checker-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.