Thru Explorer MCP

org.thruPublished by thru.orgOfficial publisherv0.1.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Remote MCP server for the Thru blockchain explorer, letting an assistant look up blocks, transactions, accounts and program ABIs on the Thru RISC-V L1.

What you can do
Look up blocks by slot, including producer, timestamp and transactions, and list recent blocks or recent transactions across them. Fetch a transaction by signature with status, accounts, instructions and events, and list an account's transactions with pagination. Read account details by address, including balance, owner and metadata. Search for blocks, transactions or accounts by block number, signature or address. Retrieve a program's on-chain ABI, including instruction and event definitions.
When to use it
Useful when you need to inspect on-chain activity on the Thru network: tracing a transaction, checking an account balance or owner, browsing recent blocks, or reading a program's ABI to understand its instructions and events.
Requirements
A remote streamable HTTP endpoint at scan.thru.org; no package, environment variables or headers are declared. Network access to that endpoint is needed.
Before you install
All listed tools are read-only lookups; no writes, credentials or payments are declared. Queries go to a third-party explorer service, so search terms and addresses you submit are visible to that provider.

Installation

In SourceWeft

  1. Open Thru Explorer MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.thru%2Fthru-explorer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "thru-explorer": {
      "type": "http",
      "url": "https://scan.thru.org/api/mcp"
    }
  }
}

Tools

8

get_block

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

Parametersslotrequired

get_transaction

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

Parameterssignaturerequired

get_account

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

Parametersaddressrequired

list_account_transactions

List transactions for an account with pagination

ParametersaddressrequiredpageSizepageToken

list_recent_blocks

List the most recent blocks on the chain

Parameterslimit

list_recent_transactions

List the most recent transactions across recent blocks

Parameterslimit

get_program_abi

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

Parametersprogramrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.