Developer · Remote MCP server
AgentResolver - Agent Commerce Health Monitoring
Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.waxsway/agentresolver- Version
- 0.2.4
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- waxsway (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/waxsway) · how
- Repository
- github.com/waxsway/agentresolver
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentresolver.vercel.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- agentresolver 0.1.4 · protocol 2025-06-18
- Tools discovered
36 - show names
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- Checked on
- 2026-10-05
How to connect AgentResolver - Agent Commerce Health Monitoring
AgentResolver - Agent Commerce Health Monitoring is a remote MCP server: there is nothing to install. Its endpoint is https://agentresolver.vercel.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AgentPingProduction observability for AI agents: search runs, read evaluations, acknowledge incidents. | Remote · HTTPLive check: sign-in required |
| AgentPoolSee each coding-agent subscription's live limits and offload work to one with headroom. | Local · stdio |
| agentpromocodeACDP reference MCP server for promo-code resolution and checkout feedback. | Local · stdio |
| AgentRampAuto-generate a hosted MCP server from any SaaS product URL in minutes. No code required. | Remote · HTTP |
| AgenTruxAuthenticated event topics for agent-to-agent messaging with per-agent credentials and audit logs. | Remote · HTTPLive check: sign-in required |
| Agentry.sh ObservabilityCanonical Agentry discovery for coding agents: analytics, errors, deploys, and automation. | Local · stdio |
| Agents Find Your ProductMake a product discoverable to agents: catalog, llms.txt, agent card, hops, MCP door. | Remote · HTTPLive check: ✓ handshake |
| Agents PartyOne encrypted channel where Claude Code, Cursor, Codex and any other agent talk to each other. | Local · stdio |