Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentResolver — Agent Commerce Health Monitoring

REMOTE · AGENTRESOLVER.VERCEL.APP

Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.

0 this week 84 Trust /100

Last scanned (17 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2495 tokens (~69/item across 36 items; 36 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (11% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 36 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.93 functional
  • 16 Oct 26 0
    • Stability: fail → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://agentresolver.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentresolver.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
vercel.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentresolver.vercel.app/mcp Verified 200
http (plaintext) http://agentresolver.vercel.app/mcp HTTPS enforced 308 https://agentresolver.vercel.app/mcp
MCP tools · 36 exposed · ~2,281 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
abi_decode ~44

Paid $0.005 USDC on Base or Solana exact Ethereum ABI decoding into JSON-safe typed values.

NameTypeReqDescription
datastringyes–
typesarrayyes–

No output schema declared.

No examples provided.

abi_encode ~48

Paid $0.005 USDC on Base or Solana exact Ethereum ABI encoding from Solidity typed JSON values to calldata-ready hex.

NameTypeReqDescription
typesarrayyes–
valuesarrayyes–

No output schema declared.

No examples provided.

agent_distribution_pack ~126

Paid $5 USDC seller-side agent distribution pack for API/MCP discoverability: live discovery audit, ready-to-commit agent-readable artifacts, and a prioritized API/MCP distribution sequence.

NameTypeReqDescription
descriptionstringyes–
mcpEndpointstring––
mcpNamestring––
openapiUrlstring––
originstringyes–
primaryEndpointstring––
providerNamestringyes–
repositoryUrlstring––
tagsarray––
versionstring––

No output schema declared.

No examples provided.

agent_readiness ~57

Paid $0.005 USDC on Base or Solana audit of a public website for agent discoverability and machine-readable integration signals. x402-aware MCP clients can authorize and settle inside this tool call.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

base64_decode ~36

Paid $0.001 USDC on Base or Solana Base64 to UTF-8 decoding.

NameTypeReqDescription
inputstringyes–

No output schema declared.

No examples provided.

base64_encode ~36

Paid $0.001 USDC on Base or Solana UTF-8 to Base64 encoding.

NameTypeReqDescription
inputstringyes–

No output schema declared.

No examples provided.

batch_verified_resolve ~63

Paid $0.05 USDC on Base or Solana batch live verification for 2–4 capability decisions using unpaid MCP and x402/HTTP evidence. x402-aware MCP clients can authorize and settle inside this tool call.

NameTypeReqDescription
itemsarrayyes–

No output schema declared.

No examples provided.

eip712_hash ~65

Paid $0.005 USDC on Base or Solana exact EIP-712 typed-data digest for signing and verification workflows.

NameTypeReqDescription
domainobjectyes–
messageobjectyes–
primaryTypestringyes–
typesobjectyes–

No output schema declared.

No examples provided.

ens_namehash ~42

Paid $0.01 USDC on Base or Solana ENSIP-15 normalization, exact ENS namehash and label hashes.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

evm_address_checksum ~40

Paid $0.003 USDC on Base or Solana exact EIP-55 address validation and checksum normalization.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

evm_units ~52

Paid $0.005 USDC on Base or Solana exact decimal/base-unit conversion with arbitrary token decimals.

NameTypeReqDescription
decimalsintegeryes–
modestringyes–
valuestringyes–

No output schema declared.

No examples provided.

hash_encode ~83

Paid $0.001 USDC on Base or Solana deterministic SHA-256, SHA-512, HMAC-SHA256, Base64 encode/decode, or non-verifying JWT decode. x402-aware MCP clients can authorize and settle inside this tool call.

NameTypeReqDescription
inputstringyes–
operationstringyes–
secretstring––

Structured output declared, but exposes no named fields.

No examples provided.

hmac_sha256 ~44

Paid $0.001 USDC on Base or Solana HMAC-SHA256 hex digest.

NameTypeReqDescription
inputstringyes–
secretstringyes–

No output schema declared.

No examples provided.

http_inspect ~77

Paid $0.001 USDC on Base or Solana verify-before-pay endpoint safety check: payTo verification, quote price, network, asset, resource binding and x402 challenge compliance before an agent authorizes spend. POST probes require explicit caller opt-in because an unprotected endpoint could have side effects.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

json_normalize ~35

Paid $0.001 USDC on Base or Solana canonical JSON normalization plus SHA-256 digest.

NameTypeReqDescription
value–yes–

No output schema declared.

No examples provided.

json_schema_validate ~39

Paid $0.001 USDC on Base or Solana deterministic JSON Schema subset validation.

NameTypeReqDescription
data–yes–
schemaobjectyes–

No output schema declared.

No examples provided.

jwt_decode ~36

Paid $0.001 USDC on Base or Solana non-verifying JWT header/payload decode.

NameTypeReqDescription
inputstringyes–

No output schema declared.

No examples provided.

keccak256 ~50

Paid $0.004 USDC on Base or Solana exact Ethereum keccak256 digest for UTF-8 text or hex bytes.

NameTypeReqDescription
encodingstring––
inputstringyes–

No output schema declared.

No examples provided.

mcp_preflight ~62

Paid $0.001 USDC on Base or Solana live MCP endpoint preflight for reachability, compatibility, latency, server metadata and tool inventory. x402-aware MCP clients can authorize and settle inside this tool call.

NameTypeReqDescription
endpointstringyes–

No output schema declared.

No examples provided.

openapi_select ~74

Paid $0.005 USDC on Base or Solana selection of the best operation from one public JSON OpenAPI spec for a stated goal. Returns a compact execution-ready contract. x402-aware MCP clients can authorize and settle inside this tool call.

NameTypeReqDescription
goalstringyes–
specUrlstringyes–

No output schema declared.

No examples provided.

payment_guard ~118

Paid $0.001 USDC fail-closed payment authorization preflight. Use immediately before an autonomous agent signs a target x402 payment. Returns eligible/blocked, exact observed payment terms, reason codes, evidence receipt and stable fingerprints. The caller retains sole spending authority.

NameTypeReqDescription
allowUnpaidPostProbeboolean––
body–––
expectedNetworkstring––
expectedPayTostring––
maxPriceUsdnumber––
methodstring––
urlstringyes–
NameTypeReqDescription
evidenceReceiptobjectyes–
guardobjectyes–
latencyMsnumberyes–
okbooleanyes–
prepaymentDecisionobjectyes–
statusintegeryes–
urlstringyes–

No examples provided.

procure ~112

CALL THIS when the agent's installed tools do not clearly satisfy the current task. Free open-world procurement across APIs, MCP, x402, L402 and MPP. Required compatibility evidence fails closed: AgentResolver returns no selected provider rather than guessing. When supported unknowns remain, the response can recommend the paid $0.02 verified_resolve step. Never authorizes spend.

NameTypeReqDescription
constraintsobject––
goalstringyes–
limitinteger––
providerOriginsarray––

No output schema declared.

No examples provided.

provider_bootstrap ~86

Free zero-state provider onboarding. Reads the fixed AgentResolver well-known manifest on one HTTPS origin, live-verifies selected same-origin x402 payment identities, returns an immediate providerOrigins procurement seed, and prepares caller-owned durable 402 Index registration actions. AgentResolver does not persist provider state or send the external registration.

NameTypeReqDescription
originstringyes–
routeIdsarray––

No output schema declared.

No examples provided.

provider_launch_check ~140

Paid $0.05 USDC seller-side agent-distribution entry check: verify provider readiness and the live x402 contract, then use the $5 Distribution Pack when discoverability artifacts or launch fixes are needed.

NameTypeReqDescription
capabilityIdstringyes–
descriptionstringyes–
endpointstringyes–
methodstring––
namestringyes–
networkstring––
originstringyes–
priceUsdnumberyes–
probeUrlstring––
providerIdstringyes–
providerNamestringyes–
tagsarray––

No output schema declared.

No examples provided.

resolve ~72

Free exploratory discovery. Use only when browsing possible tools/APIs/MCP services without needing a trustworthy execution choice yet. For an actual missing capability, prefer procure so required evidence fails closed and unresolved candidates can escalate to verification.

NameTypeReqDescription
goalstringyes–
limitinteger––
urlstring––

No output schema declared.

No examples provided.

sha256 ~38

Paid $0.001 USDC on Base or Solana SHA-256 digest of bounded UTF-8 text.

NameTypeReqDescription
inputstringyes–

No output schema declared.

No examples provided.

sha512 ~38

Paid $0.001 USDC on Base or Solana SHA-512 digest of bounded UTF-8 text.

NameTypeReqDescription
inputstringyes–

No output schema declared.

No examples provided.

slugify ~38

Paid $0.001 USDC on Base or Solana deterministic slug generation.

NameTypeReqDescription
separatorstring––
textstringyes–

No output schema declared.

No examples provided.

solidity_selector ~41

Paid $0.01 USDC on Base or Solana exact 4-byte Solidity selector and full keccak256 signature hash.

NameTypeReqDescription
signaturestringyes–

No output schema declared.

No examples provided.

sponsorship_info ~40

Free read-only information for tool/API/MCP providers about AgentResolver's explicitly labeled sponsorship pilot. Organic ranking remains independent; applying creates no purchase or financial commitment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tool_contract ~77

Paid $0.005 USDC on Base or Solana deterministic JSON-schema compatibility check between one tool output and the next tool input. Returns exact incompatibility reasons and conservative normalized mappings. x402-aware MCP clients can authorize and settle inside this tool call.

NameTypeReqDescription
consumerInputSchemaobjectyes–
producerOutputSchemaobjectyes–

No output schema declared.

No examples provided.

url_parse ~31

Paid $0.001 USDC on Base or Solana absolute URL parser.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

uuid_v4 ~39

Paid $0.001 USDC on Base or Solana UUID v4 generation, up to 20 IDs.

NameTypeReqDescription
countinteger––

No output schema declared.

No examples provided.

verified_resolve ~109

PAID $0.02 USDC verification step. Use after procure returns no proven selection / eligible_with_unknowns, or immediately before trusting an unfamiliar external candidate when live evidence is required. Re-checks supported endpoint, MCP, x402 and contract evidence and returns a fail-closed recommendation. Call only when the host independently authorizes the displayed spend.

NameTypeReqDescription
constraintsobject––
goalstringyes–
providerOriginsarray––
urlstring––

No output schema declared.

No examples provided.

x402_payment_preflight ~131

Paid $0.001 USDC on Base or Solana transaction-path gate for autonomous buyers. Returns eligible/blocked, exact target payment terms, fail-closed reason codes and verifiable evidence before caller authorization. AgentResolver never requests a private key, signs the target payment, or custodies/forwards target funds.

NameTypeReqDescription
allowUnpaidPostProbeboolean––
body–––
expectedNetworkstring––
expectedPayTostring––
maxPriceUsdnumber––
methodstring––
urlstringyes–
NameTypeReqDescription
evidenceReceiptobjectyes–
guardobjectyes–
latencyMsnumberyes–
okbooleanyes–
prepaymentDecisionobjectyes–
statusintegeryes–
urlstringyes–

No examples provided.

x402_ping ~62

Paid $0.001 USDC on Base or Solana no-body settlement canary for funded agents. Returns a timestamped pong only after successful x402 payment to verify wallet, facilitator, payment, and delivery end-to-end.

NameTypeReqDescription
echostring––
NameTypeReqDescription
atstringyes–
echostring|nullyes–
nextobjectyes–
pongbooleanyes–
requestIdstringyes–
settledDeliverybooleanyes–
unixMsintegeryes–

No examples provided.

Install

How do I install the AgentResolver — Agent Commerce Health Monitoring MCP server?

AgentResolver — Agent Commerce Health Monitoring is a hosted endpoint at https://agentresolver.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agentresolver.vercel.app

# add to Claude Code
claude mcp add --transport http waxsway-agentresolver 'https://agentresolver.vercel.app/mcp'
Common questions

What is the AgentResolver — Agent Commerce Health Monitoring MCP server?

AgentResolver — Agent Commerce Health Monitoring is an MCP server listed in the public MCP registry as io.github.waxsway/agentresolver. Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services. This page covers its hosted endpoint (https://agentresolver.vercel.app/mcp).

Is the AgentResolver — Agent Commerce Health Monitoring MCP server safe to use?

AgentResolver — Agent Commerce Health Monitoring scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AgentResolver — Agent Commerce Health Monitoring MCP server expose?

AgentResolver — Agent Commerce Health Monitoring exposes 36 tools: sponsorship_info, resolve, provider_bootstrap, procure, abi_encode, and 31 more. Their descriptions and schemas cost roughly 2,281 tokens of context every time the server is loaded.

Does the AgentResolver — Agent Commerce Health Monitoring MCP server require authentication?

No. We connected to AgentResolver — Agent Commerce Health Monitoring without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentResolver — Agent Commerce Health Monitoring MCP server still maintained?

AgentResolver — Agent Commerce Health Monitoring is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AgentResolver — Agent Commerce Health Monitoring MCP server?

VerifyMCP ran 13 checks on AgentResolver — Agent Commerce Health Monitoring, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.