Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hermes Agent Data Services (x402)

REMOTE · X402-AGENT.MAJIGHUFRON.WORKERS.DEV · SCANNED SEP 25

On-chain data for agents: token reports, contract DD, pool risk, wallet profile - USDC per call.

59 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 462 tokens (~92/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Hermes Agent Data Services (x402) MCP server?

Hermes Agent Data Services (x402) is a hosted endpoint at https://x402-agent.majighufron.workers.dev/mcp, 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 · x402-agent.majighufron.workers.dev

# add to Claude Code
claude mcp add --transport http ajighufron9999-x402-agent-data 'https://x402-agent.majighufron.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ajighufron9999-x402-agent-data": {
      "url": "https://x402-agent.majighufron.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ajighufron9999-x402-agent-data": {
      "type": "http",
      "url": "https://x402-agent.majighufron.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ajighufron9999-x402-agent-data]
url = "https://x402-agent.majighufron.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ajighufron9999-x402-agent-data": {
      "type": "remote",
      "url": "https://x402-agent.majighufron.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ajighufron9999-x402-agent-data --url 'https://x402-agent.majighufron.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ajighufron9999-x402-agent-data:
    url: "https://x402-agent.majighufron.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ajighufron9999-x402-agent-data": {
      "Transport": "http",
      "Url": "https://x402-agent.majighufron.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ajighufron9999-x402-agent-data -t streamable-http -u 'https://x402-agent.majighufron.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "ajighufron9999-x402-agent-data": {
      "type": "http",
      "url": "https://x402-agent.majighufron.workers.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 +1
    • 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 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Sept 26 58

    First indexed and scored.

Diagnostics

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 25 Sept 2026 · Probed https://x402-agent.majighufron.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=majighufron.workers.dev CN=WE1,O=Google Trust Services,C=US 2 Sept 2026 1 Dec 2026 ECDSA 256 ECDSA-SHA256 d497649a96bb5bed0e76fff00b29d1ee
SANs: majighufron.workers.dev, *.majighufron.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 x402-agent.majighufron.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402-agent.majighufron.workers.dev/mcp Verified 200
http (plaintext) http://x402-agent.majighufron.workers.dev/mcp Served over HTTP 200
MCP tools · 5 exposed · ~424 tokens

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 →

Tool Tokens
contract_dd ~79

Due-diligence signals for a token contract: risky selectors found in bytecode, owner and renounced status, transfer activity. Signals to investigate, not a verdict. Price 0.05 USDC.

NameTypeReqDescription
blocksnumber––
chainstring––
payment_signaturestring––
tokenstringyes–

No output schema declared.

No examples provided.

pool_risk ~105

Pool depth, implied price and constant-product slippage for a trade size. Price 0.02 USDC.

NameTypeReqDescription
basestringyestoken you would sell
chainstring––
notionalstring–amount of base token to sell (default 1000)
payment_signaturestring––
poolstringyesaddress holding both tokens (the AMM pool contract)
quotestringyestoken you would receive

No output schema declared.

No examples provided.

service_catalog ~27

Free: list the paid data services, their prices, the payment network and the receiving wallet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

token_report ~138

ERC-20 on-chain report (metadata, supply, transfer activity, optional pool depth). Chains: base, base-sepolia, robinhood. Price 0.01 USDC — pay first, then pass payment_signature.

NameTypeReqDescription
blocksnumber–log window in blocks (default 300)
chainstring–chain to read data from
payment_signaturestring–base64 of {"txHash":"0x…"} of your USDC transfer to payTo on Base
poolstring–optional pool address to report its token balance
tokenstringyestoken contract address 0x…

No output schema declared.

No examples provided.

wallet_profile ~75

Activity profile for one address on one token: transfers in/out, distinct counterparties, first and last block seen. Price 0.03 USDC.

NameTypeReqDescription
addressstringyes–
blocksnumber––
chainstring––
payment_signaturestring––
tokenstringyes–

No output schema declared.

No examples provided.

Common questions

What is the Hermes Agent Data Services (x402) MCP server?

Hermes Agent Data Services (x402) is an MCP server listed in the public MCP registry as io.github.AjiGhufron9999/x402-agent-data. On-chain data for agents: token reports, contract DD, pool risk, wallet profile - USDC per call. This page covers its hosted endpoint (https://x402-agent.majighufron.workers.dev/mcp).

Is the Hermes Agent Data Services (x402) MCP server safe to use?

Hermes Agent Data Services (x402) scores 59 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 Hermes Agent Data Services (x402) MCP server expose?

Hermes Agent Data Services (x402) exposes 5 tools: service_catalog, token_report, contract_dd, pool_risk, wallet_profile. Their descriptions and schemas cost roughly 424 tokens of context every time the server is loaded.

Does the Hermes Agent Data Services (x402) MCP server require authentication?

No. We connected to Hermes Agent Data Services (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hermes Agent Data Services (x402) MCP server still maintained?

Hermes Agent Data Services (x402) is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.