agent-safety MCP server

None of its 18 tools are described as changing anything. For 18 the reading was uncertain, so no mark is shown.

• base_token_checkon 1 other server

  “Base token safety pre-check: name/symbol/decimals/supply, owner and renounce status, proxy implementation, privileged functions found in bytecode (mint, blacklist, pause, fee setters, upgrade) and a …”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • addressstringrequired“ERC-20 token contract on Base”
• base_token_priceon 2 other servers

  “Live USD price of any ERC-20 token on Base from on-chain DEX quotes (Uniswap v3 0.05/0.3/1% pools and Aerodrome, against USDC and WETH; WETH converted with Chainlink ETH/USD).”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • addressstringrequired“ERC-20 token contract on Base”
• base_balanceon 7 other servers

  “Base wallet balances: native ETH and USDC for any address, with the block number they were read at.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • addressstringrequired
• base_txon 7 other servers

  “Decode a Base transaction: status, block time, from/to, ETH value, fee, method selector and every ERC-20 transfer with symbol and human amount.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • hashstringrequired
• domain_email_check

  “Domain DNS and email-security check: A/AAAA, NS, MX (incl.”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • domainstringrequired“domain name, e.g.”
• evm_decode_calldataon 2 other servers

  “Decode EVM transaction calldata before signing: finds the function signature (signature DB, verified by re-encoding to reject selector collisions), decodes all arguments, expands multicall batches, a…”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • datastringrequired“hex calldata (selector + ABI-encoded args), max 16 KB”
• evm_typed_data_check

  “Check an EIP-712 signature request BEFORE signing (the JSON passed to eth_signTypedData_v4): detects ERC-2612 Permit, DAI permit, Uniswap Permit2 (allowance + transfer) and Seaport orders, explains i…”

  Publisher declares: read-only yes · open-world yes

  4 inputs, 3 required

  • typesobjectrequired“EIP-712 type definitions”
  • domainobject“EIP-712 domain (name, version, chainId, verifyingContract)”
  • primaryTypestringrequired
  • messageobjectrequired“the message to be signed”
• base_gason 13 other servers

  “Base gas snapshot: gas price, base fee, priority fee, 10-block base-fee trend, ETH/USD (Chainlink) and estimated USD cost of an ETH transfer, ERC-20 transfer, swap and contract deploy right now.”

  Publisher declares: read-only yes · open-world yes

  1 input

  • gasLimitstring“optional: gas units of your own transaction; adds estimatedCost.custom (ETH + USD)”
• ens_resolveon 21 other servers

  “Resolve ENS and Basenames (name.eth, name.base.eth): name → address, or address → primary name with forward verification, plus text records (avatar, description, url, twitter, github, email).”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • qstringrequired“ENS/Basename (e.g.”
• domain_whoison 15 other servers

  “Domain registration lookup (RDAP, the official WHOIS successor): registration date and age in days, expiry, registrar and its abuse email, EPP status, nameservers, DNSSEC, and flags for brand-new (<3…”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • domainstringrequired“domain or host name, e.g.”
• domain_dnson 4 other servers

  “DNS lookup in one call: A, AAAA, CNAME, MX, TXT, NS and CAA records with TTLs (or just the types you ask for), NXDOMAIN status, DNSSEC validation, plus parsed hints: SPF record, CAA certificate issue…”

  Publisher declares: read-only yes · open-world yes

  2 inputs, 1 required

  • namestringrequired“domain or host name”
  • typesstring“optional comma list of A,AAAA,CNAME,MX,TXT,NS,CAA,SOA (default: all but SOA)”
• web_security_headers

  “Website security-headers audit: follows redirects (SSRF-guarded) and grades the final page A–F on HSTS, Content-Security-Policy (script-src unsafe-inline/eval/wildcards), clickjacking protection, nos…”

  Publisher declares: read-only yes · open-world yes

  1 input, 1 required

  • urlstringrequired“http(s) URL of a public site”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.