santyvv-data-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SANTYVV_MCP_URL | No | The URL of the remote MCP server to bridge to. | https://mcp.santyvv.com/mcp |
| X402_PRIVATE_KEY | No | Wallet private key that pays each call (USDC on Base). Optional; required to use the paid tools. | |
| X402_MAX_PRICE_USDC | No | Maximum price per call in USDC that the bridge will pay. Defaults to 0.05. | 0.05 |
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 |
|---|---|
| catalogoA | What can be ordered, at what price and under what name. Includes this MCP server's tools and the equivalent HTTP routes. Free. |
| estado_fuentesA | Live probe of every public source behind the data (response, HTTP status and latency). Free: use it to decide whether a paid call is worth it, and to see where a number came from. |
| precioA | What an asset is worth right now, in USD, as a MEDIAN across several venues with its spread - not a single exchange's last trade. Use it to quote, to compare venues or to spot a dislocated market. Cuesta $0.02 por llamada, en USDC sobre Base (protocolo x402). |
| ficha_tokenA | What a token is and what it is worth: name, symbol, decimals, supply, contract address and price per token. Use it to confirm that an address is a real contract and what it represents. Cuesta $0.03 por llamada, en USDC sobre Base (protocolo x402). |
| velasA | Recent candles for a trading pair at the interval you ask for (1m to 1d). What you need to compute trend or volatility, or to draw a chart without an exchange API key. Cuesta $0.01 por llamada, en USDC sobre Base (protocolo x402). |
| mercadoA | The big picture: total market cap, Bitcoin dominance, 24 h change, the coins by market cap and the top movers. This is the context question, not the one about a single asset. Cuesta $0.03 por llamada, en USDC sobre Base (protocolo x402). |
| tvl_protocoloA | How much money is deposited in a DeFi protocol (TVL in USD) with its 24 h and 7 day change. The measure of a protocol's size and health before you interact with it. Cuesta $0.01 por llamada, en USDC sobre Base (protocolo x402). |
| saldoA | What an address holds: the native balance of the network and, if you pass a token, that ERC-20 balance with its decimals. Use it to verify a payment or a holding without opening a block explorer. Cuesta $0.03 por llamada, en USDC sobre Base (protocolo x402). |
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 8 tools
Most tools map cleanly to one resource (market overview, candles, TVL, balances, source health), but `precio` and `ficha_token` both return a current price and `mercado` also includes price context, so an agent needs to read descriptions carefully to pick the right one.
All eight names are lowercase, underscore-separated, and follow a consistent noun-led pattern such as `precio`, `velas`, `ficha_token`, and `tvl_protocolo`. The mix of Spanish and English financial terms like `token` and `tvl` is minor and does not break the naming convention.
Eight tools is a well-scoped count for a read-only crypto and market-data server. Each tool covers a distinct data product, and the two free meta tools provide useful discovery and source-health context without bloating the surface.
The core read-only domain is well covered: market overview, asset price, candles, token metadata, protocol TVL, and wallet balances. The main gaps are the lack of a direct token-search/discovery tool and transaction-level data, but agents can work around these using `mercado` and `saldo`.