amanchain MCP server
io.github.gitajhd/amanchaingitajhdstreamable-httpv2.28.0Scanned
AmanChain: quantum-resistant x402 payments. Remote MCP, 50 paid services. USDC on Base or AMAN.
11 tools: 8 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the amanchain MCP server can do
The amanchain MCP server is published by the GitHub account gitajhd. It has 11 tools. It can create or change data (8 tools: aman_chain_info, aman_price, aman_invoke_service, aman_token and 4 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
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 19, 2026, version 2.28.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.
11 tools
Changes things 8Claude Code: ask
aman_chain_infoLive AmanChain network info: height, difficulty, supply, burns, agent economy stats.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Live AmanChain network info: height, difficulty, supply, burns, agent economy stats.
aman_invoke_historyRecent x402 paid calls between agents (the autonomous economy tape).No findings
Why it is in this group
- The name "aman_invoke_history" says "invoke": a word for a change.
Description, as the server wrote it Recent x402 paid calls between agents (the autonomous economy tape).
aman_invoke_serviceCall a paid agent service (AmanPay x402).No findings
Why it is in this group
- The name "aman_invoke_service" says "invoke": a word for a change.
Description, as the server wrote it Call a paid agent service (AmanPay x402). WITHOUT payTxId returns the 402 payment requirements; WITH the txId of a mined agent_invoke payment it verifies the settlement and returns the service result (node-operated services execute real computation).
aman_marketDEX snapshot: pools with real reserves, prices, 24h volume and the latest executed swaps.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it DEX snapshot: pools with real reserves, prices, 24h volume and the latest executed swaps.
aman_priceLive AMAN price from the deepest real AMM pool, with 24h change and TVL.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Live AMAN price from the deepest real AMM pool, with 24h change and TVL.
aman_service_catalogThe full x402 service catalog for agents: every purchasable service with its per-call price in AMAN and USD, request format, proven call stats and the 3-step payment flow.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The full x402 service catalog for agents: every purchasable service with its per-call price in AMAN and USD, request format, proven call stats and the 3-step payment flow. The discovery document for machine agents.
aman_tokenAMT-20 token detail: supply, holders, stable collateral backing, pool depth, governance flags.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it AMT-20 token detail: supply, holders, stable collateral backing, pool depth, governance flags.
aman_tokensAll visible AMT-20 tokens on this network.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it All visible AMT-20 tokens on this network.
Only reads 3Show 3 read-only tools
aman_autopilot_statusAgent Auto-Pilot status: the node-operated keeper agent that pays other agents automatically per call (x402), its schedule, daily spend against the cap and recent settlements.No findings
Why it is in this group
- The name "aman_autopilot_status" says "status": a word for reading.
Description, as the server wrote it Agent Auto-Pilot status: the node-operated keeper agent that pays other agents automatically per call (x402), its schedule, daily spend against the cap and recent settlements.
aman_get_txFetch a transaction by id (mined or pending) including its quantum-shield fingerprint.No findings
Why it is in this group
- The name "aman_get_tx" says "get": a word for reading.
Description, as the server wrote it Fetch a transaction by id (mined or pending) including its quantum-shield fingerprint.
aman_list_servicesList the on-chain AI agent marketplace: every service with its x402 per-call price, provider, calls and volume.No findings
Why it is in this group
- The name "aman_list_services" says "list": a word for reading.
Description, as the server wrote it List the on-chain AI agent marketplace: every service with its x402 per-call price, provider, calls and volume.
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 22, 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
- 8
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet: tools/list returned 11 tools to an anonymous client, including aman_chain_info (write), aman_price (write), aman_invoke_service (write), aman_token (write), aman_tokens (write) and 3 more
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 2.28.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http amanchain https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnetclaude mcp add --transport http amanchain https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnetRun 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.
{
"permissions": {
"allow": [
"mcp__amanchain__aman_list_services",
"mcp__amanchain__aman_get_tx",
"mcp__amanchain__aman_autopilot_status"
],
"ask": [
"mcp__amanchain__aman_chain_info",
"mcp__amanchain__aman_price",
"mcp__amanchain__aman_invoke_service",
"mcp__amanchain__aman_token",
"mcp__amanchain__aman_tokens",
"mcp__amanchain__aman_market",
"mcp__amanchain__aman_invoke_history",
"mcp__amanchain__aman_service_catalog"
],
"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 amanchain. Review it before you use it.
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/io.github.gitajhd/amanchain/verify?hash=8e9a7481a665a85a722735b904010d34ed9422d446b72fabff1906e1ee411a28" | jq -e '.changed == false'Pinned hash 8e9a7481a665, from Nov 19, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.gitajhd/amanchain/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.gitajhd/amanchain)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.
amanchain MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the amanchain MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the amanchain MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the amanchain 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 amanchain MCP server have?
- 11 tools: 8 write, 3 read. aman_chain_info, aman_price, aman_invoke_service, aman_token, aman_tokens, aman_market, aman_invoke_history, aman_service_catalog and 3 more.
Does the amanchain MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the amanchain MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the amanchain MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.