accueil / serveurs / Recherche & Web / com.kairossignal/kairos-signal
com.kairossignal/kairos-signal
serveur MCP (Model Context Protocol) · kairos-signal-mcp 3.7.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.kairossignal/kairos-signal est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.kairossignal/kairos-signal » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 15 outils
- check_balance≈ 111 tokens
Check your remaining credit balance. Use after purchases to see remaining credits.
Paramètres, retour & exemple (1)
Paramètresapi_key· string · requis
Your API key
Exemple d'appel{"name": "check_balance", "arguments": {"api_key": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - fetch_dataset≈ 214 tokens
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.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Max records (max 10 for free tier)offset· integer · optionnel
Record offsetdataset· string · requis
Dataset name (e.g., depin_onchain)
Exemple d'appel{"name": "fetch_dataset", "arguments": {"dataset": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - find_networks≈ 327 tokens
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. Read-only, no key.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Max results (default 20).query· string · optionnel
Name or ticker fragment, case-insensitive. Omit to list.category· string · optionnel
Optional category filter, e.g. compute, storage, wireless, AI.
Exemple d'appel{"name": "find_networks", "arguments": {"limit": 1, "query": "texte", "category": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"matches": 1, "networks": [], "returned": 1}} - get_data_dictionary≈ 139 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_data_dictionary", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_derivation_ledger≈ 192 tokens
Returns the derivation ledger. With a symbol: the archived raw upstream payloads (SHA-256 pinned) and the collector code hash behind that network's recent fetches, so a published value can be re-derived independently. Without one: the symbols that have ledger entries. Read-only, no key. To compare a live value with its upstream right now, use verify_value.
Paramètres, retour & exemple (1)
Paramètressymbol· string · optionnel
Optional: filter to one symbol (e.g. AKT). Omit for the coverage list.
Exemple d'appel{"name": "get_derivation_ledger", "arguments": {"symbol": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_metric_history≈ 355 tokens
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.
Paramètres, retour & exemple (3)
Paramètresdays· integer · optionnel
Days of history requested (default 7).metric· string · requis
Metric name exactly as get_network lists it, e.g. GPU_ACTIVE.symbol· string · requis
Network ticker, e.g. AKT.
Exemple d'appel{"name": "get_metric_history", "arguments": {"metric": "texte", "symbol": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"metric": "texte", "points": [], "symbol": "texte", "window_days": 1, "window_notice": "texte"}} - get_network≈ 574 tokens
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. Read-only, no key.
Paramètres, retour & exemple (4)
Paramètressymbol· string · requis
Network ticker, e.g. AKT, FIL, HNT (find_networks resolves names).max_metrics· integer · optionnel
Max metrics returned (default 40).include_stale· boolean · optionnel
Include readings past their freshness window (default false).metric_filter· string · optionnel
Optional case-insensitive substring, e.g. 'gpu' or 'storage'.
Exemple d'appel{"name": "get_network", "arguments": {"symbol": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "symbol": "texte", "category": "texte", "page_url": "texte", "telemetry": [], "stale_omitted": 1, "metrics_matched": 1, "metrics_returned": 1, "onchain_first_party": []}} - get_stats≈ 144 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_stats", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_datasets≈ 96 tokens
List the current dataset catalog with record counts. Browsing is free; existing query and daily-call limits apply.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_datasets", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_products≈ 209 tokens
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. Signal-feed tiers, DAG-manifold tiers and mcp_unlimited are priced but NOT yet purchasable: their entitlement is not wired into the serving API, so purchase_data refuses them with 503 not_yet_deliverable rather than charging you for nothing. Call after register_agent.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_products", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - purchase_data≈ 368 tokens
Buy a product with your credits; the data ships 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_*, dag_* and mcp_unlimited keys are priced but return 503 not_yet_deliverable — they are deliberately blocked, not broken, because nothing grants their entitlement yet. Credits buy DATA; they do not change your access tier. Use api_key from register_agent.
Paramètres, retour & exemple (3)
Paramètresapi_key· string · requis
Your API key from register_agentproduct_key· string · requis
Product key to purchase (e.g. depin_provenance, depin_networks; list_products has every key and price)idempotency_key· string · optionnel
Optional. Any stable string unique to THIS intended purchase (e.g. a uuid). If a network error makes you retry the same call, re-send the SAME idempotency_key: the retry returns the same receipt and re-delivers the data without a second charge.
Exemple d'appel{"name": "purchase_data", "arguments": {"api_key": "texte", "product_key": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - register_agent≈ 227 tokens
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 only needed for purchase_data, check_balance and topup_credits; every read-only tool works without one. email is optional and used for delivery and top-up notices.
Paramètres, retour & exemple (2)
Paramètresemail· string · optionnel
OPTIONAL contact email (for delivery and topup notifications). Omit to register anonymously.agent_name· string · requis
Your agent name
Exemple d'appel{"name": "register_agent", "arguments": {"agent_name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - topup_credits≈ 457 tokens
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 ({"method": "usdc"}) is also accepted but requires more work: 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 and send only after a successful quote — credit requires finalized Base evidence. Instructions: https://kairossignal.com/docs/crypto.html
Paramètres, retour & exemple (5)
Paramètresamount· number · requis · 20 | 99
Amount in USD to add. Fixed packs only: 20 or 99. Any other value returns the available packs instead of a link.method· string · requis · usdc | stripe
Payment methodapi_key· string · requis
Your API keytx_hash· string · optionnel
Legacy optional field; a transaction hash does not replace from_address or verify payment.from_address· string · optionnel
Required for USDC: your EOA address already verified to this API account through the wallet challenge flow.
Exemple d'appel{"name": "topup_credits", "arguments": {"amount": 20, "method": "usdc", "api_key": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify_footprint≈ 253 tokens
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. Other datasets: unsupported (no retained proof).
Paramètres, retour & exemple (4)
Paramètresdataset· string · requis · depin_onchainstamp_day· string · requisleaf_index· integer · requisexpected_row_sha256· string · requis
Exemple d'appel{"name": "verify_footprint", "arguments": {"dataset": "depin_onchain", "stamp_day": "texte", "leaf_index": 1, "expected_row_sha256": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify_value≈ 299 tokens
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 or not_checkable_by_get. Use it to check a figure before relying on it. Makes one GET to a third-party API; read-only.
Paramètres, retour & exemple (2)
Paramètresmetric· string · requis
Metric name from get_network, e.g. ACTIVE_MINERS.symbol· string · requis
Network ticker, e.g. FIL.
Exemple d'appel{"name": "verify_value", "arguments": {"metric": "texte", "symbol": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ours": {}, "match": {}, "metric": "texte", "symbol": "texte", "verdict": "texte", "upstream": {}, "explanation": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».