Koskamo

Kristo Intelligence MCP

A Model Context Protocol server providing DeFi market intelligence for AI agents on the Base network. It exposes tools for trading signals, whale flow tracking, and arbitrage radar, utilizing x402 micropayments in USDC without requiring API keys or user accounts.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Kristo Intelligence MCP logo, by hristovdimitri2-hubCommunity listingLegacy SSENo sign-inEndpoint checked 2026-11-01Published by hristovdimitri2-hub
MCP endpoint (Legacy SSE)
https://kristo-intelligence-api.onrender.com/mcp/sse
Vendor documentation

What you can do with it

  • Retrieve trading signals for ETH, ONDO, KAITO, and DEGEN with confidence scores
  • Track large USDC whale transfers on the Base network
  • Monitor cross-DEX arbitrage spreads refreshed every 60 seconds

Source and maintenance

Community listingRegistry 6.0.0
Maintenance checked

Protocol and capabilities

Server
kristo-intelligence 1.0.0
MCP protocol
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Kristo Intelligence — paid DeFi signals on Base. Tools advertise their x402 price; pay the exact USDC amount to the listed receiver and retry the target endpoint with the payment header.

Tools

3 advertised

get_market_stats
Advertised by the server during the last successful anonymous check.

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

get_market_stats input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
get_onchain_sales
Advertised by the server during the last successful anonymous check.

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

get_onchain_sales input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
get_bot_status
Advertised by the server during the last successful anonymous check.

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

get_bot_status input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
437 ms
95th percentile latency
437 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 437 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport sse kristo-intelligence-mcp https://kristo-intelligence-api.onrender.com/mcp/sse

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "kristo-intelligence-mcp": {
      "type": "sse",
      "url": "https://kristo-intelligence-api.onrender.com/mcp/sse",
      "disabled": false
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport sse kristo-intelligence-mcp https://kristo-intelligence-api.onrender.com/mcp/sse

Let your agent find its tools

Find servers like Kristo Intelligence MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.