Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

santyvv-data — market & on-chain data

REMOTE · MCP.SANTYVV.COM · 2 COMPONENTS · SCANNED SEP 25

Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).

63 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 808 tokens (~101/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the santyvv-data — market & on-chain data MCP server?

santyvv-data — market & on-chain data is a hosted endpoint at https://mcp.santyvv.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.santyvv.com

# add to Claude Code
claude mcp add --transport http com-santyvv-tienda 'https://mcp.santyvv.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-santyvv-tienda": {
      "url": "https://mcp.santyvv.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-santyvv-tienda": {
      "type": "http",
      "url": "https://mcp.santyvv.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-santyvv-tienda]
url = "https://mcp.santyvv.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-santyvv-tienda": {
      "type": "remote",
      "url": "https://mcp.santyvv.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-santyvv-tienda --url 'https://mcp.santyvv.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-santyvv-tienda:
    url: "https://mcp.santyvv.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-santyvv-tienda": {
      "Transport": "http",
      "Url": "https://mcp.santyvv.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-santyvv-tienda -t streamable-http -u 'https://mcp.santyvv.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-santyvv-tienda": {
      "type": "http",
      "url": "https://mcp.santyvv.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 0
    • Tool “estado_fuentes” rewrote its description, which is the text the model reads security
    • Tool “ficha_token” rewrote its description, which is the text the model reads security
    • Tool “mercado” rewrote its description, which is the text the model reads security
    • Tool “precio” rewrote its description, which is the text the model reads security
    • Tool “saldo” rewrote its description, which is the text the model reads security
    • Tool “tvl_protocolo” rewrote its description, which is the text the model reads security
    • Tool “velas” rewrote its description, which is the text the model reads security
    • Tool “catalogo” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “ficha_token” reworded the description of “chain” cosmetic
    • “ficha_token” reworded the description of “tokens” cosmetic
    • “mercado” reworded the description of “limite” cosmetic
    • “mercado” reworded the description of “vs” cosmetic
    • “precio” reworded the description of “symbols” cosmetic
    • “saldo” reworded the description of “address” cosmetic
    • “saldo” reworded the description of “chain” cosmetic
    • “saldo” reworded the description of “token” cosmetic
    • “tvl_protocolo” reworded the description of “protocol” cosmetic
    • “velas” reworded the description of “interval” cosmetic
    • “velas” reworded the description of “limite” cosmetic
    • “velas” reworded the description of “symbol” cosmetic
    • Tool “estado_fuentes” changed its title: Estado de las fuentes → Upstream source status cosmetic
    • Tool “ficha_token” changed its title: Ficha de un token → Token profile and price cosmetic
    • Tool “mercado” changed its title: Como esta el mercado → Market overview cosmetic
    • Tool “precio” changed its title: Precio de mercado → Market price cosmetic
    • Tool “saldo” changed its title: Saldo de una direccion → Wallet balance cosmetic
    • Tool “tvl_protocolo” changed its title: Dinero en un protocolo DeFi → DeFi protocol TVL cosmetic
    • Tool “velas” changed its title: Velas (OHLC) de un par → OHLC candles cosmetic
    • Tool “catalogo” changed its title: Catalogo de la tienda → Service catalogue cosmetic
  • 20 Sept 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://mcp.santyvv.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=santyvv.com CN=WE1,O=Google Trust Services,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA256 a066d7f456083481387925ed6e04ac4
SANs: santyvv.com, mcp.santyvv.com, *.mcp.santyvv.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.santyvv.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
santyvv.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.santyvv.com/mcp Verified 200
http (plaintext) http://mcp.santyvv.com/mcp Inconclusive 406
MCP tools · 8 exposed · ~808 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
catalogo ~35

What can be ordered, at what price and under what name. Includes this MCP server's tools and the equivalent HTTP routes. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

estado_fuentes ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ficha_token ~137

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).

NameTypeReqDescription
chainstring–Network the token lives on. (por defecto: base)
tokensstringyesComma-separated contract addresses, up to 10. Example: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

No output schema declared.

No examples provided.

mercado ~107

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).

NameTypeReqDescription
limiteinteger–How many coins to return in the market-cap list. (por defecto: 20)
vsstring–Quote currency. (por defecto: usd)

No output schema declared.

No examples provided.

precio ~103

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).

NameTypeReqDescription
symbolsstring–Comma-separated symbols, up to 20. Example: BTC,ETH,SOL (por defecto: BTC)

No output schema declared.

No examples provided.

saldo ~156

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).

NameTypeReqDescription
addressstringyes20-byte address (0x followed by 40 hex characters).
chainstring–Network to query. (por defecto: base)
tokenstringyesOptional: ERC-20 token contract (USDC on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).

No output schema declared.

No examples provided.

tvl_protocolo ~98

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).

NameTypeReqDescription
protocolstring–DeFiLlama protocol identifier. Example: aave (por defecto: aave)

No output schema declared.

No examples provided.

velas ~123

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).

NameTypeReqDescription
intervalstring–Size of each candle. (por defecto: 1h)
limiteinteger–How many candles to return. (por defecto: 100)
symbolstringyesPair to query. Example: BTCUSDT

No output schema declared.

No examples provided.

Common questions

What is the santyvv-data — market & on-chain data MCP server?

santyvv-data — market & on-chain data is an MCP server listed in the public MCP registry as com.santyvv/tienda. Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402). This page covers its hosted endpoint (https://mcp.santyvv.com/mcp).

Is the santyvv-data — market & on-chain data MCP server safe to use?

santyvv-data — market & on-chain data scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the santyvv-data — market & on-chain data MCP server expose?

santyvv-data — market & on-chain data exposes 8 tools: catalogo, estado_fuentes, precio, ficha_token, velas, and 3 more. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.

Does the santyvv-data — market & on-chain data MCP server require authentication?

No. We connected to santyvv-data — market & on-chain data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the santyvv-data — market & on-chain data MCP server still maintained?

santyvv-data — market & on-chain data is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.