mcpbeat Sign in

Kairos Signal — verifiable DePIN data API MCP Server

by kairossignal Your server? Claim it
answering

Kairos Signal — verifiable DePIN data API is answering right now. Last checked 8 min ago. It exposes 21 tools. Last commit 6 Nov 2026.

DePIN network telemetry with the source, as_of time and an upstream verify URL on every value.

Uptime history 91 days of history · worst day 60%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
21
Tools
read from the server
619 ms
Response time
average over 24h
0
Stars
last commit 6 Nov 2026

What changed 112

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

28 Oct 2 tool descriptions were rewritten get_network, verify_value
24 Oct 9 tool descriptions were rewritten18 times that day find_networks, get_depin_slashing_audit, get_hodge_regime_sieve and 6 more
24 Oct 2 tools changed the parameters they ask for3 times that day purchase_data, topup_credits
23 Oct 5 tools appeared10 times that day get_depin_slashing_audit, get_hodge_regime_sieve, get_listing_dilution_score and 2 more
23 Oct 5 tools disappeared get_depin_slashing_audit, get_hodge_regime_sieve, get_listing_dilution_score and 2 more
23 Oct 3 tool descriptions were rewritten get_listing_dilution_score, get_network_signals, register_agent
22 Oct a tool appeared get_network_signals
21 Oct 5 tools changed the parameters they ask for get_derivation_ledger, get_metric_history, get_network and 2 more
21 Oct 2 tool descriptions were rewritten get_derivation_ledger, verify_footprint
7 Oct 4 tools appeared find_networks, get_metric_history, get_network and 1 more
and 74 more, back to 9 August 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add kairos-signal --transport http https://kairossignal.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://kairossignal.com/mcp
~/.codex/config.toml
[mcp_servers.kairos-signal]
url = "https://kairossignal.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "kairos-signal": {
      "url": "https://kairossignal.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "kairos-signal": {
      "type": "http",
      "url": "https://kairossignal.com/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

