com.ibitlabs.www/ibitlabs-mcp
NPM · IBITLABS-MCP · SCANNED SEP 21
iBitLabs live receipts: real balance, trades, shadow rules & saga from a $1k→$10k AI experiment.
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 & Transparency19
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 139 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 497 tokens (~99/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 com.ibitlabs.www/ibitlabs-mcp server?
com.ibitlabs.www/ibitlabs-mcp runs locally as an npm package, launched with npx -y ibitlabs-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 · ibitlabs-mcp
claude mcp add com-ibitlabs-www-ibitlabs-mcp -- npx -y ibitlabs-mcp
{
"mcpServers": {
"com-ibitlabs-www-ibitlabs-mcp": {
"command": "npx",
"args": [
"-y",
"ibitlabs-mcp"
]
}
}
} {
"servers": {
"com-ibitlabs-www-ibitlabs-mcp": {
"command": "npx",
"args": [
"-y",
"ibitlabs-mcp"
]
}
}
} codex mcp add com-ibitlabs-www-ibitlabs-mcp -- npx -y ibitlabs-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ibitlabs-www-ibitlabs-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"ibitlabs-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-ibitlabs-www-ibitlabs-mcp --command npx --arg -y --arg ibitlabs-mcp
mcp_servers:
com-ibitlabs-www-ibitlabs-mcp:
command: "npx"
args: ["-y", "ibitlabs-mcp"] {
"McpServers": {
"com-ibitlabs-www-ibitlabs-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"ibitlabs-mcp"
]
}
}
} assistant mcp add com-ibitlabs-www-ibitlabs-mcp -t stdio -c npx -a -y ibitlabs-mcp
{
"mcpServers": {
"com-ibitlabs-www-ibitlabs-mcp": {
"command": "npx",
"args": [
"-y",
"ibitlabs-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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 21 Sept 2026 · Analysed npm/ibitlabs-mcp@0.2.2
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 →
get_latest_saga_chapter ~91
Latest saga chapter narrating the experiment in human prose — pulls from /data/saga_vol2.json and returns the entry for the requested language. Use when you want a human-readable summary of the most recent state, not just numbers. The saga is updated daily (or near-daily) and pairs with the trading data above.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Saga language. Default `en`. |
No output schema declared.
No examples provided.
get_live_status ~78
Current account snapshot from the live $1k → $10k experiment: balance, total/unrealized PnL, win rate, fees, funding cost, current open position (if any), reconciliation timestamp. Sourced from /api/live-status. Use when you need the actual current state of the bot instead of a backtest figure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recent_trades ~89
List the most recent N closed trades with entry/exit/PnL/regime tags. Use this to cite real fills (e.g. for a research post or an example in a strategy doc). Sourced from /data/recent_trades.json, regenerated after each morning/evening sniper check.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of recent closed trades to return (1-100). |
No output schema declared.
No examples provided.
get_rule_status ~126
Per-rule shadow log statistics: number of fires, per-bucket hit rates, distance from the 4-condition promotion bar (≥30/bucket, ≥15pp spread, direction match, no confounding shadow). Use when reviewing whether a contributor's rule is on track to graduate from log-only shadow to a real entry gate. Sourced from /data/rule_status.json, regenerated after each morning/evening sniper check.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | Single uppercase letter rule id (e.g. 'C', 'D', 'E', 'F', 'G'). |
No output schema declared.
No examples provided.
list_adopted_rules ~113
List all contributor-proposed shadow rules: adopted (in production observation-only mode, with 30-day promotion windows) and queued_for_review (proposed but not yet wired). Each row carries proposer handle, frame, source post URL, rule_id, code_location, shadow_log path, review window, and current points. Sourced from /data/contributors.json. Use to see who has contributed encodable frames to the bot.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by review_status. Default is `all`. |
No output schema declared.
No examples provided.
What is the com.ibitlabs.www/ibitlabs-mcp server?
com.ibitlabs.www/ibitlabs-mcp is listed in the public MCP registry as com.ibitlabs.www/ibitlabs-mcp. iBitLabs live receipts: real balance, trades, shadow rules & saga from a $1k→$10k AI experiment. This page covers its npm package (ibitlabs-mcp).
Is the com.ibitlabs.www/ibitlabs-mcp server safe to use?
com.ibitlabs.www/ibitlabs-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 com.ibitlabs.www/ibitlabs-mcp server expose?
com.ibitlabs.www/ibitlabs-mcp exposes 5 tools: get_live_status, get_recent_trades, list_adopted_rules, get_rule_status, get_latest_saga_chapter. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.
Is the com.ibitlabs.www/ibitlabs-mcp server still maintained?
com.ibitlabs.www/ibitlabs-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.ibitlabs.www/ibitlabs-mcp server under?
com.ibitlabs.www/ibitlabs-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.