_ registry / mcp streamable-http · checked 17h 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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
308ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ 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 open 17h 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 open 17h 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 unknown never probed

    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
  • get_block unknown never probed

    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 unknown never probed

    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 unknown never probed

    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 unknown never probed

    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
  • search unknown never probed

    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
_ 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.

_ 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)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.