_ registry / mcp streamable-http · checked 42m ago

agentindex

https://mcp-agentindex.craftyour.site

Registry code: d4122b6b404d1e81

api record

Trust scores and on-chain payment receipts for x402 services.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp-agentindex.craftyour.site/mcp
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
0 · newcomer
_ is it live, free and safe measured by this hub
Is agentindex live?
No — it has stopped answering the hub's checks (checked 42m ago). It answered 89% of checks over the last 30 days.
Is agentindex free to use?
Yes — the hub reached it with no key and no payment.
What tools does agentindex have?
4 tools: check_trust, find_service, resolve_data_need, get_verified_data.
Is agentindex 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
down
uptime, 30 days
89.3%

90 days 93%· all time 93%

latency
396ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 356 checks · signed record
  • degraded → down· HTTP 502
  • live → degraded· HTTP 502
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check an x402 service's trust score
  • find an x402 service for a need
  • get data from the most trusted service
takes → gives
text → data
tools
3 reads1 moves money
_ 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

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

  • get_verified_data moves money open 4d ago

    One call: pick the most-trusted service for a need, fetch the data from it, and return the data together with that provider's trust score and its latest on-chain probe receipt as proof. Use when you want the answer AND a record of why the source was trusted. Scam / low-trust providers are never selected.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "description": "The data you want, e.g. \"current ETH price\" or \"weather in Singapore\""
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • check_trust reads unknown 4d ago

    Full trust report for one service: score, delivery/honesty rates, latency, and recent probes with chain-aware payment receipts. Accepts a label ("weatherpro") or full name ("weatherpro.agentindex.eth").

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Service label or ENS name"
        },
        "probes": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "How many recent probes to include"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • find_service reads unknown 4d ago

    Search the AgentIndex registry for x402 services matching a capability, e.g. "weather data" or "token prices". Returns matching services with endpoints, prices and their probed trust scores.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "description": "What the service should do, in plain words"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • resolve_data_need reads unknown never probed

    End-to-end selection: describe a task, get back the single best service to pay (plus ranked alternatives and any services to avoid). Use this before spending money over x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "task"
      ],
      "properties": {
        "task": {
          "type": "string",
          "description": "The task, e.g. \"get current weather for Singapore\""
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 d4122b6b404d1e81.

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

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.