Home / MCP registry index / io.github.adamgraymon/x402-erc8004-api-sla-escrow

x402 erc8004 Api Sla Escrow

io.github.adamgraymon/x402-erc8004-api-sla-escrow in the official MCP registry. Endpoint https://own-adam.onrender.com/mcp. Source: github.com/adamgraymon/Own_adam.

The registry describes it as: Autonomous x402 Paid API SLA Oracle, ERC-8004 Reputation & ERC-8183 USDC Escrow on Base.

We read its 19 tools on 2026-11-17 and our rules matched something worth a look. We show the rule and where it fired, not the flagged text, because that text may be written to instruct an agent. Read the server's tool descriptions yourself before you connect it.

obf.base64_decode_exec
high
Decodes an encoded blob and pipes/evaluates it into an interpreter
tool audit_agent_skill_escrow, line 5

A rule matching is a signal, not a verdict on the people who run the server. If you run it and think this is wrong, write to contact@lazaretto.dev and we will look.

Tools it advertises

discover_verified_stores quote_multitoken_escrow open_escrow_job submit_encrypted_deliverable audit_quant_backtest_escrow audit_smart_contract_escrow audit_api_sla_escrow audit_agent_skill_escrow audit_rag_embeddings_escrow audit_ai_inference_escrow audit_depin_gpu_sla_escrow verify_onchain_escrow_status purchase_firstparty_catalog_item register_and_certify_store inspect_veritas_8183_seal submit_veritas_tier_upgrade_exam manage_buyer_finops_spend_passport notarize_and_witness_a2a_deal match_verified_buyers_by_intent

Tool changes

This server changed its tools after we first read them. If you approved it before the latest change, what you approved is not what it serves now: read its tools again.

Fingerprint of its tools at our last full read (2026-11-17): 2c9f2d7663efea5a. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-adamgraymon-x402-erc8004-api-sla-escrow/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-adamgraymon-x402-erc8004-api-sla-escrow)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

Crank Protocol
ing.crank/crank
196 tools, nothing matched
2026-11-14
Wever Labs Agent Products
io.github.CodeWever/wever-labs-products
178 tools, nothing matched
2026-11-06
AI 代理人任務中樞
dev.workers.panda198271.agent-hub-tw/agent-hub
174 tools, nothing matched
2026-11-06
AgentIndex x402
world.agentindex/x402
143 tools, nothing matched
2026-11-09
Geode
com.geodeapps.mcp/geode
138 tools, nothing matched
2026-11-07
Agent Tollgate
com.skinwinking/agent-tollgate
131 tools, nothing matched
2026-11-08