Solana Token Intelligence
RemoteAbout Solana Token Intelligence
Solana Token Intelligence provides agents with a fused safety and market assessment for a Solana token, including a plain-language risk verdict. Calls require no API key or account and cost $0.01 USDC through x402.
Key features
- 01Combine token safety and market data
- 02Assess authorities and holder distribution
- 03Include liquidity and wash-trade score
- 04Return a plain-language risk verdict
- 05Offer paid and demo endpoints
Use cases
- 01Screen a Solana token before further analysis
- 02Review liquidity, holders, and token authorities
- 03Request a sample assessment using the free demo
MCP support
The MCP endpoint exposes a paid token_intel tool and a free token_intel_demo tool. The paid call uses x402 payment.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://token-intel.xrpbreadcrumbs.workers.dev/mcpclaude mcp add --transport http k0diak-token-intel https://token-intel.xrpbreadcrumbs.workers.dev/mcp{"mcpServers":{"k0diak-token-intel":{"type":"http","url":"https://token-intel.xrpbreadcrumbs.workers.dev/mcp"}}}Open in Cursor{"servers":{"k0diak-token-intel":{"type":"http","url":"https://token-intel.xrpbreadcrumbs.workers.dev/mcp"}}}Open in VS Code{"mcpServers":{"k0diak-token-intel":{"type":"http","url":"https://token-intel.xrpbreadcrumbs.workers.dev/mcp"}}}{"mcpServers":{"k0diak-token-intel":{"serverUrl":"https://token-intel.xrpbreadcrumbs.workers.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
2| Parameter | Type | Required | Description |
|---|---|---|---|
| mint | string | Yes | SPL mint address (base58) |
| _payment | string | No | base64 x402 payment payload (alternative to the X-PAYMENT header) |
Details
From the project READMEtoken-intel-x402 — agent-native Solana token intelligence
One keyless call returns a fused safety + market read on any Solana token — mint/freeze
authority, top-holder %, dev holdings, wash-trade (organic) score, liquidity, verification — plus
a synthesized risk verdict (low-risk / caution / high-risk) with plain-language flags.
Gated by x402: an autonomous agent pays a $0.01 USDC micro-fee per call (Base or Solana) — no API key, no account, no signup. That is the differentiator: every rival (RugCheck, Birdeye, SolSniffer, GoPlus) needs a key and a signup; this is built for machine-to-machine payment.
Live: https://token-intel.xrpbreadcrumbs.workers.dev
GET /api/token-intel?mint=<SPL_MINT> # PAID (x402) → JSON intelligence
GET /api/token-intel/demo # free BONK sample (rate-limited, cached)
POST /mcp # MCP server: token_intel (paid) + token_intel_demo (free)
GET /stats # public funnel: challenges, demos, paid calls, revenue
GET / # free: what it is + how to pay
GET /healthz # free
Deploy (Cloudflare Workers)
Runs on the Workers free plan. v1 lived on Deno Deploy and was suspended when free traffic exceeded the free tier while paid calls stayed at zero; v2 rate-limits and caches the free demo so that can't recur, and records every step of the payment funnel in a D1 ledger.
npm install
npx wrangler d1 execute token-intel-ledger --remote --file schema.sql # once
npx wrangler deploy
Wallets, price, and facilitator are [vars] in wrangler.toml (public addresses — no secrets).
Security by design
- No private keys, no API keys on the server — data (Jupiter) and payments (PayAI facilitator) are both keyless, so there is nothing here to steal.
- Read-only toward the outside world; its only writes are an anonymous event ledger (no IPs, no PII) — near-zero attack surface.
- Pay-to wallet is receive-only; its key never touches this host.
- Every paid call requires payment first, so abuse costs the attacker money.
- Input strictly validated (base58 mint) — no SSRF/injection.
Informational only, not financial advice, no warranty.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.