Noves MCP Server
OfficialServer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recent_transactionsA | Get recent transactions for a wallet address with natural language descriptions |
| get_transaction_detailsB | Get detailed analysis of a specific transaction with natural language description |
| get_translated_transactionA | Get human-readable description of a specific transaction using Noves translation |
| get_transaction_transfersB | Get detailed transfer information from recent transactions (focus on token movements) |
| get_wallet_summaryC | Get a comprehensive summary of wallet activity with key insights |
| analyze_walletC | Analyze wallet activity and provide insights with natural language summaries |
| get_current_token_priceC | Get current price of a token on a specific blockchain |
| get_historical_token_priceB | Get historical price of a token at a specific timestamp |
| get_token_price_comparisonA | Compare token price between two timestamps to show price change |
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 9 tools
Several tools overlap significantly: get_translated_transaction and get_transaction_details both describe a specific transaction in natural language, and get_wallet_summary and analyze_wallet both provide wallet insights. This creates ambiguity in choosing the right tool for a given task.
All tool names follow a consistent 'get_' prefix with descriptive nouns (e.g., get_recent_transactions, get_historical_token_price). The pattern is uniform and predictable across the entire set.
With 9 tools, the server is well-scoped for its domain of blockchain analytics and price lookups. Each tool targets a specific resource or operation, and the count is neither too sparse nor overwhelming.
The tool surface covers recent transactions, specific transaction details, transfers, wallet summaries, and token price data, which is comprehensive for a transaction-translation and wallet-analytics server. A minor gap is the lack of tools for token balance or blockchain-level queries, but core workflows are well represented.