network
get_network
Returns the latest first-party measurements for one DePIN network (GPU and CPU capacity, storage, node or hotspot counts, on-chain totals), each with value, unit, as_of, freshness and the verify_url on the network's own API that you can open to check it. Market prices are not included. metric_filter narrows by substring; stale readings are omitted unless include_stale is true. Incident/stale exclusion reasons are returned separately, without values and not counted as metrics. Read-only, no key.
get_network_signals
Returns the current scheduled Hodge and lag-relation snapshots, coverage, observation times, invariants and timestamped history for configured market, DePIN and world cohorts. Requires an API key on a paid tier that includes the engines capability (https://kairossignal.com/pricing), sent in the X-API-Key header of the MCP connection; the free starter key from register_agent does not include it, and a call without a qualifying key is refused with isError. Descriptive relationships only: no fitted memory kernel, causal attribution, calibrated anomaly probability or trading-performance claim. Missing or stale inputs remain explicitly unavailable.
verify
verify_footprint
Retained Merkle-membership check for one depin_onchain observation: stamp_day (YYYYMMDD), leaf_index (0-based row in /attestations/batch_<day>.tsv), expected_row_sha256. verified=true ONLY when the row at that index hashes to expected_row_sha256 AND its inclusion path reaches that day's manifest merkle_root. Says nothing about Bitcoin status or upstream accuracy. Returns JSON: row_sha256, merkle_root, row_hash_matches, inclusion_path_reaches_root, verified, proof_url. Use it when you hold a row from a daily batch and want to show it was committed that day; a call with arguments missing lists the days with a proof ready and a working example. Read-only, no key. Other datasets: unsupported (no retained proof).
verify_value
Re-reads the upstream API behind one of our values right now and reports where the same number appears in the upstream response (JSONPath), the relative difference, and a verdict: exact, within_1pct, within_10pct, no_matching_field, not_checkable_by_get, or withheld_not_live (no upstream fetch; ours is empty). Use it to check a figure before relying on it. Makes one GET to a third-party API; read-only.
balance
check_balance
Check your remaining credit balance. Use after purchases to see remaining credits.
data
get_data_dictionary
ONBOARDING SPEC: freshness, history depth, coverage and endpoints per feed (depin_onchain, depin_daily, health_profiles, signal_ledger, market_ticks, zk_footprints). Machine-legible; answers 'how stale is this and how far back does it go' for every feed. Free, no key.
dataset
fetch_dataset
Query records from a dataset with limit/offset. Free tier: 10 records per query. For depin_onchain, raw archived observations, including rejected rows, are retained. observation_quality reports limited PKT airdrop checks; not_checked means not validated. This read-time annotation is not covered by original proof hashes.
datasets
list_datasets
List the current dataset catalog with record counts. Browsing is free; existing query and daily-call limits apply.
depin
get_depin_slashing_audit
Paid: 2 credits ($2.00) per answered call, charged once and only after a non-empty answer is computed; an unavailable answer, a refusal or an error costs nothing. Send your API key in the X-API-Key header or as api_key. Each call is a new answer and a new charge (no idempotency key). Computes the left-hand side of Theorem 1 in Qazi (2026, arXiv:2608.12576), the enforcement capacity p * (lambda*S + delta*min Phi): the largest per-audit deterrence ratio a network's slashing and probation can support, in the network's stake unit. Inputs are the network's published protocol parameters (stake per provider, slash fraction, audit probability, probation ladder, hardware-identity binding), each returned with the URL it was read from and the date it was last confirmed there; unsourced stake or slash parameters are refused, never defaulted, and so is one not re-confirmed within 60 days. Where a network publishes no audit probability, p = 1 is used and the figure is labelled an upper bound (capacity_upper_bound_p1); a slash fraction published only as a recommended default is labelled so and its range is reported. Structural screens (deviations that cannot be detected, missing identity binding) are reported. A ceiling, not a verdict: the cheating gain it would have to exceed is private, so no incentive-compatibility answer is given. Networks without sourced parameters are answered unavailable and not charged.
derivation
get_derivation_ledger
Returns the derivation ledger index. With a symbol: up to 20 recent archived upstream fetches behind that network, each with time, verify_url, the SHA-256 and size of the raw payload, the collector code hash and the fetch status, so a published value can be traced to the exact bytes and build that produced it (the payload bytes themselves are the paid derivation_replay product). A network with live data that the ledger does not cover yet returns entries: [] with ledger_status not_yet_covered and the covered symbols. Without a symbol: every covered symbol with its latest fetch time and entry count. Read-only, no key. To compare a live value with its upstream right now, use verify_value.
hodge
get_hodge_regime_sieve
Paid: 1 credit ($1.00) per answered call, charged once and only after a non-empty answer is computed; an unavailable answer, a refusal or an error costs nothing. Send your API key in the X-API-Key header or as api_key. Each call is a new answer and a new charge (no idempotency key). For one DePIN network: daily closes of its stored first-party metrics over the last `days` complete UTC days (one publisher per metric; a metric that is an exact combination of others, e.g. a writer-derived ratio, is excluded and named; the panel's effective rank and near-identical pairs are reported), each metric's daily log change, and the lag-1 lead-lag flow between every pair (correlation of one metric today with the other yesterday, minus the reverse). A Helmholtz-Hodge decomposition on the complete graph splits the flow into a gradient part (one consistent ordering, reported as a lead score per metric) and a curl part (cyclic lead-lag); the harmonic part is zero on a complete graph and is shown as a check. Descriptive, no significance test; the flow size expected under independence is given for scale. Uses up to `max_metrics` (3-16, default 10) metrics, by name order. Every input daily close is returned with its as_of and verify_url. The tool name is historical: no regime classification or trading signal is produced.
listing
get_listing_dilution_score
Paid: 1 credit ($1.00) per answered call, charged once and only after a non-empty answer is computed; an unavailable answer, a refusal or an error costs nothing. Send your API key in the X-API-Key header or as api_key. Each call is a new answer and a new charge (no idempotency key). For one DePIN network: each first-party on-chain supply series it has (eligible metrics whose name contains 'supply', e.g. onchain_total_supply), its daily close at the latest complete UTC day and 7 and 30 days earlier, the percentage changes, and each change annualised by compounding ((end/start)^(365/days) - 1, so a 7-day move is heavily amplified). Each series is the supply of the contract or chain at its verify_url; one below half of the network's reference supply (a bridged or partial representation, e.g. a BEP-20 wrapper) is not used, and one with no reference held, or counted in another unit than whole tokens of the network's ticker (base units, a second token), is labelled unchecked. A series with 2 or fewer distinct daily closes in 30 days is not used (a stuck feed cannot be told from a fixed supply). Every endpoint carries its as_of and verify_url; nothing is interpolated. No exchange-listing, price, funding, market-cap or aggregator data is used; the tool name is historical. Networks without an eligible supply series are answered unavailable and not charged.
metric
get_metric_history
Returns the daily series for one network metric (one point per UTC day, with how many observations backed it), e.g. symbol=AKT metric=GPU_ACTIVE. Days with no observation are absent, never zero. The free tier serves the last 7 days and says so in window_notice; an X-API-Key header on the connection serves your tier's window. Read-only.
networks
find_networks
Looks up DePIN networks (and Bittensor subnets) that have live data, by name or ticker, e.g. 'akash', 'helium', 'FIL'. Returns symbol, name, category and the network's public page. Use it to get the symbol that get_network, get_metric_history and verify_value take; a network with no public ticker is listed under its internal reference (symbol_kind 'internal_ref'). Read-only, no key.
products
list_products
Browse purchasable products with prices in credits ($1 = 1 credit). DePIN supply-telemetry, provenance, derivation-replay, history and the intel bundle start at $0.49. Grade purchases are conditional on measured-grade availability; check /v1/credits/pricing before buying. 30-day Pro access to the DAG manifold API is sold as dag_manifold_30d and delivers its API key inline. Not purchasable, refused by purchase_data with 503 not_yet_deliverable and nothing charged: the signal-feed tiers (retired, not sold), dag_pro (buy dag_manifold_30d instead), and dag_quant, dag_enterprise and mcp_unlimited (listed, not on sale yet). The five paid analytics tools are not products here: each charges credits per answered call, stated in its own description. Call after register_agent.
purchase
purchase_data
Buy a product with your credits; most products ship their data inline in the response. Deliverability is product-specific, including grade availability; check /v1/credits/pricing before buying — call list_products for the live prices rather than trusting a figure restated here, which is how a price in a second place drifts from the first. The signal_* keys (retired, not sold), dag_pro (sold as dag_manifold_30d), dag_quant, dag_enterprise and mcp_unlimited (not on sale yet) return 503 not_yet_deliverable and charge nothing; they are deliberately blocked, not broken. Most products deliver data inline; dag_manifold_30d delivers a 30-day DAG manifold API key inline; a delivery larger than 4 MB (today depin_history and lead_lag_correlations, each tens of MB, and derivation_replay whenever its 100 raw upstream bodies pass 4 MB, as an unfiltered pull does today) returns the receipt and a no-charge URL that serves the stored payload. Every purchase carries an idempotency_key (yours, or one generated and returned to you): if a call errors, the answer says whether you may have been charged, and repeating it with the same idempotency_key returns the receipt and data without a second charge. Use api_key from register_agent.
register
register_agent
Creates an API key for this agent and grants the free starter credits ($5 free credits, no card (first 3 keys per IP per 30 days)). Past the per-IP limit a key is still created, with $0, and the response says so. A key is needed for purchase_data, check_balance, topup_credits and every tool that charges credits; get_network_signals needs one on a paid tier with the engines capability, which the free starter key does not have. Every other read-only tool works without one. email is optional and used for delivery and top-up notices.
rmt
get_rmt_regime_state
Paid: 1 credit ($1.00) per answered call, charged once and only after a non-empty answer is computed; an unavailable answer, a refusal or an error costs nothing. Send your API key in the X-API-Key header or as api_key. Each call is a new answer and a new charge (no idempotency key). For one DePIN network: the correlation matrix of the daily log changes of its stored first-party metrics over the last `days` complete UTC days (one publisher per metric; exact combinations of other metrics, e.g. writer-derived ratios, excluded and named; effective rank and near-identical pairs reported), its eigenvalues, and the Marchenko-Pastur edges for the same number of independent series (q = N / (T-1)). Reports the largest eigenvalue over the upper edge, how many eigenvalues exceed it, the absorption ratio (variance share of the top ceil(N/5) eigenvalues) and each metric's loading on the top eigenvector. The edge is a reference for independent light-tailed series; telemetry changes are neither, so exceeding it describes co-movement and is not a test. Uses up to `max_metrics` (3-60, default 30) metrics, by name order. Every input daily close is returned with its as_of and verify_url. No regime label, position size or trading mode is produced.
shap
get_shap_node_attribution
Paid: 1.5 credits ($1.50) per answered call, charged once and only after a non-empty answer is computed; an unavailable answer, a refusal or an error costs nothing. Send your API key in the X-API-Key header or as api_key. Each call is a new answer and a new charge (no idempotency key). For one DePIN network: an exact two-factor functional ANOVA of the daily log changes of its stored first-party metrics over the last `days` complete UTC days (same input rules as get_rmt_regime_state), with factors day (moves shared by the network's metrics that day) and unit (metrics measured in the same unit; units held by one metric are pooled into one named group; a panel where a group would hold one metric, or that has only one unit group, is answered unavailable, uncharged). Returns each factor's variance share, their interaction and the metric-specific remainder, the mean absolute Shapley value per factor, and for the latest day each metric's change split exactly into its day and unit Shapley values plus remainder (additivity error reported). Descriptive: not causal, not a forecast. Uses up to `max_metrics` (3-60, default 30) metrics, by name order. Every input daily close is returned with its as_of and verify_url.
stats
get_stats
Returns the row count of every dataset served here (depin_onchain, market_ticks and the rest), their total, the scope statement and the free-tier limits. No arguments, no key, read-only. For one network's live values use get_network; for freshness and history depth per feed use get_data_dictionary.
topup
topup_credits
Add credits. Card (one call): {"method": "stripe", "amount": N} where N is $20 or $99 — returns a Stripe checkout_url already bound to your api_key, and credits post automatically once Stripe confirms payment at $1 = 1 credit. No human step and no wallet needed. USDC on Base, two modes. micro_decimal, no wallet signature: {"method": "usdc", "mode": "micro_decimal", "amount": N} with N whole USDC from 1 to 999,999 returns a unique amount with a 6-decimal suffix and an expires_at; a finalized Base transfer of EXACTLY that amount, from any sender including an exchange, before expires_at credits your account (1 USDC = 1 credit); a different amount does not credit your account. verified_wallet (the default when mode is omitted): verify your sender first via POST /v1/credits/crypto/challenge and /verify with X-API-Key, sign the returned challenge with your own EOA, then pass the verified from_address; only a transfer FROM that wallet is credited. In every USDC mode send only after a successful quote; credit requires finalized Base evidence. Instructions: https://kairossignal.com/docs/crypto.html

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_zk_provenance
removed 11 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://kairossignal.com/mcp streamable-http answering 611 ms 8 min ago

Alternatives to Kairos Signal — verifiable DePIN data API

same job, measured the same way
Intel
by chainhelix

Nine chain onchain intelligence with a verifiable onchain signal attestation stream

82 tools answering
Materials
by spacemushroom

Read-only sourced engineering materials data: every value with unit, conditions and source.

24 tools answering
Databutler Facts
by physics-star-cat

Official thresholds, rates and fees by key, with source, verified date and signature.

3 tools answering
open-signals
by civops-platform

Public hazard, water, weather and EPA data with source, age and licence on every reading.

9 tools answering
FLOPS Index
by zeroatflops

GPU rental reference prices (spot, on-demand, DePIN), key-free; every value carries a verify URL.

196 installs/wk 6 tools answering
Social Signal
by pipeworx-io

Social Signal — post-VOLUME TIME SERIES across the open social networks that can be read without…

285 installs/wk 46 tools answering
Lumin guru
by lumin

The calculation and trust layer for astrology agents. Every value returns with its rule and source.

answering
Recipe360
by pulso360

Your AI runs your data workflows the same way every time, with a record of every run.

local only

Kairos Signal — verifiable DePIN data API — questions

Answers built from our own checks of this server.

What can Kairos Signal — verifiable DePIN data API do?
It exposes 21 tools, read directly from the server on our last check. Among them: check_balance, fetch_dataset, find_networks, get_data_dictionary, get_depin_slashing_audit, get_derivation_ledger and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Kairos Signal — verifiable DePIN data API mostly used for?
Its tools cluster around verify and network. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Kairos Signal — verifiable DePIN data API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 619 ms. The bar chart above shows every period we have measured.
Did Kairos Signal — verifiable DePIN data API ever remove tools?
Yes. get_zk_provenance is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Kairos Signal — verifiable DePIN data API?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Kairos Signal — verifiable DePIN data API need an API key?
No. Kairos Signal — verifiable DePIN data API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Kairos Signal — verifiable DePIN data API?
It answers our handshake in 619 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Kairos Signal — verifiable DePIN data API open source?
We cannot say either way: written in JavaScript, 0 stars on GitHub and 1 open issue, but we could not determine the licence, and without one the code is not open source by default.