Developer Tools
thru.org
Provides blockchain querying capabilities for blocks, transactions, and accounts to support development and analysis.
ENDPOINT 1
https://scan.thru.org/api/mcp
MCP server metadata
- Name
- thru-explorer
- Version
- 0.1.0
Known tools 8
get_blockGet block details by slot number, including producer, timestamp, and transactions
Inferred read-onlyget_transactionGet transaction details by signature, including status, accounts, instructions, and events
Inferred read-onlysearchSearch for blocks, transactions, or accounts by query (block number, tx signature, or address)
Inferred read-onlyget_program_abiGet the on-chain ABI for a program, including instruction and event definitions
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.thru-explorer]
url = "https://scan.thru.org/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"thru-explorer": {
"type": "http",
"url": "https://scan.thru.org/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: thru-explorer
Remote MCP URL: https://scan.thru.org/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"thru-explorer": {
"url": "https://scan.thru.org/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"thru-explorer": {
"type": "http",
"url": "https://scan.thru.org/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "thru-explorer",
"transport": "streamable-http",
"url": "https://scan.thru.org/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.