Pit Officer runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 28 Oct 2026.
Pre-trade risk limits for AI trading agents: every order is checked before it reaches your broker.
What the code does
We read the source, 24 min ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
select {
case <-runCtx.Done():
return
case <-ticker.C:
tick++
if !c.emitTick(runCtx, subs, tick, out) {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Pit Officer
same job, measured the same wayAn AI agent's trading mandate it can't break: checked before every order, reasoning sealed in IRL.
Polymarket paper trading for AI agents: $10k paper money, real order books, official fees.
Compliance, risk, tax and audit checks for AI trading agents: pre-trade, sizing, wash sales, Reg BI.
Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.
Risk guardrails for AI trading agents. Your agent proposes; your policy decides.
Risk limits and an audit log for AI agents trading Hyperliquid, enforced outside the model.
Simulated stock markets that react to your orders: run, fork and score trading agents.
AI agents backtest, paper trade and live trade via your broker. Free to connect; OAuth.
Pit Officer — questions
Answers built from our own checks of this server.