Arc MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_balanceA | Get USDC balance of any address on Arc Testnet |
| get_transactionC | Get transaction details on Arc Testnet |
| get_blockA | Get latest block information from Arc Testnet |
| get_tx_countA | Get transaction count (nonce) for an address on Arc Testnet |
| get_agent_infoA | Get ERC-8004 agent information for the main Arc Intelligence agent |
| get_job_statusA | Get ERC-8183 job status on Arc Testnet |
| get_network_infoA | Get Arc Testnet network information and key contract addresses |
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 7 tools
Each tool targets a distinct piece of blockchain data: agent info, balance, block, job status, network info, transaction, and transaction count. Their purposes are clearly separated, leaving no ambiguity.
All tools follow a uniform `get_` + noun pattern (e.g., get_balance, get_block), making the naming predictable and easy to understand.
With 7 tools, the server is well-scoped for its purpose as a read-only blockchain explorer. This number is appropriate—neither too few to be useful nor too many to be overwhelming.
The set covers core blockchain queries: balances, blocks, transactions, network info, and agent details. However, it lacks common features like event logs, contract state queries, or search/filtering, which would make it more complete for a full blockchain explorer.