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/Br0ski777/ens-resolver-x402Wrote 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/br0ski777/ens-resolver-x402/ens-resolver)<a href="https://agentmods.dev/mcp/br0ski777/ens-resolver-x402/ens-resolver"><img src="https://agentmods.dev/badge/mcp/br0ski777/ens-resolver-x402/ens-resolver/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/br0ski777/ens-resolver-x402/ens-resolver"><img src="https://agentmods.dev/badge/mcp/br0ski777/ens-resolver-x402/ens-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ens-resolver 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
{
"ens-resolver": {
"url": "https://ens-resolver.api.klymax402.com/mcp",
"type": "sse"
}
}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 f3bcd323fc0c
ens-resolver is an MCP server published in the GitHub repository Br0ski777/ens-resolver-x402 (0 stars, last pushed 7d 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
bray
Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity. Runs locally from the nostr-bray npm package. Needs 3 environment variables to run.
ens
ENS (Ethereum Name Service) MCP. Remote server at gateway.pipeworx.io.
wallet-identity
Resolve wallet addresses to X and Farcaster accounts, and back again. Remote server at walletlink.social.
mintlify
MCP server "mintlify", hosted remotely at www.mintlify.com, as configured in starl3xx/wallet-to-social.
walletlink-docs
MCP server "walletlink-docs", hosted remotely at docs.walletlink.social, as configured in starl3xx/wallet-to-social.
mint-mcp
Trust stack for AI agents: identity, attest, verify, rate, recommend, discover — on Solana. Remote server at mint-mcp-production.up.railway.app.