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/runningoffcode/agent-wormholeWrote 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/runningoffcode/agent-wormhole/wormhole-x402)<a href="https://agentmods.dev/mcp/runningoffcode/agent-wormhole/wormhole-x402"><img src="https://agentmods.dev/badge/mcp/runningoffcode/agent-wormhole/wormhole-x402/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/runningoffcode/agent-wormhole/wormhole-x402"><img src="https://agentmods.dev/badge/mcp/runningoffcode/agent-wormhole/wormhole-x402.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
wormhole-x402 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 3d 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
{
"wormhole-x402": {
"command": "npx",
"args": [
"-y",
"wormhole-x402"
],
"env": {
"WORMHOLE_API_KEY": "",
"WORMHOLE_VERIFY_URL": "",
"WORMHOLE_ADDRESS_LEDGER": ""
}
}
}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.
- 3d ago First seen · 14 lines scan A 4c5f14804cb0
wormhole-x402 is an MCP server published in the GitHub repository runningoffcode/agent-wormhole (3 stars, last pushed yesterday), licensed Apache-2.0. 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-09-13.
Other mcp servers, from other repositories
dfx-agentguard
Autonomous security scanner for AI agents. Detects prompt injection, tool abuse, data exfiltration, and OWASP ASI Top 10 vulnerabilities. Runs locally from the dfx-agentguard Python package.
shellward
AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP. Runs locally from the shellward npm package. Needs 3 environment variables to run.
filesystem
Gives the agent read and write access to a set of allowed directories on the local filesystem. Runs locally from the @modelcontextprotocol/server-filesystem npm package.
shell
MCP server "shell" as configured in opena2a-org/hackmyagent. Runs locally from the @anthropic/mcp-shell-server npm package.
local-dev
MCP server "local-dev", hosted remotely at localhost, as configured in akanthed/SecureAI-Scan.
tooltrust-scanner
Scans MCP servers for prompt injection, data exfiltration, and privilege escalation. Runs locally from the tooltrust-mcp npm package.