Home / MCP registry index / io.github.waxsway/agentresolver
AgentResolver — Agent Commerce Health Monitoring
io.github.waxsway/agentresolver in the official MCP registry.
Endpoint https://agentresolver.vercel.app/mcp. Source: github.com/waxsway/agentresolver.
The registry describes it as: Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.
We read its 36 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
sponsorship_info resolve provider_bootstrap procure abi_encode abi_decode eip712_hash ens_namehash evm_address_checksum keccak256 solidity_selector evm_units x402_ping sha256 sha512 hmac_sha256 base64_encode base64_decode jwt_decode json_normalize json_schema_validate url_parse uuid_v4 slugify hash_encode payment_guard x402_payment_preflight http_inspect tool_contract openapi_select mcp_preflight agent_readiness agent_distribution_pack provider_launch_check verified_resolve batch_verified_resolve
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-waxsway-agentresolver)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. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.