thru-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THRU_RPC_URL | No | Thru RPC endpoint | https://rpc.alphanet.thru.org |
| THRU_FAUCET_ACCOUNT | No | Faucet account inspected by get_faucet_status | taxoImN8…In |
| THRU_NAME_SERVICE_PROGRAM | No | Name service program address | taAAAA…UF |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Look up a Thru account by public key and return its balance, nonce, owner program, size and flags. Balances are returned as raw integer strings. |
| get_transactionA | Fetch a Thru transaction by signature. Returns consensus status, execution result, fee payer, invoked program and resource consumption. |
| resolve_nameA | Resolve a Thru name service entry to its on-chain account. Accepts a root registrar name or a |
| get_faucet_statusA | Report the on-chain Thru faucet account: its current balance and the per-transaction withdraw limit. This is read-only — Thru exposes no HTTP faucet, so actually withdrawing requires submitting a signed transaction to the faucet program with a funded fee payer (use the |
| get_network_statusA | Check the health of the configured Thru RPC endpoint: node readiness, consensus state, chain id, current block heights and component versions. |
| query_eventsA | Query events emitted by Thru programs. Fetch one event by id, list an account's recent transaction history with its emitted events, or page through the most recent events chain-wide. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource: name resolution, account, transaction, faucet, network, and events. No overlapping purposes; even the two status tools (faucet and network) are clearly separated by domain.
Five tools use the 'get_' prefix, but 'resolve_name' and 'query_events' deviate from that pattern. All follow a verb_noun structure with consistent lowercase styling, so the inconsistency is minor.
Six tools is well-scoped for a blockchain read-only server. Each tool covers a distinct domain area without unnecessary redundancy.
The set covers core read operations: accounts, transactions, names, network health, faucet state, and event queries. It lacks block-level queries and any transaction submission, but those may be intentionally excluded since withdrawal requires the CLI.