Pitbridge

Name: Pitbridge
Author: ToolstackVault

by ToolstackVaultversion 0.2.2i★ –iRuns on your computer

Registry namecom.pitbridge/pitbridge

Install

Overview

Description from the maker (original English)

Local-first MCP bridge for NinjaTrader 8 behind a deterministic guardrail engine.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "pitbridge": {
      "command": "uvx",
      "args": [
        "pitbridge",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add pitbridge -- uvx pitbridge mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pitbridge": {
      "command": "uvx",
      "args": [
        "pitbridge",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pitbridge": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "pitbridge",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain pitbridge.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32398 servers in this category
Published to the registry more recently than 17% of the other 32398 servers in this category
Basic checks equal to or better than 100% of the other 32398 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Pitbridge safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, AI Deprecations

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

AI Deprecations

by aideprecations.com

AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

PitBridge

A local-first MCP bridge for NinjaTrader 8, with hard risk limits your AI cannot bypass.

PitBridge connects an AI agent (Claude Code, Claude Desktop, or your own script) to a NinjaTrader 8 futures account through a daemon that runs on your own machine. Every order the agent asks for passes through a deterministic guardrail engine first. The guardrails are default-on, they live in code rather than in prompts, and the agent has no tool to weaken them, unlock live trading, or release the kill switch.

We build rails, not alpha. PitBridge does not tell you what to trade.

What it is

A local-first daemon (Python 3.12) that speaks MCP (stdio and streamable HTTP), a REST API, and a WebSocket event feed. It runs on macOS, Linux, or Windows.
A deterministic guardrail engine: pure, synchronous checks (daily-loss halt, position caps, trading windows, rate limits, a kill switch, and more) that every order must pass before it can reach the broker.
A thin NinjaTrader 8 AddOn (C#) that connects out to the daemon and places orders through the official NinjaTrader.Cbi Account API. The AddOn is deliberately dumb: all safety lives in the daemon.
An append-only, hash-chained audit log that records every request, decision, and outcome, and can tell you exactly why any order was allowed or blocked.

What it is NOT

Read this section before anything else.

Not a broker or an exchange. PitBridge routes orders you (or your agent) create to your existing NinjaTrader account. It holds no funds and executes nothing itself.
Not signals, strategies, or alpha. PitBridge ships no trading logic. It will not tell you what, when, or how much to trade. That is your job, or your agent's.
Not financial or investment advice. It is trading infrastructure.
Not a guarantee of prop-firm compliance. You configure the limits that match your firm's rules. PitBridge helps you encode and enforce them locally, but you remain responsible for staying within your firm's terms. We make no compliance guarantee.
Not a cloud order relay. Orders, keys, and positions never touch our servers. There is no PitBridge account in the order path.
Not autonomous. Enabling live execution is an operator-only ritual at the command line. The agent cannot arm live trading, and it cannot lift a kill.

Architecture

The entire order path is local. PitBridge's own cloud (the marketing site, the docs, software updates) is never in it.

   AI agent   (Claude Code / Claude Desktop / your own script)

│ │ MCP (stdio or HTTP) REST /v1/* WS events ▼ PitBridge daemon ← runs on YOUR machine │ │ frozen pipeline (no code path skips it): │ schema → permission → GUARDRAILS → confirm → submit → audit ▼ Guardrail engine (deterministic, default-on, not reconfigurable by the agent) │ │ WebSocket on :8873 (the AddOn dials OUT; the NT8 box never listens) ▼ NT8 AddOn (C#, .NET 4.8, next to NinjaTrader 8 on Windows) │ │ NinjaTrader.Cbi Account API (close / flatten are strictly reduce-only) ▼ NinjaTrader 8 → your broker / prop account (CQG, Rithmic, ...)

PitBridge's own cloud is NOT on this path. Orders, keys, and positions never leave your machine(s).

Two run modes:

Localhost (default): the daemon and NinjaTrader run on the same Windows machine, bound to 127.0.0.1.
Paired: the daemon runs on, for example, your Mac, and the NinjaTrader AddOn connects out to it over your own private network (Tailscale / LAN). This is the "runs on your Mac, your Windows box, or both" setup. Non-localhost binds are refused unless paired mode is explicitly enabled and a pairing token is configured.

Safety model in short

Deterministic guardrails. The engine is a set of pure functions with no I/O and no LLM in the loop: check(request, state, now) returns Allow, Block (with a typed reason code), or RequireConfirm. Given the same inputs it always returns the same decision, and that decision is testable.
A frozen pipeline. Every order takes exactly one path: schema validation, then permission (read-only / paper / live), then the guardrail chain, then an optional human-confirm gate, then submit, then an audit append. There is no route from the agent surface to the broker that skips it. A structural test in CI fails the build if any code tries.
The agent cannot reconfigure safety. Limits live in an on-disk config that is checksum-verified. No MCP tool can edit config, raise a limit, un-kill, or arm live trading. Those controls exist only at the operator's command line.
Local-first. The daemon runs on your machine(s). Orders, keys, and positions never reach a PitBridge server.
Kill switch. A file, the CLI, or a REST call can engage it instantly. Only the CLI (a human at the keyboard) can release it. De-risking (cancel, close, flatten) is deliberately still allowed under a kill, so you can always get flat.
Tamper-evident audit log. Append-only, hash-chained JSONL with an out-of-file anchor. pitbridge audit why explains any order; pitbridge audit verify proves the chain is intact and catches edits, truncation, or a wiped tail.

The guardrails

Twelve v0 guardrails, each its own module, all table-tested. The chain runs in a frozen order: the kill switch is checked first, the human-confirm gate last.

Kill switch: file, CLI, or REST engages it; release is CLI-only, never an agent tool.
Daily-loss halt: per-account day ledger with New-York rollover; can latch sticky for the rest of the day once breached.
Profit lock: stop trading for the day after a configured profit.
Max contracts per order: reject any single order above the cap.
Max position per instrument and account: cap net exposure, and refuse an over-cap position flipping to an equally over-cap opposite side.
Instrument allowlist: only configured contracts may be traded.
Trading windows and holiday calendar: per-account timezone, holiday and early-close aware.
Cooldown: a minimum spacing after a loss and/or after an order.
Order rate limits: caps per minute, per hour, and per day.
Duplicate-order protection: same account, instrument, side, and quantity within N seconds is rejected.
Link-down block: if the heartbeat to the AddOn goes stale, new orders hard-reject rather than queue against a dead link.
Human-confirm gate: parks an order as PENDING_CONFIRM, pings a notifier, and waits for pitbridge confirm (or a REST approval); auto-rejects after 60 seconds.

Open-core boundary

PitBridge is open-core. The safety kernel is open so it can be read and trusted. Live execution and the operational suite for running many accounts are the paid tier.

Open source (free)	Pro (paid)
The daemon and the full guardrail engine	Live-execution unlock (the private `LiveExecutionProvider` plugin)
The MCP, REST, and WebSocket agent surface	The advanced guardrail suite and prop-firm rule packs
Read-only tools and paper trading (against the fake AddOn / simulation)	Multi-account fan-out (one tool call, N accounts)
The CLI and the hash-chained audit log	The human-confirm UI and audit export

This is licensing-gating, not DRM. The core is fully functional for read-only and paper use on its own. Live trading requires the Pro plugin plus a deliberate, operator-only arm-live step.

Quickstart

You can run the complete daemon on a Mac today, with no NinjaTrader install, no Windows box, and no market data. A fake AddOn simulator stands in for the real C# AddOn, so you can watch the guardrails pass good orders, block bad ones with a typed reason, stop everything with the kill switch, and explain every decision from the audit log.

cd daemon

uv sync --extra dev uv run pitbridge run --config ./config.toml # terminal A uv run python ../tools/fake_addon.py \ # terminal B --host 127.0.0.1 --port 8873 --token pb_pair_demo --account Sim101

Then place a paper order over REST or wire up Claude as the MCP client and ask it in plain language. The full walkthrough, a ready-to-paste config, the Claude Desktop / Claude Code MCP setup block, five test scenarios, and a "try to break it" section are in [docs/testing-on-mac.md](docs/testing-on-mac.md).

Everything in the quickstart is paper / simulation. See that guide's "What this does and does not prove" for the honest boundary.

Status and roadmap

PitBridge is early and pre-launch. We are honest about what exists versus what is planned.

Built and tested today (paper / simulation only):

the daemon core, the full guardrail engine (all twelve guardrails), the day ledger, and the hash-chained audit log;
the MCP server (nine tools), the REST API, the WebSocket event feed, and the CLI;
a scripted fake AddOn for end-to-end and chaos testing;
a table-driven test suite (300+ tests) that runs on macOS, Linux, and Windows in CI, including prompt-injection and no-bypass tests.

In progress:

the real C# NinjaTrader 8 AddOn (order routing on a Sim101 account), with close and flatten implemented as strictly reduce-only.

Planned:

shadow-mode validation, running PitBridge in parallel with our own live prop-trading operation to prove order-intent parity before it ever routes a live order;
a supervised, operator-gated live migration;
the open-core public launch, the website, and full docs;
additional platforms (Tradovate, ProjectX / TopstepX) via thin adapters.

No live account has been traded through PitBridge yet. Live routing sits behind an operator-only ritual and is not part of the current build.

Documentation

docs/architecture.md: the binding architecture and safety spec.
docs/testing-on-mac.md: run and test the daemon on a Mac against the fake AddOn.
SECURITY.md: how to report a vulnerability.
CONTRIBUTING.md: how to contribute, and the rules for safety-critical changes.

Disclaimers

Trademarks. NinjaTrader is a registered trademark of NinjaTrader Group, LLC. CQG, Rithmic, and any prop-firm names are trademarks of their respective owners. PitBridge is an independent project and is not affiliated with, endorsed by, or sponsored by NinjaTrader Group, LLC, any data or clearing provider, or any prop firm. Platform names are used nominatively, only to describe compatibility.

Not financial advice. PitBridge is trading infrastructure, not financial, investment, or trading advice. It provides no signals, strategies, or recommendations.

Risk. Trading futures involves substantial risk of loss and is not suitable for every investor. You are solely responsible for your own trading decisions and for staying within the terms of any broker or prop firm you use.

CFTC Rule 4.41 (hypothetical and simulated performance). Any results, examples, or simulated data shown for PitBridge are hypothetical or simulation-based. Simulated performance has inherent limitations: unlike a live record, simulated results do not represent actual trading, and because the trades were not actually executed, they may under- or over-compensate for factors such as lack of liquidity. No representation is being made that any account will or is likely to achieve profits or losses s

Only the beginning is shown; read the rest in the repo

Pitbridge

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

AI Deprecations

README from the maker

PitBridge

What it is

What it is NOT

Architecture

Safety model in short

The guardrails

Open-core boundary

Quickstart

Status and roadmap

Documentation

Disclaimers