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 Guard — Verify x402 Before Paying

REMOTE · AGENTRESOLVER.VERCEL.APP · SCANNED SEP 25

Capability procurement + provider routing; $0.001 x402 verify-before-pay Guard on Base + Solana.

+1 this week 69 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2290 tokens (~65/item across 35 items; 35 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 10 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 34 additions. See how to fix → Fail
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 35 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • Manipulation not yet verified: only 35 of 36 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the AgentResolver Guard — Verify x402 Before Paying MCP server?

AgentResolver Guard — Verify x402 Before Paying 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'
// .cursor/mcp.json
{
  "mcpServers": {
    "waxsway-agentresolver": {
      "url": "https://agentresolver.vercel.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "waxsway-agentresolver": {
      "type": "http",
      "url": "https://agentresolver.vercel.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.waxsway-agentresolver]
url = "https://agentresolver.vercel.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "waxsway-agentresolver": {
      "type": "remote",
      "url": "https://agentresolver.vercel.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add waxsway-agentresolver --url 'https://agentresolver.vercel.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  waxsway-agentresolver:
    url: "https://agentresolver.vercel.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "waxsway-agentresolver": {
      "Transport": "http",
      "Url": "https://agentresolver.vercel.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add waxsway-agentresolver -t streamable-http -u 'https://agentresolver.vercel.app/mcp'
// mcp.json
{
  "mcpServers": {
    "waxsway-agentresolver": {
      "type": "http",
      "url": "https://agentresolver.vercel.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 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
  • 24 Sept 26 0
    • Server version: 0.1.3 → 0.1.4 functional
  • 21 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “resolve” rewrote its description, which is the text the model reads security
    • Tool “verified_resolve” rewrote its description, which is the text the model reads security
    • Schema quality: 58 → 65 ▼ functional
    • Tool “hash_encode” now declares an output schema ▲ functional
    • Tool “payment_guard” now declares an output schema ▲ functional
    • Tool “x402_payment_preflight” now declares an output schema ▲ functional
    • Tool “x402_ping” now declares an output schema ▲ functional
    • First check of Tool coverage: 11 functional
    • New tool “provider_bootstrap” functional
    • New tool “provider_launch_check” functional
    • New tool “procure” functional
    • “verified_resolve” added an optional parameter “constraints” cosmetic
    • “verified_resolve” added an optional parameter “providerOrigins” cosmetic
    • Tool “resolve” changed its title: Resolve a missing capability → Explore possible capabilities cosmetic
    • Tool “verified_resolve” changed its title: Live verified resolve — $0.02 → Verify an unresolved external capability — $0.02 cosmetic
  • 18 Sept 26 0
    • New tool “payment_guard” functional
    • Tool “x402_payment_preflight” changed its title: X402 preflight — verify endpoint before paying — $0.001 → X402 preflight — verify endpoint before paying — endpoint safety — USDC payment check — $0.001 cosmetic
    • Tool “x402_ping” changed its title: x402 settlement test — $0.001 → x402 settlement test — wallet facilitator payment test — $0.001 cosmetic
  • 17 Sept 26 −2
    • Judged manipulation: pass → unverified ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “agent_readiness” rewrote its description, which is the text the model reads security
    • Tool “batch_verified_resolve” rewrote its description, which is the text the model reads security
    • Tool “http_inspect” rewrote its description, which is the text the model reads security
    • Tool “mcp_preflight” rewrote its description, which is the text the model reads security
    • Tool “openapi_select” rewrote its description, which is the text the model reads security
    • Tool “tool_contract” rewrote its description, which is the text the model reads security
    • Tool “verified_resolve” rewrote its description, which is the text the model reads security
    • Schema quality: 74 → 56 ▲ functional
    • New tool “uuid_v4” functional
    • New tool “x402_payment_preflight” functional
    • New tool “x402_ping” functional
    • New tool “url_parse” functional
    • New tool “abi_decode” functional
    • New tool “abi_encode” functional
    • New tool “base64_decode” functional
    • New tool “base64_encode” functional
    • New tool “eip712_hash” functional
    • New tool “ens_namehash” functional
    • New tool “evm_address_checksum” functional
    • New tool “evm_units” functional
    • New tool “hash_encode” functional
    • New tool “hmac_sha256” functional
    • New tool “json_normalize” functional
    • New tool “json_schema_validate” functional
    • New tool “jwt_decode” functional
    • New tool “keccak256” functional
    • New tool “sha256” functional
    • New tool “sha512” functional
    • New tool “slugify” functional
    • New tool “solidity_selector” functional
    • New tool “sponsorship_info” functional
    • Tool “http_inspect” changed its title: HTTP inspection — $0.001 → x402 payment preflight + PayTo verification — $0.001 cosmetic
  • 16 Sept 26 −1
    • Stability: unverified → fail ▼ security
    • Tool “list_capabilities” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “resolve” rewrote its description, which is the text the model reads security
    • Schema quality: 59 → 74 ▼ functional
    • Server version: 0.1.0 → 0.1.3 functional
    • New tool “tool_contract” functional
    • New tool “verified_resolve” functional
    • New tool “openapi_select” functional
    • New tool “mcp_preflight” functional
    • New tool “http_inspect” functional
    • New tool “batch_verified_resolve” functional
    • New tool “agent_readiness” functional
    • Tool “resolve” changed its title: Resolve a missing capability cosmetic
  • 15 Sept 26 71

    First indexed and scored.

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 25 Sept 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 29 Aug 2026 27 Nov 2026 RSA 2048 SHA256-RSA f7911168ffa7d0f4135e24792e7a52a8
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. present 23684 8 Verified
vercel.app. absent 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 · 35 exposed · ~2,135 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_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 ~120

Paid $0.05 USDC seller-side readiness and x402 contract verification before AgentResolver provider-network review.

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.

Common questions

What is the AgentResolver Guard — Verify x402 Before Paying MCP server?

AgentResolver Guard — Verify x402 Before Paying is an MCP server listed in the public MCP registry as io.github.waxsway/agentresolver. Capability procurement + provider routing; $0.001 x402 verify-before-pay Guard on Base + Solana. This page covers its hosted endpoint (https://agentresolver.vercel.app/mcp).

Is the AgentResolver Guard — Verify x402 Before Paying MCP server safe to use?

AgentResolver Guard — Verify x402 Before Paying scores 69 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 Guard — Verify x402 Before Paying MCP server expose?

AgentResolver Guard — Verify x402 Before Paying exposes 35 tools: sponsorship_info, resolve, provider_bootstrap, procure, abi_encode, and 30 more. Their descriptions and schemas cost roughly 2,135 tokens of context every time the server is loaded.

Does the AgentResolver Guard — Verify x402 Before Paying MCP server require authentication?

No. We connected to AgentResolver Guard — Verify x402 Before Paying without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentResolver Guard — Verify x402 Before Paying MCP server still maintained?

AgentResolver Guard — Verify x402 Before Paying is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.