Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AmanChain: quantum-resistant x402 payments. Remote MCP, 50 paid services. USDC on Base or AMAN.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnetRun this in your terminal
claude mcp add --transport http amanchain 'https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet'Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"amanchain": {
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"amanchain": {
"type": "http",
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnetMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account gitajhd, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (2.28.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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).
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.
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.
Two payment rails — primary: USDC on Base, secondary: native AMAN:
| Rail | Status | How it works | Best for |
|---|---|---|---|
| USDC on Base (primary) | ✅ live | Standard 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) | ✅ live | 402 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 |
@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.
# 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"}'
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":" "}}'
Every deal between agents can run through native escrow, mined into blocks:
FUNDED)DELIVERED — proof only, not payment)SETTLED), or a refund resolves it (provider-initiated any time in FUNDED; buyer after SLA)The first full cycles are settled on-chain with balances matching to the atomic unit.
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.
Full live catalog with per-call prices: [`/llms.txt`](https://amanchain-relay.gitajhd.workers.dev/llms.txt) (machine-readable, prices update with the AMAN AMM) or [`/services.json`](https://amanchain-relay.gitajhd.workers.dev/services.json). Entry prices start around $0.001 per call.
| Category | Flagship services |
|---|---|
| On-chain audits | Token Risk Audit , Token Supply Audit , Stablecoin Health , Token Launch Check |
| Market data | Live Crypto Prices (BTC/ETH/SOL/BNB/LTC) , AMAN Price Feed , OHLC History , Swap Quotes , Pool Analytics , Arbitrage Scan |
| Web & utilities | Live Web Search , Fetch Web Page , RSS Reader , Domain RDAP , IP Geolocation , Weather + Forecast , FX Rates , Translate , Email Validation |
| AI generation | AI Text Generation (LLM) , AI Image Generation (1024x1024 PNG) , Summarize , Sentiment Analysis |
| Network & explorer | Network Stats , Fee & Gas Tracker , Block Inspector , Transaction Lookup , Bridge Status , Agent Roster |
| Business documents | Invoice PDF , Pro Forma Invoice , Payment Receipt , Credit Note , Quote & Estimate |
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:
| Service | Document | Extras |
|---|---|---|
aman-invoice-pdf | INVOICE | due date, notes |
aman-invoice-proforma | PROFORMA INVOICE | validity date (customs / advance payment) |
aman-receipt-payment | PAYMENT RECEIPT | payment method + transaction reference + paid date |
aman-credit-note | CREDIT NOTE | original-invoice reference, negative lines allowed |
aman-quote-estimate | QUOTE | validity 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.
| Surface | URL |
|---|---|
| MCP endpoint | https://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 card | https://amanchain-relay.gitajhd.workers.dev/.well-known/agent.json |
| OpenAPI | https://amanchain-relay.gitajhd.workers.dev/openapi.json |
| x402 discovery | https://amanchain-relay.gitajhd.workers.dev/x402/discovery |
| Network explorer API | https://amanchain-relay.gitajhd.workers.dev/api/status |
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.
io.github.gitajhd/amanchain — active · Smithery: @sat-ma/amanchain/services.json