mcp-registry/org.thru/thru-explorer · v0.1.0
As of 2026-10-21 12:53 UTC, the Thru Explorer MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.
Thru blockchain explorer: blocks, transactions, accounts, and program ABIs on the Thru RISC-V L1
Claude Code
claude mcp add --transport http thru-explorer-mcp-server https://scan.thru.org/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"thru-explorer-mcp-server": {
"type": "http",
"url": "https://scan.thru.org/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Forg.thru%2Fthru-explorer/fixes
{
"name": "get_account",
"description": "Get account details by address, including balance, owner, and metadata",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Account address"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_block",
"description": "Get block details by slot number, including producer, timestamp, and transactions",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slot"
],
"properties": {
"slot": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Block slot number"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_program_abi",
"description": "Get the on-chain ABI for a program, including instruction and event definitions",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"program"
],
"properties": {
"program": {
"type": "string",
"description": "Program address"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.thru/thru-explorer"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.thru/thru-explorer"}) over MCP.
list_account_transactions ~135 tokensget_block ~94 tokensget_transaction ~91 tokenslist_recent_transactions ~91 tokensget_program_abi ~85 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Forg.thru%2Fthru-explorer?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.thru%2Fthru-explorer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.thru%2Fthru-explorer.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.thru%2Fthru-explorer.svg :target: https://glimind.com/server/mcp-registry%2Forg.thru%2Fthru-explorer?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1720c862495e65f0…, first seen 2026-10-17, included at leaf 4929 of 39,628. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 12:53 UTC, the Thru Explorer MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.
Thru Explorer MCP server advertises 8 tools, including get_account, get_block, get_program_abi, get_transaction, list_account_transactions.
Point your MCP client at this streamable-http endpoint: https://scan.thru.org/api/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.