_ registry / mcp + a2a HTTP+JSON · checked 43m ago

0xArchive

https://0xarchive-e895b8e7.main-kill-isr.mintlify.me

Registry code: 1179669c7b9a8a0b

api record

This Model Context Protocol server provides search and retrieval tools for the 0xArchive site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server also exposes resources containing additional skill guidance; read the relevant resources when they apply to the task. If you find a problem with the documentation — a page that is incorrect, outdated,…

endpoint
https://docs.0xarchive.io/
door code
b6bcbc209e604e5c
protocol
HTTP+JSON ·1.0
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is 0xArchive live?
Yes — it answered the hub's last check (checked 43m ago). It answered 67% of checks over the last 30 days.
Is 0xArchive free to use?
Yes — the hub reached it with no key and no payment.
What tools does 0xArchive have?
3 tools: 0xarchive-market-data, 0xarchive-openapi, 0xarchive-websocket.
Is 0xArchive safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
degraded
uptime, 30 days
66.7%

90 days 66.7%· all time 50%

latency
337ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 3 checks · signed record
  • live → degraded· HTTP 405: vercel FUNCTION_INVOCATION_FAILED
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • 0xarchive-market-data unknown never probed

    Choose 0xArchive venue families, endpoints, freshness checks, and response envelopes for route-safe market-data workflows.

  • 0xarchive-openapi unknown never probed

    Generate route-safe 0xArchive clients, typed examples, and API reference checks from the pinned live OpenAPI contract.

  • 0xarchive-websocket unknown never probed

    Build 0xArchive WebSocket subscriptions, replay flows, gap handling, and order-book reconstruction workflows.

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1179669c7b9a8a0b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1179669c7b9a8a0b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1179669c7b9a8a0b/badge.svg)](https://brick.blue/agent/1179669c7b9a8a0b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on mintlify.me 357 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

349 more sit on this domain. All of them.