Kristo Intelligence
REMOTE · KRISTO-INTELLIGENCE-API.ONRENDER.COM · 2 COMPONENTS
Pay-per-call DeFi intelligence for AI agents on Base — x402, USDC, no keys.
Last scanned (6 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 692 tokens (~115/item across 6 items; 6 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 4 Nov 26 0
- Schema quality: fail → pass ▲ functional
- Server version: 1.0.0 → 6.2.0 functional
- New tool “get_whale_flow” functional
- New tool “get_trading_signal” functional
- New tool “get_arbitrage_opportunities” functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 63. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://kristo-intelligence-api.onrender.com/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.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 kristo-intelligence-api.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.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 |
|---|---|---|---|---|
| sse | https://kristo-intelligence-api.onrender.com/mcp/sse | Verified | 200 | |
| http (plaintext) | http://kristo-intelligence-api.onrender.com/mcp/sse | HTTPS enforced | 301 | https://kristo-intelligence-api.onrender.com/mcp/sse |
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 →
get_arbitrage_opportunities ~85
Read-only operation — no side effects, no parameters. Returns live cross-DEX arbitrage spreads on Base, refreshed every 60 seconds. Use it for executable price gaps between venues; use get_market_stats for aggregate prices or get_trading_signal for directional calls. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_bot_status ~124
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_stats ~111
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
get_onchain_sales ~127
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trading_signal ~110
Read-only operation — no side effects, no parameters. Returns this service's flagship trading-agent signals for ETH, ONDO, KAITO and DEGEN: action, confidence, price_usd and the model's reasoning. Use it when you need a directional call rather than raw market data; use get_whale_flow for large-transfer flow and get_arbitrage_opportunities for cross-DEX spreads. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_whale_flow ~95
Read-only operation — no side effects, no parameters. Returns network-wide USDC whale flow on Base: transfers of $5M or more, refreshed every 60 seconds, with labelled counterparties. Use it to see where size is moving; use get_trading_signal for directional calls or get_market_stats for broad context. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Kristo Intelligence MCP server?
Kristo Intelligence is a hosted endpoint at https://kristo-intelligence-api.onrender.com/mcp/sse, 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 · kristo-intelligence-api.onrender.com
claude mcp add --transport http hristovdimitri2-hub-kristo-intelligence 'https://kristo-intelligence-api.onrender.com/mcp/sse'
What is the Kristo Intelligence MCP server?
Kristo Intelligence is an MCP server listed in the public MCP registry as io.github.hristovdimitri2-hub/kristo-intelligence. Pay-per-call DeFi intelligence for AI agents on Base, x402, USDC, no keys. This page covers its hosted endpoint (https://kristo-intelligence-api.onrender.com/mcp/sse).
Is the Kristo Intelligence MCP server safe to use?
Kristo Intelligence scores 73 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 Kristo Intelligence MCP server expose?
Kristo Intelligence exposes 6 tools: get_market_stats, get_onchain_sales, get_bot_status, get_trading_signal, get_whale_flow, get_arbitrage_opportunities. Their descriptions and schemas cost roughly 652 tokens of context every time the server is loaded.
Does the Kristo Intelligence MCP server require authentication?
No. We connected to Kristo Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kristo Intelligence MCP server still maintained?
Kristo Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.