santyvv-data — market & on-chain data
REMOTE · MCP.SANTYVV.COM · 2 COMPONENTS
Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).
Available components
Last scanned (16 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Crypto and Web3
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 22 Oct 26 0
- DNSSEC: fail → pass ▲ security
- 21 Oct 26 0
- HTTPS: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 28 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
- 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
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 22 Nov 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 | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 3455d5e9db1186270edce8b6fa8cea41 |
| 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 secure
Validation of mcp.santyvv.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| santyvv.com. | DS published | 2371 | 13 | Verified |
| mcp.santyvv.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=() |
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 | HTTPS enforced | 301 | https://mcp.santyvv.com/mcp |
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 →
catalogo Service catalogue ~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 Upstream source status ~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 Token profile and price ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Network the token lives on. (por defecto: base) |
| tokens | string | yes | Comma-separated contract addresses, up to 10. Example: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
No output schema declared.
No examples provided.
mercado Market overview ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | How many coins to return in the market-cap list. (por defecto: 20) |
| vs | string | – | Quote currency. (por defecto: usd) |
No output schema declared.
No examples provided.
precio Market price ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| symbols | string | – | Comma-separated symbols, up to 20. Example: BTC,ETH,SOL (por defecto: BTC) |
No output schema declared.
No examples provided.
saldo Wallet balance ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 20-byte address (0x followed by 40 hex characters). |
| chain | string | – | Network to query. (por defecto: base) |
| token | string | yes | Optional: ERC-20 token contract (USDC on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). |
No output schema declared.
No examples provided.
tvl_protocolo DeFi protocol TVL ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | – | DeFiLlama protocol identifier. Example: aave (por defecto: aave) |
No output schema declared.
No examples provided.
velas OHLC candles ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Size of each candle. (por defecto: 1h) |
| limite | integer | – | How many candles to return. (por defecto: 100) |
| symbol | string | yes | Pair to query. Example: BTCUSDT |
No output schema declared.
No examples provided.
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
claude mcp add --transport http com-santyvv-tienda 'https://mcp.santyvv.com/mcp'
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 90 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 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the santyvv-data — market & on-chain data MCP server?
VerifyMCP ran 13 checks on santyvv-data — market & on-chain data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.