Summary
Historical price at a timestamp is what makes the translation useful — knowing what moved is half an answer without knowing what it was worth then.
Transaction translation on its own is a readability improvement. Pairing it with a price lookup at the transaction's own timestamp is what lets a question like 'what did that swap actually cost me' be answered, since valuing last year's trade at today's price is the most common way these analyses go wrong. The comparison tool between two timestamps is the same idea made explicit. Read-only throughout — this reads chains and prices, and signs nothing.
What it is
A blockchain translation client: it turns transactions into human-readable descriptions, summarises wallet activity, and supplies current and historical token prices to put numbers on it.
What you get
- get_recent_transactions and get_transaction_details return natural-language descriptions rather than call data and topic hashes.
- get_translated_transaction runs one transaction through the translation specifically, and get_transaction_transfers focuses on the token movements inside it.
- get_wallet_summary and analyze_wallet produce activity summaries and insights across a wallet rather than transaction by transaction.
- Prices at three granularities: current, historical at a specific timestamp, and a comparison between two timestamps showing the change.
Requirements
Nothing to supply.
Setup effort
One command — npx @noves/noves-mcp-server@0.1.3