Tradeledger

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 4, 2026

Read the iBitLabs live trading experiment: account status, recent trades, rules and saga.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Read-only MCP client that lets an assistant quote the live iBitLabs trading experiment: balance, trades, shadow rules and saga.

What you can do
  • Read account status: balance, total PnL, win rate, trade count, market regime and any open position
  • List recent closed trades with direction, exit reason, PnL, regime, MFE and MAE
  • List contributor-proposed shadow rules filtered by adopted, queued or all
  • Inspect one rule's per-bucket hit rates and distance from its promotion bar
  • Fetch the latest narrated saga chapter in English or Chinese
When to use it
Useful when you want an assistant to report the experiment's real figures instead of plausible-sounding numbers, for example answering questions about current performance, recent trades or rule progress.
Requirements
Runs locally via npx or Docker (stdio). No credentials are needed or accepted. It forwards every call to one upstream MCP endpoint, configurable with IBITLABS_MCP_URL (default and needs network access; REQUEST_TIMEOUT_MS sets the per-request timeout.
Before you install
All five tools are read-only; there is no order, wallet or account-write operation. Calls are forwarded to a third-party upstream endpoint, so the queries and their results leave your machine. The endpoint and forwarding shape are labelled reconstructions, so figures depend on that upstream and errors come back as tradeledger error: text.

Installation

In SourceWeft

  1. Open Tradeledger in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

tradeledger

A read-only window onto a live trading experiment. tradeledger lets an agent quote the experiment's actual state — its current balance and open position, the trades it has actually closed, the contributor shadow rules it runs, and the story it tells about itself — instead of inventing plausible numbers.

Nothing here trades. The five tools only read public data; there is no order, wallet, or account-write operation in the surface, and no credential is needed or accepted.

Tools

ToolArgumentsWhat it answers
get_live_status—Balance, total PnL, win rate, trade count, market regime, and the open position if one is running.
get_recent_tradeslimit (optional integer)The most recent closed trades, each with direction, exit reason, PnL, and regime.
list_adopted_rulesstatus (optional: adopted, queued, or all)The contributor-proposed shadow rules, filtered by where they stand.
get_rule_statusrule_id (required string)One rule's per-bucket hit rates and how far it sits from its promotion bar.
get_latest_saga_chapterlang (optional: en or zh)The newest entry in the experiment's narrated saga.

How it works

tradeledger is a forwarding client. A tool call is packaged as a JSON-RPC tools/call request and sent to a single upstream MCP endpoint; whatever the upstream returns is handed back untouched. When the upstream fails, the answer is an error text beginning tradeledger error: — never a locally invented figure.

Provenance

The endpoint and the forwarding shape are labelled reconstructions. The original server's public description names its data sources in prose but publishes no per-tool endpoint, so this rebuild points every call at one configurable upstream:

  • IBITLABS_MCP_URL — upstream MCP endpoint. Default: https://www.ibitlabs.com/api/mcp (labelled reconstruction).
  • REQUEST_TIMEOUT_MS — per-request timeout. Default: 15000.

Run it as an MCP server

json
{  "mcpServers": {    "tradeledger": {      "command": "npx",      "args": ["-y", "@reneturcios/tradeledger", "mcp"]    }  }}

Or in a container:

bash
docker run -i ghcr.io/cloudcorprecords/tradeledger

Run it as a CLI

bash
npx @reneturcios/tradeledger get_live_status '{}'npx @reneturcios/tradeledger get_recent_trades '{"limit": 2}'npx @reneturcios/tradeledger get_rule_status '{"rule_id": "F"}'npx @reneturcios/tradeledger --version

Each tool subcommand takes exactly one JSON object string with the tool's arguments and prints the result text. Exit codes are 0 on success, 1 on an error result, and 2 on a usage error.

Development

bash
npm installnpm run build   # tsc -> dist/ (dist/cli.js is the bin)npm test        # tsx --test test/*.test.ts — offline; the upstream is stubbednpm run dev     # tsx src/cli.ts — run the CLI from source

The test suite never touches the network: it drives the core with a stubbed JSON-RPC upstream whose payloads are the public worked-example responses, and checks they pass through untouched, that failures become tradeledger error: results, and that the served tool list matches the contracted five tools exactly.

License

MIT. See LICENSE.

Source: README.md at commit 3f47566

Tools

5

get_live_status

Current balance, PnL, win rate, open position, reconciliation

Takes no parameters.

get_recent_trades

Last N closed trades with entry/exit/PnL/regime/MFE/MAE

Parameterslimit

list_adopted_rules

Contributor-proposed shadow rules (adopted | queued | all)

Parametersstatus

get_rule_status

Per-rule bucket hit-rates + distance from promotion bar

Parametersrule_idrequired

get_latest_saga_chapter

Latest narrated saga entry (en | zh)

Parameterslang

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts