io.github.collapseindex/ci1t-mcp
NPM · @COLLAPSEINDEX/CI1T-MCP · SCANNED SEP 20
CI-1T prediction stability engine. Detect ghosts, evaluate drift, monitor fleets. 20 tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 203 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2424 tokens (~115/item across 21 items; 20 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "fleet_session_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.collapseindex/ci1t-mcp server?
io.github.collapseindex/ci1t-mcp runs locally as an npm package, launched with npx -y @collapseindex/ci1t-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @collapseindex/ci1t-mcp
claude mcp add collapseindex-ci1t-mcp -- npx -y @collapseindex/ci1t-mcp
{
"mcpServers": {
"collapseindex-ci1t-mcp": {
"command": "npx",
"args": [
"-y",
"@collapseindex/ci1t-mcp"
]
}
}
} {
"servers": {
"collapseindex-ci1t-mcp": {
"command": "npx",
"args": [
"-y",
"@collapseindex/ci1t-mcp"
]
}
}
} codex mcp add collapseindex-ci1t-mcp -- npx -y @collapseindex/ci1t-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"collapseindex-ci1t-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@collapseindex/ci1t-mcp"
],
"enabled": true
}
}
} openclaw mcp add collapseindex-ci1t-mcp --command npx --arg -y --arg @collapseindex/ci1t-mcp
mcp_servers:
collapseindex-ci1t-mcp:
command: "npx"
args: ["-y", "@collapseindex/ci1t-mcp"] {
"McpServers": {
"collapseindex-ci1t-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@collapseindex/ci1t-mcp"
]
}
}
} assistant mcp add collapseindex-ci1t-mcp -t stdio -c npx -a -y @collapseindex/ci1t-mcp
{
"mcpServers": {
"collapseindex-ci1t-mcp": {
"command": "npx",
"args": [
"-y",
"@collapseindex/ci1t-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@collapseindex/ci1t-mcp@1.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
alert_check ~218
Check episodes against configurable thresholds and return triggered alerts — no API call, no auth, no credits. Takes an episode array from evaluate or fleet responses. Response: { status: 'ok'|'warn'|'critical', total_alerts, critical, warnings, episodes_checked, thresholds, alerts: [{ episode, type, value, threshold, severity }] }. Alert types: ci_exceeded, ema_exceeded, authority_elevated, ghost_detected, fault.
| Name | Type | Req | Description |
|---|---|---|---|
| al_threshold | integer | – | Alert if any episode authority level >= this (default: 3 = Minimal) |
| ci_threshold | number | – | Alert if any episode CI exceeds this (default: 0.45 = Drift boundary) |
| ema_threshold | number | – | Alert if any episode EMA exceeds this (default: 0.45) |
| episodes | array | yes | Episode array from an evaluate or fleet response |
| fault_alert | boolean | – | Alert on faults (default: true) |
| ghost_alert | boolean | – | Alert on ghost detections (default: true) |
No output schema declared.
No examples provided.
compare_windows ~149
Compare two windows of episodes to detect drift or degradation — no API call, no auth, no credits. Takes baseline and recent episode arrays from evaluate or fleet_session_round responses. Response: { comparison: { baseline: stats, recent: stats }, delta: { ci_mean, ema_mean, al_mean, ghost_delta, warn_delta, fault_delta }, trend: 'improving'|'stable'|'degrading', degraded: bool, severity_factors: [...] }. Use after multiple evaluate calls to track model health over time.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | array | yes | Baseline episode array (e.g. last hour, known-good run) |
| recent | array | yes | Recent episode array to compare against baseline |
No output schema declared.
No examples provided.
convert_scores ~135
Convert between probability floats (0.0–1.0) and Q0.16 fixed-point integers (0–65535) — no API call, no auth, no credits. Response: { direction, count, converted: [{ input, q16|float }] }. Use to_q16 before evaluate, from_q16 to make CI outputs human-readable.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | "to_q16" converts 0.0–1.0 floats to Q0.16 integers. "from_q16" converts Q0.16 integers to floats. |
| scores | array | yes | Array of scores to convert |
No output schema declared.
No examples provided.
create_api_key ~90
Create a new CI-1T API key. Response: { api_key, masked_key, scope, record }. IMPORTANT: Save the returned api_key — it cannot be retrieved again after creation.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Human-readable name for the key |
| scope | string | – | Endpoint scope (default: all) |
| user_id | string | yes | Your user ID (shown on your dashboard) |
No output schema declared.
No examples provided.
delete_api_key ~50
Delete an API key by its PocketBase record ID (from list_api_keys). Response: { deleted: true }.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | PocketBase record ID of the API key to delete |
No output schema declared.
No examples provided.
evaluate ~233
Evaluate prediction stability. Sends scores to the CI-1T engine and returns per-episode stability metrics. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535) — auto-converts. Response: { episodes: [{ ci_out, ci_ema_out, al_out, warn, fault, ghost_confirmed, ghost_suspect_streak, ... }], credits_used, credits_remaining }. CI values are Q0.16 (0–65535; divide by 65535 for %). Classification: ≤0.15=Stable, ≤0.45=Drift, ≤0.70=Flip, >0.70=Collapse. Chain results → visualize (chart), alert_check (threshold alerts), compare_windows (drift detection), or interpret_scores (stats).
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | Episode length (default: 3) |
| scores | array | yes | Array of prediction scores — floats (0.0–1.0) or Q0.16 integers (0–65535), auto-detected. Max 10,000. |
No output schema declared.
No examples provided.
fleet_evaluate ~193
Evaluate a fleet of model nodes for prediction stability. Each node provides a score stream. Returns per-node episodes and aggregate fleet stats. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535) — auto-converts per node. Response: { nodes: [{ node_id, episodes: [{ ci_out, ci_ema_out, al_out, warn, fault, ghost_confirmed, ... }] }], fleet_summary, credits_used, credits_remaining }. Chain per-node episodes → visualize, alert_check, or compare_windows. For persistent multi-round fleet monitoring, use fleet_session_create instead.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | Episode length (default: 3) |
| nodes | array | yes | Array of node score arrays — each inner array is one node's scores (floats or Q0.16). Max 16 nodes, 10,000 scores per node. |
No output schema declared.
No examples provided.
fleet_session_create ~103
Create a new persistent fleet monitoring session. Returns a session ID for subsequent rounds. Max 16 nodes. Response: { session_id, node_count, node_names, created_at }. Workflow: fleet_session_create → fleet_session_round (repeat) → fleet_session_state (check) → fleet_session_delete (cleanup).
| Name | Type | Req | Description |
|---|---|---|---|
| node_count | integer | yes | Number of nodes in the fleet |
| node_names | array | – | Optional names for each node (must match node_count) |
No output schema declared.
No examples provided.
fleet_session_delete ~49
Delete a fleet session by ID. Response: { deleted: true, session_id }. Call when monitoring is complete to free server resources.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Fleet session ID to delete |
No output schema declared.
No examples provided.
fleet_session_list ~35
List all active fleet sessions. Response: { sessions: [{ session_id, node_count, round_count, created_at }] }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fleet_session_round ~105
Submit a scoring round to an existing fleet session. Each node's scores array is evaluated and the cumulative fleet snapshot is returned. Response: { round, nodes: [{ episodes: [...] }], fleet_summary }. Episodes in the response can be passed to visualize, alert_check, or compare_windows.
| Name | Type | Req | Description |
|---|---|---|---|
| scores | array | yes | Per-node score arrays for this round. Max 16 nodes, 10,000 scores per node. |
| session_id | string | yes | Fleet session ID |
No output schema declared.
No examples provided.
fleet_session_state ~67
Get the current state of a fleet session without submitting new scores. Response: { session_id, round_count, nodes: [{ node_id, node_name, episodes: [...] }], fleet_summary }. Use to inspect accumulated results between rounds.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Fleet session ID |
No output schema declared.
No examples provided.
generate_config ~162
Generate CI-1T integration boilerplate for a specific framework or language — no API call, no auth, no credits. Response: { framework, use_case, api_base, endpoints, score_format, auth, cost, instruction }. The instruction field tells you how to produce complete, production-ready integration code for the user's stack.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework or language (e.g. "fastapi", "express", "django", "flask", "nextjs", "python", "typescript", "go", "rust") |
| use_case | string | – | Integration pattern: "single" for single-model monitoring, "fleet" for multi-model fleet evaluation, "guardrail" for CI-as-guardrail (reject/fallback when unstable) |
No output schema declared.
No examples provided.
get_invoices ~58
Get billing history (Stripe invoices). Response: { invoices: [{ amount, credits, date, status }], has_more, cursor }. Pass cursor to paginate.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor (payment intent ID) for next page |
No output schema declared.
No examples provided.
health ~38
Check CI-1T engine health. Response: { status, version, latency_ms }. Call before evaluate/fleet operations to verify the engine is reachable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
interpret_scores ~133
Analyze raw prediction scores with statistical breakdown — no API call, no auth, no credits. Response: { count, mean, std, min, max, breakdown: [{ index, raw, normalized }] }. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535) — auto-detects. For full stability classification (Stable/Drift/Flip/Collapse), pass scores to the evaluate tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| scores | array | yes | Array of scores — floats (0.0–1.0) or Q0.16 integers (0–65535) |
No output schema declared.
No examples provided.
list_api_keys ~65
List all API keys for the authenticated user. Response: { keys: [{ id, name, masked_key, scope, enabled, created }] }. Use the record id with delete_api_key to revoke.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | Your user ID (shown on your dashboard) |
No output schema declared.
No examples provided.
onboarding ~47
Welcome guide for new users. Returns setup instructions, available tools, pricing, and links. No auth required. Call this when someone is new to CI-1T or asks how to get started.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
probe ~317
Probe an LLM for prediction instability. Sends the same prompt 3 times and compares responses using the specified similarity method. Two modes: (1) Default — routes through CI-1T backend (costs 1 credit, uses Grok). (2) BYOM (Bring Your Own Model) — provide base_url + model_api_key + model to probe any OpenAI-compatible API directly (no credits, no CI-1T auth needed). Response: { scores: [u16, u16, u16], normalized: [f64, f64, f64], responses: [str, str, str], method, mode }. The returned scores array can be passed directly to evaluate for full stability classification.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | OpenAI-compatible API base URL for BYOM mode (e.g. http://localhost:11434/v1, https://api.openai.com/v1). When set, probes this endpoint directly instead of CI-1T backend. |
| method | string | – | Similarity method (default: jaccard) |
| model | string | – | Model name for BYOM mode (e.g. gpt-4o, claude-sonnet-4-20250514, llama3, mistral). Required when base_url is set. |
| model_api_key | string | – | API key for the target LLM provider (BYOM mode). Sent as Bearer token in Authorization header. |
| prompt | string | yes | The prompt to send 3 times to the LLM |
No output schema declared.
No examples provided.
visualize ~131
Generate an interactive HTML visualization of CI-1T evaluate results — no API call, no auth, no credits. Takes an episode array from evaluate or fleet responses. Returns a file path to a self-contained HTML chart with sidebar KPIs, color-coded CI bars, EMA trend, authority levels, and hover tooltips. Response: { visualization: filepath, episodes, title, instruction }. Open the file in a browser or VS Code Simple Browser.
| Name | Type | Req | Description |
|---|---|---|---|
| episodes | array | yes | Episode array from an evaluate or fleet_evaluate response |
| title | string | – | Chart title (default: CI-1T Stability Analysis) |
No output schema declared.
No examples provided.
What is the io.github.collapseindex/ci1t-mcp server?
io.github.collapseindex/ci1t-mcp is listed in the public MCP registry as io.github.collapseindex/ci1t-mcp. CI-1T prediction stability engine. Detect ghosts, evaluate drift, monitor fleets. 20 tools. This page covers its npm package (@collapseindex/ci1t-mcp).
Is the io.github.collapseindex/ci1t-mcp server safe to use?
io.github.collapseindex/ci1t-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.collapseindex/ci1t-mcp server expose?
io.github.collapseindex/ci1t-mcp exposes 20 tools: onboarding, evaluate, fleet_evaluate, probe, health, and 15 more. Their descriptions and schemas cost roughly 2,378 tokens of context every time the server is loaded.
Is the io.github.collapseindex/ci1t-mcp server still maintained?
io.github.collapseindex/ci1t-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.