Thru Explorer is an MCP server with 8 tools an agent can call, among them get_account, get_block, get_program_abi. It answers at https://scan.thru.org/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Thru blockchain explorer: blocks, transactions, accounts, and program ABIs on the Thru RISC-V L1
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_account | Get account details by address, including balance, owner, and metadata Inputs: address |
get_block | Get block details by slot number, including producer, timestamp, and transactions Inputs: slot |
get_program_abi | Get the on-chain ABI for a program, including instruction and event definitions Inputs: program |
get_transaction | Get transaction details by signature, including status, accounts, instructions, and events Inputs: signature |
list_account_transactions | List transactions for an account with pagination Inputs: address, pageSize, pageToken |
list_recent_blocks | List the most recent blocks on the chain Inputs: limit |
list_recent_transactions | List the most recent transactions across recent blocks Inputs: limit |
search | Search for blocks, transactions, or accounts by query (block number, tx signature, or address) Inputs: query |
Every block below points at https://scan.thru.org/api/mcp. Pick your client and copy.
claude mcp add --transport http thru-explorer https://scan.thru.org/api/mcp
{
"mcpServers": {
"thru-explorer": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://scan.thru.org/api/mcp"]
}
}
}{
"mcpServers": {
"thru-explorer": {
"url": "https://scan.thru.org/api/mcp"
}
}
}{
"servers": {
"thru-explorer": {
"type": "http",
"url": "https://scan.thru.org/api/mcp"
}
}
}{
"context_servers": {
"thru-explorer": {
"url": "https://scan.thru.org/api/mcp"
}
}
}{
"mcpServers": {
"thru-explorer": {
"serverUrl": "https://scan.thru.org/api/mcp"
}
}
}{
"mcpServers": {
"thru-explorer": {
"url": "https://scan.thru.org/api/mcp"
}
}
}name: Thru Explorer
version: 0.0.1
schema: v1
mcpServers:
- name: Thru Explorer
type: streamable-http
url: https://scan.thru.org/api/mcp{
"mcpServers": {
"thru-explorer": {
"httpUrl": "https://scan.thru.org/api/mcp"
}
}
}{
"mcpServers": {
"thru-explorer": {
"type": "http",
"url": "https://scan.thru.org/api/mcp"
}
}
}{
"mcpServers": {
"thru-explorer": {
"url": "https://scan.thru.org/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fscan.thru.org%2Fapi%2Fmcp&type=streamable_http&id=thru-explorer&name=Thru%20Explorer
It answered our last check on 24 October 2026 in 203 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by thru.org and served from scan.thru.org, the vendor's own domain: https://scan.thru.org/api/mcp.
8, as returned by the server's own tools/list on 23 September 2026: get_account, get_block, get_program_abi, get_transaction, list_account_transactions, list_recent_blocks, list_recent_transactions, search.
It answered our last check on 24 October 2026 in 203 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://scan.thru.org/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: org.thru. Endpoint host: scan.thru.org. ARD identifier: urn:air:org.thru:mcp:thru-explorer.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.