Skip to main content
Glama
santyvv1993

santyvv-data-mcp

by santyvv1993
README.md
# santyvv-data-mcp

**Market and on-chain data for AI agents.** A local (stdio) bridge to the
`santyvv-data` remote MCP server: crypto prices from several venues, token
facts, OHLC candles, market overview, DeFi TVL and wallet balances.

Eight tools, no API keys and no accounts. Two are free; the other six are paid
**per call in USDC on Base** through the [x402](https://x402.org) protocol, so
you pay for what you use and nothing else.

## Install

```bash
npx -y santyvv-data-mcp
```

You normally don't run it by hand: your MCP client starts it. Add this to your
client's config (Claude Desktop, Cursor, VS Code, Cline…):

```json
{
	"mcpServers": {
		"santyvv-data": {
			"command": "npx",
			"args": ["-y", "santyvv-data-mcp"]
		}
	}
}
```

Without any configuration the two **free** tools work right away:

| Tool             | What it gives you                                             |
| ---------------- | ------------------------------------------------------------- |
| `catalogo`       | everything for sale, its price and its parameters              |
| `estado_fuentes` | live status of every upstream source (so you know before paying) |

## Paying for the paid tools (optional)

To let the bridge pay the six paid tools automatically, give it a wallet with
USDC on Base (the bridge signs the exact amount of each call; it never sends
funds anywhere else):

```json
{
	"mcpServers": {
		"santyvv-data": {
			"command": "npx",
			"args": ["-y", "santyvv-data-mcp"],
			"env": {
				"X402_PRIVATE_KEY": "0x…",
				"X402_MAX_PRICE_USDC": "0.05"
			}
		}
	}
}
```

| Variable               | Default                        | What it does                                          |
| ---------------------- | ------------------------------ | ----------------------------------------------------- |
| `X402_PRIVATE_KEY`     | *(none)*                       | wallet that pays each call (USDC on Base)             |
| `X402_MAX_PRICE_USDC`  | `0.05`                         | refuses to pay anything above this price per call      |
| `SANTYVV_MCP_URL`      | `https://mcp.santyvv.com/mcp`  | the remote server to bridge to                         |

Paid tools, with their price per call: `precio` ($0.02), `ficha_token`
($0.03), `velas` ($0.01), `mercado` ($0.03), `tvl_protocolo` ($0.01), `saldo`
($0.03).

## Notes

- **The key stays local.** It is read from your environment, used to sign one
  payment per call and never sent anywhere else. Use a dedicated wallet with a
  small balance.
- **This package does not reimplement anything.** It asks the remote server for
  its tool list and forwards calls, so the tools, their prices and the data are
  always the ones actually served.
- **No accounts, no tracking.** No sign-up, no API keys, no cookies.
- Privacy policy: <https://mcp.santyvv.com/privacy> · HTTP API with the same
  data: <https://x402.santyvv.com/api> · Registered as `com.santyvv/tienda` in
  the official MCP Registry.

## Develop

```bash
npm install
npm run build     # bundles src/index.ts into dist/index.mjs
npm run probar    # starts the bridge over stdio and calls a free tool
npm run probar:publicado   # installs the published package from npm and runs it
```

This repository is the source of the package published to npm. The same engine also serves the
HTTP API (40 routes, same data, same per-call pricing) and is registered as `com.santyvv/tienda` in
the official MCP Registry.

MIT.

TDQS

A4/5.0

Scored across 8 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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

Maintenance

ActivityMaintained
ResponsivenessNo issues