_ registry / mcp streamable-http · checked 1h ago

blockchainiq-x402-remote

https://www.blockchainiq.co

Registry code: 61575b1e440ec69d

api record

Blockchain IQ pay-per-call crypto data over x402 (USDC on Base or Solana). list_endpoints shows the catalogue free. call_endpoint returns free data, or the payment requirements for a paid resource. This server holds no wallet and never pays: pay with your own x402 client and call again with the signed payload in `payment`. Market data and analysis, not investment advice.

endpoint
https://www.blockchainiq.co/api/mcp
door code
d27d255530dfb84e
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is blockchainiq-x402-remote live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is blockchainiq-x402-remote free to use?
Yes — the hub reached it with no key and no payment.
What tools does blockchainiq-x402-remote have?
2 tools: call_endpoint, list_endpoints.
Is blockchainiq-x402-remote 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
274ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 124 checks · signed record
  • degraded → live
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 27 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
74

distinct

settlements
315

last 2026-11-22

received on chain
1074.47 USDC

concentrated

_ what it can do 2 tools
1 open 1 never probed 1 of 2 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.

  • list_endpoints open 12h ago

    Free. Lists every resource Blockchain IQ sells per call over x402 (USDC on Base, or on Solana): id, path, price, what it returns and its parameters. Use the id with call_endpoint. Optional free_only=true keeps only resources that cost nothing.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "free_only": {
          "type": "boolean",
          "description": "Only resources that need no payment."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • call_endpoint unknown 12h ago

    Calls one catalogue resource with a plain GET. A free resource returns its data. A paid one returns the x402 payment requirements (HTTP 402: price, network, asset, payTo) and is NOT paid by this server, which holds no wallet. To buy: pay with your own x402 client, then call again with the signed payload in `payment`. Nothing is charged unless the data is delivered.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "enum": [
            "catalog",
            "sample",
            "free-dashboards",
            "free-dashboard",
            "macro",
            "calendar",
            "indices",
            "dashboard",
            "dashboard-panel",
            "dashboard-section",
            "brief",
            "event-risk",
            "network",
            "networks",
            "stablecoins",
            "stablecoin-events",
            "stablecoin-history",
            "x402-market",
            "x402-seller-history",
            "analyst-pack",
            "reports-index",
            "reports-digest",
            "report-ripple-review",
            "report-liquidation-levels",
            "research-index",
            "research-digest",
            "research",
            "dispatch-index",
            "dispatch-bis-review",
            "dispatch-charter-race",
            "dispatch-sec-v-ripple",
            "dispatch-governance",
            "dispatch-ondo-blackrock",
            "dispatch-x402-market",
            "glossary"
          ],
          "type": "string",
          "description": "Resource id from list_endpoints."
        },
        "query": {
          "type": "object",
          "description": "Query-string parameters named in the resource's params.",
          "additionalProperties": {
            "type": [
              "string",
              "number",
              "boolean"
            ]
          }
        },
        "payment": {
          "type": "string",
          "description": "Optional. The base64 x402 payment payload YOUR client signed for this exact request; forwarded as the PAYMENT-SIGNATURE header."
        },
        "pathParams": {
          "type": "object",
          "description": "Values for {placeholders} in the resource path, e.g. {\"chain\":\"ethereum\"}. Letters, digits, dot, dash, underscore.",
          "additionalProperties": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    }
    arguments 72 lines
_ try it 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 61575b1e440ec69d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/61575b1e440ec69d/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/61575b1e440ec69d/badge.svg)](https://brick.blue/agent/61575b1e440ec69d?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 know
card completeness
60%

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.