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/degenlegion-com/waxseal-sdkWrote 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/degenlegion-com/waxseal-sdk/waxseal)<a href="https://agentmods.dev/mcp/degenlegion-com/waxseal-sdk/waxseal"><img src="https://agentmods.dev/badge/mcp/degenlegion-com/waxseal-sdk/waxseal/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/degenlegion-com/waxseal-sdk/waxseal"><img src="https://agentmods.dev/badge/mcp/degenlegion-com/waxseal-sdk/waxseal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
waxseal 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 11d 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
{ "waxseal": { "command": "npx", "args": [ "-y", "@waxseal/mcp" ], "env": { "WAXSEAL_PRIVATE_KEY_PEM": "" } } }
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.
- 11d ago First seen · 12 lines scan A 1d3ce060e91a
waxseal is an MCP server published in the GitHub repository degenlegion-com/waxseal-sdk (1 stars, last pushed 2mo 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
cabal-hunter
MCP server "cabal-hunter", hosted remotely at api.cabal-hunter.com, as configured in paulf280-ui/solana-safe-sniper-mcp-template.
arb-dex-mcp
Live cross-DEX pool prices, liquidity and spreads on 6 EVM chains, read from on-chain pool state. Runs locally from the arb-dex-mcp npm package. Needs 2 environment variables to run.
bubble-agent-mcp
Open-source MCP server for discovering and understanding fast-growing internet conversations with Bubble Agent. Runs locally from the bubble-agent-mcp npm package.
evmscope
EVM blockchain intelligence toolkit for AI agents. 20 tools across 5 chains. Zero config. Runs locally from the evmscope npm package.
rsk-mcp-server
MCP Server for Rootstock Blockchain. Runs locally from the @rsksmart/rsk-mcp-server npm package.
animica
MCP server "animica" as configured in animicaorg/animica-mcp. Launched with animica-mcp.