mcpField
A
amanchain

amanchain

Remote
github.com/gitajhdFinance0Updated 7w ago
Repository

About amanchain

AmanChain is a proof-of-work blockchain with a marketplace of paid agent services and hybrid signatures designed to resist quantum attacks. Its remote MCP server supports service discovery and paid calls, with payments in USDC on Base or native AMAN.

Key features

  1. 01Access network and service catalog information
  2. 02Invoke services with per-call payments
  3. 03Pay in USDC on Base or native AMAN
  4. 04Use on-chain escrow for deals
  5. 05Score agents from escrow outcomes

Use cases

  1. 01Look up market data or on-chain information
  2. 02Call web, AI generation, or document services per use
  3. 03Handle agent-to-agent deals through escrow

MCP support

The remote MCP server exposes 11 tools over Streamable HTTP for network information, service discovery, market data, and paid service invocation.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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.

version MCP x402

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:

{
  "mcpServers": {
    "amanchain": {
      "url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
    }
  }
}

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:

RailStatusHow it worksBest for
USDC on Base (primary)✅ liveStandard x402: unpaid request → 402 with accepts[0] (scheme exact, network eip155:8453) → sign EIP-3009 → retry with X-PAYMENT / PAYMENT-SIGNATURE → 200 + settlement receipt. Verified & settled by the Coinbase facilitator, gasless.Any compliant x402 client — regular USDC, no AMAN needed
AMAN native (secondary)✅ live402 with price + pay-to address → sign an agent_invoke transaction (chainId 1) → broadcast → re-request with the txId → node verifies on-chain and executes.Zero third parties, on-chain settlement
Quick start (USDC on Base — @x402/fetch)
import { wrapFetchWithPayment } from '@x402/fetch';

const paid = await wrapFetchWithPayment(fetch)(
  'https://amanchain-relay.gitajhd.workers.dev/api/x402?net=mainnet',
  { method: 'POST', headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ serviceId: 'aman-price-feed', request: 'BTC' }) },
);
const result = await paid.json(); // 402 auto-handled, USDC on Base, receipt included

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)
# 1. Get the 402 payment requirements for a service
curl -s -X POST "https://amanchain-relay.gitajhd.workers.dev/api/x402?net=mainnet" \
  -H "Content-Type: application/json" \
  -d '{"serviceId":"aman-crypto-prices"}'

# 2. Pay: sign an agent_invoke transaction for the exact price and broadcast it
#    POST https://amanchain-relay.gitajhd.workers.dev/api/v1/tx

# 3. Retry with the txId - the node verifies the real on-chain payment
curl -s -X POST "https://amanchain-relay.gitajhd.workers.dev/api/x402?net=mainnet" \
  -H "Content-Type: application/json" \
  -d '{"serviceId":"aman-crypto-prices","payment":{"txId":"<your-txid>"}}'

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 in FUNDED; 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.

CategoryFlagship services
On-chain auditsToken Risk Audit , Token Supply Audit , Stablecoin Health , Token Launch Check
Market dataLive Crypto Prices (BTC/ETH/SOL/BNB/LTC) , AMAN Price Feed , OHLC History , Swap Quotes , Pool Analytics , Arbitrage Scan
Web & utilitiesLive Web Search , Fetch Web Page , RSS Reader , Domain RDAP , IP Geolocation , Weather + Forecast , FX Rates , Translate , Email Validation
AI generationAI Text Generation (LLM) , AI Image Generation (1024x1024 PNG) , Summarize , Sentiment Analysis
Network & explorerNetwork Stats , Fee & Gas Tracker , Block Inspector , Transaction Lookup , Bridge Status , Agent Roster
Business documentsInvoice PDF , Pro Forma Invoice , Payment Receipt , Credit Note , Quote & Estimate
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:

ServiceDocumentExtras
aman-invoice-pdfINVOICEdue date, notes
aman-invoice-proformaPROFORMA INVOICEvalidity date (customs / advance payment)
aman-receipt-paymentPAYMENT RECEIPTpayment method + transaction reference + paid date
aman-credit-noteCREDIT NOTEoriginal-invoice reference, negative lines allowed
aman-quote-estimateQUOTEvalidity date (devis / estimate)
POST https://amanchain-relay.gitajhd.workers.dev/api/x402?net=mainnet
{"serviceId":"aman-invoice-pdf","request":"{\"invoiceNumber\":\"INV-1\",\"buyer\":{\"name\":\"Acme\"},\"items\":[{\"description\":\"Work\",\"qty\":1,\"unitPrice\":50}],\"vatRate\":20}"}

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)

SurfaceURL
MCP endpointhttps://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet
x402 well-known (primary rail declared here)https://amanchain-relay.gitajhd.workers.dev/.well-known/x402
Agent catalog (llms.txt)https://amanchain-relay.gitajhd.workers.dev/llms.txt (also under /.well-known/llms.txt)
Agent cardhttps://amanchain-relay.gitajhd.workers.dev/.well-known/agent.json
OpenAPIhttps://amanchain-relay.gitajhd.workers.dev/openapi.json
x402 discoveryhttps://amanchain-relay.gitajhd.workers.dev/x402/discovery
Network explorer APIhttps://amanchain-relay.gitajhd.workers.dev/api/status

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.