Kristo Intelligence
Pay-per-call DeFi intelligence for AI agents on Base — x402, USDC, no keys.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"kristo-intelligence": {
"url": "https://kristo-intelligence-api.onrender.com/mcp"
}
}
}Remote endpoints
https://kristo-intelligence-api.onrender.com/mcpstreamable-httphttps://kristo-intelligence-api.onrender.com/mcp/ssesseWhat it can do
Tool inventory
Tools (3)
🟢get_market_stats
Read-only operation — no side effects, no parameters. Returns the live Base market snapshot: aggregated activity, daily request/sales counters, the official agent catalog, and real-time market data (CoinGecko, DEXScreener, Fear & Greed). Use it for market context and price/indicator lookups; use get_onchain_sales for paid-call revenue and get_bot_status for integration health. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢get_onchain_sales
Read-only operation — no side effects, no parameters. Returns the real on-chain payment history to this service's fee receiver on Base: total_volume_usd, total_sales, by_token, up to 100 history rows (tx hash, payer, amount, block, timestamp), source="real_blockchain", plus the wallet state and a market snapshot. Use it when you need provable revenue or settlement evidence; use get_market_stats for prices and get_bot_status for integration health. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢get_bot_status
Read-only operation — no side effects, no parameters. Returns the service's Telegram integration status as JSON: telegram_bot_running, telegram_token_configured, last_heartbeat, uptime_started, messages_sent, active_users, commands_processed, vip_invites_sent, plus the wallet state. Use it to confirm this service's own monitoring is alive (and its heartbeat recent) before trusting other outputs; use get_market_stats for market data or get_onchain_sales for provable revenue. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Community
Evidence