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.

ERC-20 allowance check (x402)

REMOTE · STORE.AGENTEXCHANGE.WORK

How much of an ERC-20 a spender may move from a wallet (approval risk check). x402 per call.

61 Trust /100

Last scanned (21 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security63
  • 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability49
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 135 tokens (~135/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 60

    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 21 Nov 2026 · Probed https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentexchange.work CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 cdd21212e1bb1f6a135983b641230886
SANs: agentexchange.work, store.agentexchange.work, *.store.agentexchange.work
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of store.agentexchange.work. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
work. DS published 33659 13 Verified
agentexchange.work. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance Verified 200
http (plaintext) http://store.agentexchange.work/chain/mcp?tools=get_chain_allowance Served over HTTP 200
MCP tools · 1 exposed · ~97 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
get_chain_allowance ~97

How much of an ERC-20 token a spender is approved to move from an owner's wallet, via allowance, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The approval read every DeFi, swap and trading agent makes before (and after) a transaction to know if an approve is needed. Live public RPC; one paid call.

NameTypeReqDescription
x_paymentstring–Signed x402 payment payload

No output schema declared.

No examples provided.

Install

How do I install the ERC-20 allowance check (x402) MCP server?

ERC-20 allowance check (x402) is a hosted endpoint at https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance, 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 · store.agentexchange.work

# add to Claude Code
claude mcp add --transport http work-agentexchange-erc20-allowance 'https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance'
Common questions

What is the ERC-20 allowance check (x402) MCP server?

ERC-20 allowance check (x402) is an MCP server listed in the public MCP registry as work.agentexchange/erc20-allowance. How much of an ERC-20 a spender may move from a wallet (approval risk check). x402 per call. This page covers its hosted endpoint (https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance).

Is the ERC-20 allowance check (x402) MCP server safe to use?

ERC-20 allowance check (x402) scores 61 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 ERC-20 allowance check (x402) MCP server expose?

ERC-20 allowance check (x402) exposes 1 tool: get_chain_allowance. Their descriptions and schemas cost roughly 97 tokens of context every time the server is loaded.

Does the ERC-20 allowance check (x402) MCP server require authentication?

No. We connected to ERC-20 allowance check (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ERC-20 allowance check (x402) MCP server still maintained?

ERC-20 allowance check (x402) 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 ERC-20 allowance check (x402) MCP server?

VerifyMCP ran 13 checks on ERC-20 allowance check (x402), 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.