Overview
Pond3r provides a Model Context Protocol (MCP) server that lets AI agents query curated crypto datasets directly. The server uses Streamable HTTP transport, so it works with Claude Desktop, Claude Code, Cursor, and any MCP-compatible client.Getting Your API Key
Create an account
Sign up at makeit.pond3r.xyz if you haven’t already.
Generate an API key
Go to makeit.pond3r.xyz/api-keys and generate a new key.
Setup with Claude Code
Run this command in your terminal to add the Pond3r MCP server:Setup with Claude Desktop
Add the following to your Claude Desktop MCP configuration file (claude_desktop_config.json):
Setup with Cursor
In Cursor, go to Settings > MCP Servers and add a new server:- URL:
https://mcp.pond3r.xyz/mcp - Headers:
Authorization: Bearer your_api_key_here
Setup with Other Clients
For any MCP-compatible client that supports Streamable HTTP transport, send POST requests to:Authorization header:
Available Tools
Once connected, your AI agent has access to three tools:| Tool | Description |
|---|---|
list_datasets | List all available datasets and their tables |
get_schema | Get column names, types, and descriptions for a dataset |
query | Execute a read-only SQL query against a dataset |
Query Tool
Thequery tool executes read-only SQL against Pond3r datasets. A few things to note:
- SELECT only — write operations are not allowed.
- Use bare table names — e.g.
SELECT * FROM stablecoin_yields, not fully qualified paths. - Results are capped at 10,000 rows — use
LIMITorWHEREfilters for large datasets. - Cost is estimated before execution — queries that exceed your tier limits are rejected before running.
Available Datasets
The MCP server provides access to the following curated datasets:Prediction Markets
polymarket — Polymarket markets and tokens
polymarket — Polymarket markets and tokens
Periodic snapshots of Polymarket prediction markets with prices, volume, liquidity, and resolution status. Includes a pre-computed view linking markets to CLOB token IDs for crypto up/down markets.Tables:
polymarket_trades, polymarket_resolutions, polymarket_markets, polymarket_market_tokensBest for: Market analysis, resolution tracking, crypto derivatives researchcrypto_trades — Crypto market trades
crypto_trades — Crypto market trades
Enriched Polymarket crypto 5m/15m market trades with pre-computed price, size, side, and market timing. Filtered to BTC, ETH, SOL, XRP up/down markets only.Tables:
crypto_tradesBest for: Trade flow analysis, price discovery, market microstructurecrypto_market_resolutions — Resolved crypto markets
crypto_market_resolutions — Resolved crypto markets
One row per resolved crypto 5m/15m market with outcome and metadata. Includes volume, liquidity, and resolution timestamps.Tables:
crypto_market_resolutionsBest for: Backtesting strategies, outcome prediction, market efficiency analysismarket_summary — Per-market aggregated stats
market_summary — Per-market aggregated stats
One row per crypto 5m/15m market with aggregated trade stats, price stats, resolution outcome, and orderbook stats. Primary view for strategy backtests.Tables:
market_summaryBest for: Strategy development, market behavior analysis, performance researchorderbook_features — Orderbook time-series
orderbook_features — Orderbook time-series
Enriched orderbook snapshots with time-series features (changes between consecutive snapshots). Built with LAG window functions for detecting liquidity changes.Tables:
orderbook_featuresBest for: Liquidity analysis, market making research, microstructure studiescross_timeframe_signals — 5m→15m predictions
cross_timeframe_signals — 5m→15m predictions
For each resolved 15-minute market, counts how many overlapping 5-minute markets resolved up vs down, and whether this predicted the 15-minute outcome.Tables:
cross_timeframe_signalsBest for: Multi-timeframe analysis, signal generation, predictive modelingstreak_features — Sequential patterns
streak_features — Sequential patterns
Sequential market patterns tracking consecutive same-outcome streaks and whether they break. Useful for mean-reversion studies.Tables:
streak_featuresBest for: Pattern recognition, momentum/reversion analysis, sequence modelingDeFi Yields & Lending
stablecoin_yields — Curated stablecoin yields
stablecoin_yields — Curated stablecoin yields
Hourly snapshots of stablecoin DeFi yields across lending protocols. TIME-SERIES TABLE with multiple snapshot rows per pool — always use deduplication.Tables:
stablecoin_yieldsBest for: Yield farming, protocol comparison, APY optimizationyield_pool_features — Pool yields with rolling stats
yield_pool_features — Pool yields with rolling stats
Daily aggregated pool yields enriched with 7d/30d rolling stats, momentum indicators, spike detection, and rankings. Built from yield_pool_daily.Tables:
yield_pool_featuresBest for: Trend analysis, risk-adjusted returns, yield stability assessmentmorpho_market_features — Morpho market analysis
morpho_market_features — Morpho market analysis
Daily Morpho individual market data enriched with rolling stats, utilization trends, and rankings. Includes supply APY, utilization, and flow metrics.Tables:
morpho_market_featuresBest for: Morpho-specific strategies, capital efficiency research, utilization analysismorpho_vault_features — Morpho vault performance
morpho_vault_features — Morpho vault performance
Daily Morpho vault data enriched with APY features, actual share price returns, and rankings. Tracks net APY after fees and cumulative returns.Tables:
morpho_vault_featuresBest for: Vault comparison, return tracking, fee impact analysisaave_rate_features — Aave cross-chain rates
aave_rate_features — Aave cross-chain rates
Daily Aave rates enriched with rolling stats and cross-chain ranking. Identifies best chains per token and arbitrage opportunities.Tables:
aave_rate_featuresBest for: Cross-chain optimization, rate comparison, chain selectionExample Conversations
Once the MCP server is connected, you can ask your AI agent questions like:Prediction Markets
DeFi Yields
list_datasets and get_schema tools to understand what’s available, then write and execute SQL via the query tool.
Troubleshooting
Connection refused or timeout
Connection refused or timeout
Make sure your API key is valid and correctly set. Check that your client is sending the
Authorization header with every request.Query rejected: use simple table names
Query rejected: use simple table names
The server requires bare table names (e.g.
stablecoin_yields). Do not include project or dataset prefixes in your SQL.Usage limit exceeded
Usage limit exceeded
You’ve hit your daily or monthly spend cap. Wait for the limit to reset or upgrade your plan for higher limits.