Skip to content

ERC-20 allowance check (x402) MCP server

work.agentexchange/erc20-allowanceagentexchange.workstreamable-httpv1.0.0Scanned

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

1 tool: 1 only read.

Tools: 0 delete, 0 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the ERC-20 allowance check (x402) MCP server can do

The ERC-20 allowance check (x402) MCP server is published by agentexchange.work, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (get_chain_allowance).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Only reads 1Show 1 read-only tool
  • get_chain_allowanceHow 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_chain_allowance" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:27 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://store.agentexchange.work/.well-known/oauth-protected-resource/chain/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http erc20-allowance https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance
claude mcp add --transport http erc20-allowance https://store.agentexchange.work/chain/mcp?tools=get_chain_allowance

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__erc20-allowance__get_chain_allowance"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as erc20-allowance. Review it before you use it.

Capability tags behind 1 rule
  • mcp__erc20-allowance__get_chain_allowance untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/work.agentexchange/erc20-allowance/verify?hash=ad17c28caefd3cd0d561f634c2065f284cfd7b217c7ac61f652047e8108a7830" | jq -e '.changed == false'

Pinned hash ad17c28caefd, from Nov 20, 2026, 13:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/work.agentexchange/erc20-allowance/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for work.agentexchange/erc20-allowance
[![Anlyon Radar](https://radar.anlyon.com/badge/work.agentexchange/erc20-allowance.svg)](https://radar.anlyon.com/servers/work.agentexchange/erc20-allowance)

Source: MCP Registry. Synced Nov 20, 2026, 14:18 UTC.

ERC-20 allowance check (x402) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the ERC-20 allowance check (x402) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ERC-20 allowance check (x402) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ERC-20 allowance check (x402) MCP server have?

1 tool: 1 read. get_chain_allowance.

Does the ERC-20 allowance check (x402) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ERC-20 allowance check (x402) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ERC-20 allowance check (x402) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.