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/warengonzaga/relay-protocol-mcp-serverWrote 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/warengonzaga/relay-protocol-mcp-server/relay-protocol-mcp)<a href="https://agentmods.dev/mcp/warengonzaga/relay-protocol-mcp-server/relay-protocol-mcp"><img src="https://agentmods.dev/badge/mcp/warengonzaga/relay-protocol-mcp-server/relay-protocol-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
relay-protocol-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 6d 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
{ "relay-protocol-mcp": { "command": "npx", "args": [ "-y", "relay-protocol-mcp" ] } }
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.
- 6d ago First seen · 9 lines scan A de5529f16429
relay-protocol-mcp is an MCP server published in the GitHub repository warengonzaga/relay-protocol-mcp-server (1 stars, last pushed 6mo 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
x402-list-mcp
MCP server for x402-list: discover x402 payment services, on-chain-verified facilitator settlement volume, server-ranked recommendations, and paid on-demand assessments (x402 pass-through, never holds keys). Thin wrapper over the public x402-list API. Runs locally from the x402-list-mcp npm package. Needs 2…
unstoppable-domains
MCP server "unstoppable-domains", hosted remotely at api.unstoppabledomains.com, as configured in drQedwards/PPM.
pulsechain-mcp
MCP server "pulsechain-mcp" as configured in DavidFeder/pulsechain-mcp. Runs REPLACE_WITH_ABSOLUTE_PATH/dist/index.js with node. Needs 7 environment variables to run.
solana-mcp-vybe
MCP server "solana-mcp-vybe", hosted remotely at mcp.vybenetwork.xyz, as configured in vybenetwork/solana-mcp-vybe.
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
verantis-mcp
MCP server for Verantis — the verified directory for machine payments (x402 & MPP). Find live-verified services and check a wallet before your agent pays. Runs locally from the verantis-mcp Python package. Needs 1 environment variable to run.