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/beepboop2025/undertow-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/beepboop2025/undertow-mcp/undertow)<a href="https://agentmods.dev/mcp/beepboop2025/undertow-mcp/undertow"><img src="https://agentmods.dev/badge/mcp/beepboop2025/undertow-mcp/undertow/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/beepboop2025/undertow-mcp/undertow"><img src="https://agentmods.dev/badge/mcp/beepboop2025/undertow-mcp/undertow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
undertow 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 1mo 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
{
"undertow": {
"url": "https://api.seiche.info/undertow/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.
- 1mo ago First seen · 6 lines scan A 51775bb7488e
undertow is an MCP server published in the GitHub repository beepboop2025/undertow-mcp (0 stars, last pushed yesterday), 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
mcp
Hyperliquid and Lighter market data: order books, trades, candles, funding, OI, and webhooks. Remote server at mcp.0xarchive.io.
brs-signals-mcp
Live Bitcoin market regime for agents: three sensors read pre-price data — fee curves, funding velocity, whale flows, absence — every 30s and reject almost everything. When they converge, a directional call is emitted with evidence. The data can't be reconstructed from history. Public, agent-auditable track record.…
prereason
MCP server "prereason", hosted remotely at api.prereason.com, as configured in PreReason/mcp.
chart-library
MCP server "chart-library" as configured in grahammccain/chart-library-mcp. Launched with chartlibrary-mcp. Needs 1 environment variable to run.
intelligence
36 tools: intel feeds, DeFi, crypto, OSINT, NLP, scraping, proxy. x402 micropayments. Runs locally from the @apollo_ai/mcp-proxy npm package. Needs 1 environment variable to run.
apollo-proxy
26 AI tools: DeFi, OSINT, crypto, intel feeds, search, proxy. x402 micropayments. Runs locally from the @apollo_ai/mcp-proxy npm package.