Veri5ight 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ethereum_getRecentTransactionsC | Get recent transactions for an Ethereum address |
| ethereum_getTokenBalanceC | Get ERC20 token balance for an address |
| ethereum_getTokenDelegationC | Get delegation info for an ERC20 governance token |
| ethereum_getContractInfoC | Get information about any contract |
| ethereum_getTransactionInfoC | Get detailed information about an Ethereum transaction |
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 5 tools
Each tool has a clearly distinct purpose targeting different Ethereum data types: contract info, recent transactions, token balance, token delegation, and transaction details. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tools follow a consistent 'ethereum_verbNoun' pattern with snake_case, using descriptive verbs like 'get' and specific nouns like 'ContractInfo' or 'TokenBalance'. This predictability enhances usability.
Five tools is a reasonable number for an Ethereum data server, covering key queries. It might be slightly thin for broader blockchain interactions, but it's well-scoped for its apparent purpose of retrieving specific Ethereum data.
The tools cover read operations for contracts, transactions, tokens, and delegation, but there are notable gaps such as write operations (e.g., sending transactions), broader blockchain state queries, or support for other token standards. Agents can work with the provided tools but may hit limitations.