Serveur MCP PitBridge
✓ VérifiéConnecte les agents IA aux comptes de futures NinjaTrader 8 via un daemon local doté de garde-fous de risque déterministes.
Aussi connu sous ToolstackVault/pitbridge
- Étoiles
- 1
- Outils
- —
- Téléchargements, 30 jours
- 240
- Dernière version
- 0.2.2
- Dernier commit
- 16 juil. 2026
- Licence
- Apache-2.0
Qu'est-ce que PitBridge MCP ?
PitBridge est un serveur MCP. Connecte les agents IA aux comptes de futures NinjaTrader 8 via un daemon local doté de garde-fous de risque déterministes.
Résumé généré à partir du README du projet
À propos du MCP server PitBridge
PitBridge fournit une infrastructure locale pour connecter les agents IA aux comptes de futures NinjaTrader 8. Il fonctionne comme un daemon s'exécutant sur votre propre machine, prenant en charge macOS, Linux ou Windows. Le système utilise un daemon basé sur Python pour communiquer avec des clients IA tels que Claude Desktop ou Claude Code via MCP via stdio ou streamable HTTP. Il propose également une API REST et un flux d'événements WebSocket pour l'intégration.
La sécurité est gérée par un moteur de garde-fous déterministe situé entre l'agent et le courtier. Ce moteur applique des règles telles que l'arrêt en cas de perte quotidienne, le plafonnement des positions et les fenêtres de trading. Comme ces garde-fous sont codés en dur et ne font pas partie du prompt du LLM, un agent ne peut ni les contourner ni modifier les limites de risque. Un AddOn NinjaTrader 8 en C# gère l'exécution réelle des ordres via l'API Account officielle. L'intégralité du flux d'ordres reste locale à votre matériel, garantissant que les clés et les positions ne parviennent jamais à des serveurs externes.
Ce que vous pouvez faire avec
- 1Appliquer une gestion des risques stricteUn agent IA peut tenter de placer des transactions, mais le système bloquera automatiquement tout ordre dépassant les limites de contrats prédéfinies ou les seuils de perte quotidienne.
- 2Auditer les décisions de trading de l'agentLes développeurs peuvent consulter un journal infalsifiable pour comprendre exactement pourquoi un ordre spécifique a été autorisé ou rejeté par le système.
- 3Tester la logique de trading en toute sécuritéVous pouvez exécuter le daemon sur un Mac en utilisant un simulateur AddOn fictif pour observer comment les garde-fous réagissent à différents scénarios d'ordres sans avoir besoin d'une machine Windows ou de données de marché réelles.
- 4Implémenter un bouton d'arrêt d'urgence manuelUn opérateur humain peut interrompre instantanément toute activité de trading via la ligne de commande, empêchant l'IA d'exécuter de nouveaux ordres.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer PitBridge MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller PitBridge MCP dans Claude Code
$ claude mcp add pitbridge -- uvx pitbridgeInstaller PitBridge MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pitbridge": {
"command": "uvx",
"args": [
"pitbridge"
]
}
}
}Installer PitBridge MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"pitbridge": {
"type": "stdio",
"command": "uvx",
"args": [
"pitbridge"
]
}
}
}Installer PitBridge MCP dans VS Code CLI
$ code --add-mcp '{"name":"pitbridge","type":"stdio","command":"uvx","args":["pitbridge"]}'Installer PitBridge MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pitbridge": {
"command": "uvx",
"args": [
"pitbridge"
]
}
}
}Installer PitBridge MCP dans Codex
$ codex mcp add pitbridge -- uvx pitbridgeInstaller PitBridge MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.pitbridge] command = "uvx" args = ["pitbridge"]
Installer PitBridge MCP dans Gemini CLI
$ gemini mcp add -s user pitbridge uvx -- pitbridgeInstaller PitBridge MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pitbridge": {
"command": "uvx",
"args": [
"pitbridge"
]
}
}
}Vérifications automatisées
Exécuté le 15 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibletoolstackvault/pitbridge is public and reachablegithub.com/toolstackvault/pitbridge ↗Réussi
- Le nom du package correspond au dépôt sourcepitbridge names toolstackvault/pitbridge as sourcepypi.org/project/pitbridge/ ↗Réussi
- Provenance du build (attestation Sigstore)No build attestation published for this releaseNon vérifié
- Licence open source (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-07-16github.com/toolstackvault/pitbridge ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from pitbridgeRéussi
- Aucun avis critique dans le package ou ses dépendances42 resolved dependencies checked; no critical advisoryosv.dev ↗Réussi
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubPitBridge
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.CbiAccount 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 <id>explains any order;pitbridge audit verifyproves 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 <id>(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.
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 similar to those shown.
Questions sur PitBridge MCP
Comment ajouter PitBridge MCP à Claude Code ?
Exécutez claude mcp add pitbridge -- uvx pitbridge dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter PitBridge MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Un agent IA peut-il contourner les limites de risque ?
Non, les garde-fous sont déterministes et intégrés directement dans le code plutôt que dans les prompts ; l'agent ne possède pas les outils nécessaires pour les affaiblir ou déverrouiller le trading réel.