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

thru-explorer

https://scan.thru.org

Registry code: 67fbee876929a69c

api record

Thru blockchain explorer: blocks, transactions, accounts, and program ABIs on the Thru RISC-V L1

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

endpoint
https://scan.thru.org/api/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 thru-explorer live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is thru-explorer free to use?
Yes — the hub reached it with no key and no payment.
What tools does thru-explorer have?
8 tools: get_account, search, get_block, get_program_abi, get_transaction, list_account_transactions, list_recent_blocks, list_recent_transactions.
Is thru-explorer 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
98.3%

90 days 98.9%· all time 98.9%

latency
497ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 376 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain onchain analytics
used for
  • look up a block on the thru chain
  • get a transaction by signature
  • get account balance and transactions
  • get a program abi
takes → gives
text → data
tools
8 reads
_ 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 8 tools
2 open 6 never probed 2 of 8 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_recent_blocks reads open 14h ago

    List the most recent blocks on the chain

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Number of blocks to return (1-50, default 10)"
    }
  }
}
    arguments 12 lines
  • list_recent_transactions reads open 14h ago

    List the most recent transactions across recent blocks

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Number of transactions to return (1-50, default 10)"
    }
  }
}
    arguments 12 lines
  • get_account reads unknown 8h ago

    Get account details by address, including balance, owner, and metadata

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Account address"
    }
  }
}
    arguments 13 lines
  • search reads unknown 8h ago

    Search for blocks, transactions, or accounts by query (block number, tx signature, or address)

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query"
    }
  }
}
    arguments 13 lines
  • get_block reads unknown 14h ago

    Get block details by slot number, including producer, timestamp, and transactions

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slot"
  ],
  "properties": {
    "slot": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Block slot number"
    }
  }
}
    arguments 15 lines
  • get_program_abi reads unknown 10h ago

    Get the on-chain ABI for a program, including instruction and event definitions

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "program"
  ],
  "properties": {
    "program": {
      "type": "string",
      "description": "Program address"
    }
  }
}
    arguments 13 lines
  • get_transaction reads unknown 10h ago

    Get transaction details by signature, including status, accounts, instructions, and events

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "signature"
  ],
  "properties": {
    "signature": {
      "type": "string",
      "description": "Transaction signature"
    }
  }
}
    arguments 13 lines
  • list_account_transactions reads unknown 10h ago

    List transactions for an account with pagination

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "description": "Account address"
    },
    "pageSize": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Number of transactions per page (1-100, default 10)"
    },
    "pageToken": {
      "type": "string",
      "description": "Pagination token for next page"
    }
  }
}
    arguments 23 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 67fbee876929a69c.

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

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.