# com.ibitlabs.www/ibitlabs-mcp (npm · ibitlabs-mcp)

iBitLabs live receipts: real balance, trades, shadow rules & saga from a $1k→$10k AI experiment.

- Trust score: 63/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `ibitlabs-mcp`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-ibitlabs-www-ibitlabs-mcp/ibitlabs-mcp.md), [page](https://verifymcp.io/servers/com-ibitlabs-www-ibitlabs-mcp/ibitlabs-mcp)

## Channel facts

- Registry: `npm`
- Package: `ibitlabs-mcp`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 90 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 497 tokens (~99/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add com-ibitlabs-www-ibitlabs-mcp -- npx -y ibitlabs-mcp
```

### Codex

```bash
codex mcp add com-ibitlabs-www-ibitlabs-mcp -- npx -y ibitlabs-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ibitlabs-www-ibitlabs-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ibitlabs-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ibitlabs-www-ibitlabs-mcp --command npx --arg -y --arg ibitlabs-mcp
```

### Hermes

```yaml
mcp_servers:
  com-ibitlabs-www-ibitlabs-mcp:
    command: "npx"
    args: ["-y", "ibitlabs-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-ibitlabs-www-ibitlabs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ibitlabs-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 59, +22)

- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Maintenance: pass → unverified
- [functional regression] License: pass → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: MIT

### 2026-07-31 (score 37, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 42, −30)

- [security regression] Known CVEs: partial → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: partial → unverified

### 2026-07-29 (score 72, +32)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT

### 2026-07-27 (score 40)

First indexed and scored.

## MCP tools (5)

### `get_live_status` (~78 tokens)

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.

### `get_recent_trades` (~89 tokens)

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.

Input parameters:

- `limit` (integer): Number of recent closed trades to return (1-100).

### `list_adopted_rules` (~113 tokens)

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.

Input parameters:

- `status` (string): Filter by review_status. Default is `all`.

### `get_rule_status` (~126 tokens)

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.

Input parameters:

- `rule_id` (string, required): Single uppercase letter rule id (e.g. 'C', 'D', 'E', 'F', 'G').

### `get_latest_saga_chapter` (~91 tokens)

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.

Input parameters:

- `lang` (string): Saga language. Default `en`.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-ibitlabs-www-ibitlabs-mcp/ibitlabs-mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 59
- 2026-08-01: 37
- 2026-07-31: 37
- 2026-07-30: 42
- 2026-07-29: 72
- 2026-07-28: 40
- 2026-07-27: 40

## Links

- npm package: https://www.npmjs.com/package/ibitlabs-mcp
- Socket report: https://socket.dev/npm/package/ibitlabs-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-ibitlabs-www-ibitlabs-mcp/ibitlabs-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ibitlabs-www-ibitlabs-mcp/ibitlabs-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-ibitlabs-www-ibitlabs-mcp/ibitlabs-mcp