io.github.gitajhd/amanchain
REMOTE · AMANCHAIN-RELAY.GITAJHD.WORKERS.DEV · SCANNED SEP 29
AmanChain: quantum-resistant x402 payments. Remote MCP, 50 paid services. USDC on Base or AMAN.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 536 tokens (~48/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.gitajhd/amanchain MCP server?
io.github.gitajhd/amanchain is a hosted endpoint at https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · amanchain-relay.gitajhd.workers.dev
claude mcp add --transport http gitajhd-amanchain 'https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet'
{
"mcpServers": {
"gitajhd-amanchain": {
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
} {
"servers": {
"gitajhd-amanchain": {
"type": "http",
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
} [mcp_servers.gitajhd-amanchain] url = "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gitajhd-amanchain": {
"type": "remote",
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet",
"enabled": true
}
}
} openclaw mcp add gitajhd-amanchain --url 'https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet' --transport streamable-http
mcp_servers:
gitajhd-amanchain:
url: "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet" {
"McpServers": {
"gitajhd-amanchain": {
"Transport": "http",
"Url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
} assistant mcp add gitajhd-amanchain -t streamable-http -u 'https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet'
{
"mcpServers": {
"gitajhd-amanchain": {
"type": "http",
"url": "https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gitajhd.workers.dev | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 14e9d5ee4f9368e30ed57e5b7ed83d36 |
| SANs: gitajhd.workers.dev, *.gitajhd.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of amanchain-relay.gitajhd.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https: wss:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet | Verified | 200 | |
| http (plaintext) | http://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aman_autopilot_status ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aman_chain_info ~27
Live AmanChain network info: height, difficulty, supply, burns, agent economy stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aman_get_tx ~35
Fetch a transaction by id (mined or pending) including its quantum-shield fingerprint.
| Name | Type | Req | Description |
|---|---|---|---|
| txId | string | yes | – |
No output schema declared.
No examples provided.
aman_invoke_history ~23
Recent x402 paid calls between agents (the autonomous economy tape).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aman_invoke_service ~119
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).
| Name | Type | Req | Description |
|---|---|---|---|
| payTxId | string | – | Transaction id of the agent_invoke payment (step 2 of x402) |
| request | string | – | Request payload, e.g. a token symbol for the audit service |
| serviceId | string | yes | Service handle from aman_list_services |
No output schema declared.
No examples provided.
aman_list_services ~53
List the on-chain AI agent marketplace: every service with its x402 per-call price, provider, calls and volume.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Optional capability filter, e.g. pricing, audit, market-data |
No output schema declared.
No examples provided.
aman_market ~29
DEX snapshot: pools with real reserves, prices, 24h volume and the latest executed swaps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aman_price ~29
Live AMAN price from the deepest real AMM pool, with 24h change and TVL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aman_service_catalog ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional keyword/capability filter, e.g. "audit" or "portfolio" |
No output schema declared.
No examples provided.
aman_token ~44
AMT-20 token detail: supply, holders, stable collateral backing, pool depth, governance flags.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Token symbol, e.g. USDT |
No output schema declared.
No examples provided.
aman_tokens ~19
All visible AMT-20 tokens on this network.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.gitajhd/amanchain MCP server?
io.github.gitajhd/amanchain is an MCP server listed in the public MCP registry as io.github.gitajhd/amanchain. AmanChain: quantum-resistant x402 payments. Remote MCP, 50 paid services. USDC on Base or AMAN. This page covers its hosted endpoint (https://amanchain-relay.gitajhd.workers.dev/api/mcp?net=mainnet).
Is the io.github.gitajhd/amanchain MCP server safe to use?
io.github.gitajhd/amanchain scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.gitajhd/amanchain MCP server expose?
io.github.gitajhd/amanchain exposes 11 tools: aman_chain_info, aman_price, aman_list_services, aman_invoke_service, aman_token, and 6 more. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.
Does the io.github.gitajhd/amanchain MCP server require authentication?
No. We connected to io.github.gitajhd/amanchain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.gitajhd/amanchain MCP server still maintained?
io.github.gitajhd/amanchain is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.