Kairos MCP Server

Kairos Signal MCP Server — DePIN and world data

Measured DePIN telemetry, physical-world datasets and descriptive research analytics through REST and MCP. Use source links, observation times and coverage metadata to decide whether a result is suitable for your question. Availability and freshness vary by feed.

Kairos Signal is not a property-owner contact or lead-generation service. The current product is data and research, not a promise of profitable trading signals.

Coverage changes. Use find_networks, get_data_dictionary and the network catalog rather than a copied network count. Catalog entries, distinct networks, Bittensor subnets, rows and metric series are different quantities. get_stats describes dataset row counts, not network coverage.

Connect directly

Full MCP endpoint (Streamable HTTP):

https://kairossignal.com/mcp

Read-only edition, without account creation, purchases or payment tools:

https://kairossignal.com/mcp/public

Read-only does not mean every tool is anonymous or free. In either edition, get_network_signals requires an eligible paid-tier key with the engines capability. Other discovery/data tools have their stated no-key samples and limits. The full edition also exposes account tools and paid analytics.

Claude Code:

claude mcp add --transport http kairos-signal https://kairossignal.com/mcp

Cursor, Windsurf and clients that accept a URL:

{"mcpServers": {"kairos-signal": {"url": "https://kairossignal.com/mcp"}}}

VS Code (.vscode/mcp.json):

{"servers": {"kairos-signal": {"type": "http", "url": "https://kairossignal.com/mcp"}}}

Stdio clients can use this package's bridge:

{"mcpServers": {"kairos-signal": {"command": "npx", "args": ["-y", "kairos-mcp-server"]}}}

Key placement depends on the tool:

• get_network_signals requires an eligible subscription key in the connection's X-API-Key header. Tiered network/history access also uses that header. In the stdio bridge, KAIROS_API_KEY supplies the header.
• Paid analytics accept that header or an api_key tool argument.
• purchase_data, topup_credits and check_balance require api_key inside the tool input, even when the connection or bridge already has a header key. The bridge does not inject it into the arguments.

An API key, a credit balance and a subscription entitlement are not interchangeable.

Official MCP Registry identity: com.kairossignal/kairos-signal. Prefer the vendor endpoint above over a third-party proxy. Smithery's October 31, 2026 service notice says its proxy and connection-management services will close while its directory remains.

Ask a measured question

• GPU capacity: find_networks {"query":"akash"}, then get_network {"symbol":"AKT","metric_filter":"gpu"}.
• Observed history: get_metric_history {"symbol":"FIL","metric":"ACTIVE_MINERS"}. An absent series is not a zero.
• Check a figure: verify_value {"symbol":"FIL","metric":"ACTIVE_MINERS"}. Read the verdict; some upstream values cannot be checked by a GET.

Tools and access

The bridge obtains tools/list from the hosted service rather than maintaining a separate implementation. Consult that live schema for current inputs, prices and limits.

Paid analytics can spend credits. Read the current description before calling; do not repeatedly invoke a paid tool to retry an uncertain result. Their historically named identifiers are retained for compatibility, not as claims of forecasting or causal validation.

Provenance: what the checks establish

Supported network measurements expose provenance and observation-time fields. A source URL is a way to inspect an origin, not a guarantee that the origin is correct. History, derived analytics, raw archives and catalog metadata have different response contracts; do not assume that every output is a fresh first-party measurement.

verify_value compares against a supported upstream GET response that may be cached; inspect upstream.read_at_utc and the verdict rather than assuming a new upstream fetch. verify_footprint checks retained Merkle membership, not upstream truth, independent Bitcoin confirmation or a zero-knowledge proof. The derivation ledger covers the fetches it explicitly lists; a network can have live telemetry without an archived derivation entry. Raw archives can retain rejected or unchecked observations—read their quality fields.

Products, delivery and pricing

Use list_products and the live credit catalog for current prices, eligibility and deliverability; use the pricing page for subscription access. This documentation does not set prices or payment policy.

• Registration creates a key; starter-credit eligibility depends on the current per-IP policy. Read the returned balance instead of assuming a grant. A starter key does not itself grant paid-tier engine access.
• purchase_data requires api_key in its tool input and a currently deliverable product. Small responses can arrive inline; larger deliveries return a receipt and retrieval URL. Use your own stable idempotency_key for each intended purchase and reuse it only for retries of that purchase.
• The current catalog describes dag_manifold_30d as a DAG API access product. Listed legacy/retired products are not automatically purchasable; read deliverability before committing credits.
• topup_credits provides payment instructions for supported card and USDC modes. A quote or checkout link is not payment confirmation. Follow the payment documentation; never send funds without a successful current quote.

Links

• Homepage
• Network pages
• Documentation
• OpenAPI
• Machine-readable introduction
• Evidence-based diligence

Measurements and research only; not investment advice. Terms.

License: MIT