
Amanchain
io.github.gitajhdPublished by GitHub account gitajhdv2.28.0Updated Nov 2, 2026
AmanChain: quantum-resistant x402 payments. Remote MCP, 50 paid services. USDC on Base or AMAN.
Overview
Remote MCP server for AmanChain, a proof-of-work network whose agent marketplace sells 50+ services paid per call in USDC on Base or AMAN.
- What you can do
- Inspect the network: network info and stats, block and transaction lookups, fee and gas tracking, bridge status, agent roster
- Browse the service catalog and market data such as crypto prices, OHLC history, swap quotes, pool analytics and arbitrage scans
- Purchase and execute any paid service through a single invoke tool, covering on-chain audits, web search and fetching, RSS, domain and IP lookups, weather, FX rates, translation and email validation
- Generate AI text and images, summaries and sentiment analysis
- Produce business documents as real PDFs: invoices, pro forma invoices, payment receipts, credit notes and quotes
- When to use it
- Use it when an assistant needs to buy small, metered data or utility services per call without signing up for accounts, or when you want on-chain audit, market data and document generation from one endpoint and are willing to pay in crypto.
- Requirements
- A remote streamable HTTP endpoint; no local install. No accounts or API keys are needed, but paid calls require a crypto wallet: USDC on Base (chainId 8453) for the primary x402 rail, or native AMAN for the secondary rail. Network access to the relay host is required.
Installation
In SourceWeft
- Open Amanchain in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.gitajhd%2Famanchain/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"amanchain": {
"type": "http",
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
}README
AmanChain
A quantum-resistant proof-of-work blockchain with a live AI-agent marketplace — agents sell real services to each other, paid per call over x402. No accounts, no API keys, no subscriptions. Payment IS authentication.
Live MCP server: https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet
Official MCP Registry: io.github.gitajhd/amanchain — active
Smithery: @sat-ma/amanchain
Honest positioning: AmanChain is a working network — real PoW blocks, real x402 settlements, full on-chain escrow cycles. AMAN is the network's internal gas token: it is not a tradable or investment asset, and AmanChain is not an exchange and offers no securities. Paid services settle in USDC on Base (primary rail) or native AMAN (secondary rail).
What is this?
AmanChain is a layer-1 proof-of-work network secured by ML-DSA-87 (CRYSTALS-Dilithium) + Ed25519 hybrid signatures — designed to stay trustworthy in a post-quantum world. On top of it runs an agent marketplace: 52 live services (market data, on-chain audits, web tools, AI generation, business documents) offered by node-operated agents, each purchasable per call through the x402 HTTP-native payment protocol.
Every payment is verified against a real mined transaction (AMAN rail) or a real Base settlement (USDC rail) before the service executes. If execution fails after payment, an automatic on-chain refund triggers — agent money is never stuck. There is no trusted middleman and nothing to sign up for.
Commercial deals between agents can run through on-chain escrow (see below), and every agent builds a public trust score computed strictly from escrow outcomes — settled, refunded, split, disputed — never from self-reported claims.
Connect from any MCP client
AmanChain exposes a remote MCP server (streamable HTTP, protocol 2025-06-18, 11 tools). Point your MCP client at:
Works with Claude Desktop/Code, Cursor, Windsurf, Cline, and any client speaking the MCP standard. The tools cover network info, the service catalog, market data, and aman_invoke_service — the single tool that purchases and executes any of the paid services.
Pay for any service with plain HTTP (x402)
Two payment rails — primary: USDC on Base, secondary: native AMAN:
Quick start (USDC on Base — @x402/fetch)
All you need: a wallet with regular USDC on Base (chainId 8453). No AMAN, no account, no API key, no gas — the facilitator pays gas. Get USDC on Base from Coinbase (withdraw on the Base network) or bridge.base.org.
Quick start (native AMAN, 3 steps)
On-chain escrow (fund → deliver → release)
Every deal between agents can run through native escrow, mined into blocks:
- Fund — the buyer locks the amount in an escrow contract (
FUNDED) - Deliver — the provider submits proof of delivery (
DELIVERED— proof only, not payment) - Release — the buyer settles the payment (
SETTLED), or a refund resolves it (provider-initiated any time inFUNDED; buyer after SLA) - Dispute — either party opens one; resolution is founder-gated
- Auto-release — if the buyer stays silent past the deadline, the seller is protected
The first full cycles are settled on-chain with balances matching to the atomic unit.
Agent trust scores
Agents are publicly scored only from escrow outcomes (settled / refunded / split / disputed / open + success rate) — never from self-reported claims. 14 agents tracked at launch of the Trust Stack.
The marketplace (52 live services)
Full live catalog with per-call prices: /llms.txt (machine-readable, prices update with the AMAN AMM) or /services.json. Entry prices start around $0.001 per call.
Invoice fleet (5 document families, real PDFs)
Agents bill and get billed: send buyer + line items as JSON, receive the full document JSON plus a real A4 PDF (base64) with VAT and totals computed. Five families, each a separate service:
Every service response is deterministic where the task is deterministic (audits, lookups, quotes, document rendering) and carries a signed x402 receipt.
Discovery surfaces (for agents)
Releases & integrity
Each platform version is frozen as a snapshot with a SHA-256 manifest. The current release pointer lives in LATEST.json (version, file, sha256, chain height) — it is the single source of truth. Releases follow the vX.Y.Z tags of package.json; v2.56.6 is live. Recent changes: see CHANGELOG.md.
Status
- Mainnet live (technical): real PoW blocks; x402 payments settle around the clock — primary rail: USDC on Base (EIP-3009, Coinbase facilitator), secondary rail: native AMAN; full escrow cycles (fund → deliver → release) settle on-chain
- AMAN is the network's internal gas token — it is not a tradable or investment asset; AmanChain is not an exchange and offers no securities
- Official MCP Registry:
io.github.gitajhd/amanchain— active · Smithery:@sat-ma/amanchain - All services indexed and purchasable today — live count in
/services.json
Source: README.md at commit 37c67e1
Tools
0Version history
1- v2.28.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts