Skip to content

kairos-signal MCP server

io.github.OV3RK177/kairos-signalOV3RK177streamable-httpv3.5.1Scanned

Provenance-first DePIN telemetry: 331 live networks + 129 Bittensor subnets, 10,508 series.

21 tools: 6 can delete or cancel things, 1 do something that can't be undone, 4 change things and 10 only read.

Tools: 6 delete, 1 irreversible, 4 write, 10 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 5 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

11 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the kairos-signal MCP server can do

The kairos-signal MCP server is published by the GitHub account OV3RK177. It has 21 tools. It can delete or cancel things (6 tools: purchase_data, get_hodge_regime_sieve, get_rmt_regime_state, get_depin_slashing_audit and 2 more), do things that cannot be undone, such as sending, paying or publishing (topup_credits) and create or change data (4 tools: verify_value, register_agent, check_balance and verify_footprint). 10 tools only read.

4 tools bring in text other people can write (get_network, verify_value, list_products and 1 more).

The fixed checks matched 5 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 3.5.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Deletes or cancels 6Claude Code: deny
  • get_depin_slashing_auditPaid: 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.1 finding

    Why it is in this group

    • The name "get_depin_slashing_audit" says "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "get_depin_slashing_audit" destructive (destructiveHint: true), and its name says "get", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_depin_slashing_audit" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Enforcement capacity from sourced protocol parameters (paid)
  • get_hodge_regime_sievePaid: 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.1 finding

    Why it is in this group

    • The name "get_hodge_regime_sieve" says "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "get_hodge_regime_sieve" destructive (destructiveHint: true), and its name says "get", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_hodge_regime_sieve" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Hodge lead-lag decomposition of one network's metrics (paid)
  • get_listing_dilution_scorePaid: 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.1 finding

    Why it is in this group

    • The name "get_listing_dilution_score" says "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "get_listing_dilution_score" destructive (destructiveHint: true), and its name says "get", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_listing_dilution_score" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Measured token-supply change for one network (paid)
  • get_rmt_regime_statePaid: 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.1 finding

    Why it is in this group

    • The name "get_rmt_regime_state" says "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "get_rmt_regime_state" destructive (destructiveHint: true), and its name says "get", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_rmt_regime_state" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Correlation spectrum vs Marchenko-Pastur for one network (paid)
  • get_shap_node_attributionPaid: 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.1 finding

    Why it is in this group

    • The name "get_shap_node_attribution" says "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "get_shap_node_attribution" destructive (destructiveHint: true), and its name says "get", a word for reading.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_shap_node_attribution" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Exact day/unit Shapley attribution of a network's daily moves (paid)
  • purchase_dataBuy a product with your credits; most products ship their data inline in the response.No findings

    Why it is in this group

    • The name "purchase_data" says "purchase": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Buy a data product with credits
Can't be undone 1Claude Code: ask
  • topup_creditsAdd credits.Reads text others writeNo findings

    Why it is in this group

    • The name "topup_credits" says "topup": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • title: Add credits (card checkout link or USDC quote)
Changes things 4Claude Code: ask
  • check_balanceCheck your remaining credit balance.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check your remaining credit balance. Use after purchases to see remaining credits.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Check credit balance
  • register_agentCreates 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)).No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Register an agent API key
  • verify_footprintRetained Merkle-membership check for one depin_onchain observation: stamp_day (YYYYMMDD), leaf_index (0-based row in /attestations/batch_<day>.tsv), expected_row_sha256.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Verify a row's Merkle inclusion proof
  • verify_valueRe-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: …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Re-check a value against its upstream source
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 10Show 10 read-only tools
  • fetch_datasetQuery records from a dataset with limit/offset.No findings

    Why it is in this group

    • The name "fetch_dataset" says "fetch": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Fetch raw dataset rows
  • find_networksLooks up DePIN networks (and Bittensor subnets) that have live data, by name or ticker, e.g.No findings

    Why it is in this group

    • The name "find_networks" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find DePIN networks by name or ticker
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_data_dictionaryONBOARDING SPEC: freshness, history depth, coverage and endpoints per feed (depin_onchain, depin_daily, health_profiles, signal_ledger, market_ticks, zk_footprints).No findings

    Why it is in this group

    • The name "get_data_dictionary" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get the data dictionary
  • get_derivation_ledgerReturns the derivation ledger index.No findings

    Why it is in this group

    • The name "get_derivation_ledger" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get the derivation ledger
  • get_metric_historyReturns the daily series for one network metric (one point per UTC day, with how many observations backed it), e.g.No findings

    Why it is in this group

    • The name "get_metric_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get daily history for one network metric
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_networkReturns 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "get_network" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a network's latest measured values
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_network_signalsReturns the current scheduled Hodge and lag-relation snapshots, coverage, observation times, invariants and timestamped history for configured market, DePIN and world cohorts.No findings

    Why it is in this group

    • The name "get_network_signals" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read live network signal decomposition
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_statsReturns 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 findings

    Why it is in this group

    • The name "get_stats" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get coverage statistics
  • list_datasetsList the current dataset catalog with record counts.No findings

    Why it is in this group

    • The name "list_datasets" says "list": a word for reading.
    Description, as the server wrote it
    List the current dataset catalog with record counts. Browsing is free; existing query and daily-call limits apply.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List raw datasets
  • list_productsBrowse purchasable products with prices in credits ($1 = 1 credit).Reads text others writeNo findings

    Why it is in this group

    • The name "list_products" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List data products and prices

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://kairossignal.com/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (6 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://kairossignal.com/mcp/: tools/list returned 21 tools to an anonymous client, including purchase_data (destructive), get_hodge_regime_sieve (destructive), get_rmt_regime_state (destructive), get_depin_slashing_audit (destructive), get_shap_node_attribution (destructive) and 6 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 6 to 11

Findings

Matches of fixed checks, with the text they matched.

5 warn
  • The server marks "get_hodge_regime_sieve" destructive (destructiveHint: true), and its name says "get", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_hodge_regime_sieve" says "get": a word for reading.

    What this check looks for
  • The server marks "get_rmt_regime_state" destructive (destructiveHint: true), and its name says "get", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_rmt_regime_state" says "get": a word for reading.

    What this check looks for
  • The server marks "get_depin_slashing_audit" destructive (destructiveHint: true), and its name says "get", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_depin_slashing_audit" says "get": a word for reading.

    What this check looks for
  • The server marks "get_shap_node_attribution" destructive (destructiveHint: true), and its name says "get", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_shap_node_attribution" says "get": a word for reading.

    What this check looks for
  • The server marks "get_listing_dilution_score" destructive (destructiveHint: true), and its name says "get", a word for reading.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":true,"idempotentHint":false,"openWorldHint":false}; The name "get_listing_dilution_score" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools6 added, 7 changed.+6 added~7 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 11.View diff
    • Tools that change things, listed without credentials: 6 to 11

Install

Pinned to version 3.5.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__kairos-signal__get_network_signals",
      "mcp__kairos-signal__find_networks",
      "mcp__kairos-signal__get_network",
      "mcp__kairos-signal__get_metric_history",
      "mcp__kairos-signal__list_products",
      "mcp__kairos-signal__list_datasets",
      "mcp__kairos-signal__get_stats",
      "mcp__kairos-signal__get_data_dictionary",
      "mcp__kairos-signal__get_derivation_ledger",
      "mcp__kairos-signal__fetch_dataset"
    ],
    "ask": [
      "mcp__kairos-signal__verify_value",
      "mcp__kairos-signal__register_agent",
      "mcp__kairos-signal__topup_credits",
      "mcp__kairos-signal__check_balance",
      "mcp__kairos-signal__verify_footprint"
    ],
    "deny": [
      "mcp__kairos-signal__purchase_data",
      "mcp__kairos-signal__get_hodge_regime_sieve",
      "mcp__kairos-signal__get_rmt_regime_state",
      "mcp__kairos-signal__get_depin_slashing_audit",
      "mcp__kairos-signal__get_shap_node_attribution",
      "mcp__kairos-signal__get_listing_dilution_score"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kairos-signal. Review it before you use it.

Capability tags behind 4 rules
  • mcp__kairos-signal__get_network untrusted-input
  • mcp__kairos-signal__verify_value untrusted-input
  • mcp__kairos-signal__list_products untrusted-input
  • mcp__kairos-signal__topup_credits untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.OV3RK177/kairos-signal/verify?hash=329be1c336f7a2a1e87558852d400dbfb4a57048a61e927ed6cc78c401b9af42" | jq -e '.changed == false'

Pinned hash 329be1c336f7, from Nov 16, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.OV3RK177/kairos-signal/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.OV3RK177/kairos-signal
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.OV3RK177/kairos-signal.svg)](https://radar.anlyon.com/servers/io.github.OV3RK177/kairos-signal)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.

kairos-signal MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the kairos-signal MCP server safe?

No scan can promise that. What its definitions show: 21 tools, 11 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the kairos-signal MCP server delete data?

Yes. 6 tools can delete, cancel or revoke something: purchase_data, get_hodge_regime_sieve, get_rmt_regime_state, get_depin_slashing_audit, get_shap_node_attribution and get_listing_dilution_score.

Can the kairos-signal MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: topup_credits.

What tools does the kairos-signal MCP server have?

21 tools: 6 destructive, 1 irreversible, 4 write, 10 read. purchase_data, get_hodge_regime_sieve, get_rmt_regime_state, get_depin_slashing_audit, get_shap_node_attribution, get_listing_dilution_score, topup_credits, verify_value and 13 more.

Does the kairos-signal MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the kairos-signal MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the kairos-signal MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.