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/feniix/pi-extensions/exagit clone --depth 1 https://github.com/feniix/pi-extensionsWrote 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/feniix/pi-extensions/exa)<a href="https://agentmods.dev/mcp/feniix/pi-extensions/exa"><img src="https://agentmods.dev/badge/mcp/feniix/pi-extensions/exa.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
exa 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 4d 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
{
"exa": {
"type": "http",
"url": "https://mcp.exa.ai/mcp?tools=web_search_exa,web_fetch_exa,web_search_advanced_exa",
"headers": {
"x-api-key": "${EXA_API_KEY}"
},
"env": {
"EXA_API_KEY": "${EXA_API_KEY}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 4d ago First seen · 12 lines scan A c2f498152c9d
exa is an MCP server published in the GitHub repository feniix/pi-extensions (23 stars, last pushed 11d 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
web
MCP server "web" as configured in stormlightlabs/xngmcp. Launched with xngmcp serve. Needs 1 environment variable to run.
browser
MCP server "browser", hosted remotely at unapproved.example, as configured in aolingge/agent-reliability-kit.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
camoufox-research
MCP server for browser research on the anti-detect Camoufox browser: search, page reading (incl. JS/SPA), batch fetch, clicks, typing, sessions, cache. Runs locally from the camoufox-research Python package.
doc-bridge
Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code. Runs locally from the @agentskit/doc-bridge npm package.
gitpin
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. Runs locally from the gitpin npm package. Needs 1 environment variable to run.