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/Pexafy/pexafy-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/pexafy/pexafy-mcp/pexafy-mcp)<a href="https://agentmods.dev/mcp/pexafy/pexafy-mcp/pexafy-mcp"><img src="https://agentmods.dev/badge/mcp/pexafy/pexafy-mcp/pexafy-mcp/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/pexafy/pexafy-mcp/pexafy-mcp"><img src="https://agentmods.dev/badge/mcp/pexafy/pexafy-mcp/pexafy-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pexafy-mcp 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 9d 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
{
"pexafy-mcp": {
"url": "https://mcp.pexafy.com/mcp",
"type": "streamable-http"
}
}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.
- 9d ago First seen · 6 lines scan A 76655a32b2f7
pexafy-mcp is an MCP server published in the GitHub repository Pexafy/pexafy-mcp (0 stars, last pushed 12d 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
image-search-mcp
MCP server "image-search-mcp" as configured in serbyte-development/image-search-mcp. Runs locally from the serbyte-image-search-mcp Python package. Needs 3 environment variables to run.
mcp-arr
MCP server for arr media suite - Sonarr, Radarr, Lidarr, Readarr, Prowlarr. Runs locally from the mcp-arr-server npm package. Needs 10 environment variables to run.
openrouter-multimodal
Chat with 300+ LLMs via OpenRouter. Analyze and generate images, audio, and video from MCP. Runs locally from the @stabgan/openrouter-mcp-multimodal npm package. Needs 13 environment variables to run.
mcp-suno
MCP Server for Suno AI Music Generation via AceDataCloud API. Runs locally from the mcp-suno Python package. Needs 1 environment variable to run.
mcp
Run any model on the live WaveSpeed catalog: image, video, audio, 3D. Runs locally from the @wavespeed/mcp npm package. Needs 3 environment variables to run.
talkthrough-mcp
Local MCP server: turn screen recordings into transcript, exact frames, OCR and wall-clock evidence for coding agents. Runs locally from the talkthrough-mcp Python package. Needs 4 environment variables to run.