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/sepehrbayat/sepcc/fcc-graphgit clone --depth 1 https://github.com/sepehrbayat/SEPCCWrote 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/sepehrbayat/sepcc/fcc-graph)<a href="https://agentmods.dev/mcp/sepehrbayat/sepcc/fcc-graph"><img src="https://agentmods.dev/badge/mcp/sepehrbayat/sepcc/fcc-graph.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
fcc-graph 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
{
"fcc-graph": {
"command": "uv",
"args": [
"run",
"python",
"scripts/graph/mcp_server.py"
],
"env": {
"FCC_PROJECT_ROOT": "${CLAUDE_PROJECT_DIR:-.}"
}
}
}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.
- 5d ago First seen · 13 lines scan A 5b6ce229b8fc
fcc-graph is an MCP server published in the GitHub repository sepehrbayat/SEPCC (38 stars, last pushed 14d 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-30.
Other mcp servers, from other repositories
pare-test
Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON. Runs locally from the @paretools/test npm package.
Pinecone
Model Context Protocol server for Pinecone - enables AI assistants to interact with Pinecone indexes and documentation. Runs locally from the @pinecone-database/mcp npm package. Needs 1 environment variable to run.
CloudflareLogpush
MCP server "CloudflareLogpush", hosted remotely at logs.mcp.cloudflare.com, as configured in spacehendrix/clauder.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.