Harbor MCP · /0.5

The engine as a plug-in brain.

A read-only Model Context Protocol server that wires outside agents and side bots into the Harbor ecosystem — Claude connectors, GPT tools, custom stacks. Probability surfaces as a service.

https://phillipsharbor.com/mcp

Four Tools

Small surface. Whole engine.

ask_probability(conditions, ticker?, as_of?, context_for?)

Given this indicator state, what happened next? Seven horizons, each with win rate, effective sample size, baseline, posterior, lift, P(lift>0), and a CI90 credible interval.

scan(tickers)

Current extremes and context-scoped labels — legacy and lift — for up to 20 tickers in one call.

analyze(ticker, full?)

The full cascade read on one ticker: state, extremes, forward distributions, narrative, and the environment the answer was scoped in.

calibration_report()

The report card. Every probability the engine quotes is graded nightly against what actually happened — the calibration curve per bucket, public.

Why It Is Different

Every answer ships with its own honesty.

as_of

Causal cutoff

Ask as of any past date and the answer uses only what was knowable then. Agents doing backtest research get walk-forward honesty for free.

context_for

Environment scoping

Scope the answer to a ticker's current environment — market regime, post-earnings window. Lift becomes context-conditional, not a pooled average.

calibration

Auditable trust

Trust is not asserted, it is graded. The same nightly reliability curve that disciplines the engine is exposed as a tool.

Security Model

Read-only by construction. No write tools. Strategy activation, order flow, and the live book stay behind Harbor's signed-bundle governance — unreachable from this surface.
Bearer token, fail-closed. No token configured means nothing answers. Keys are provisioned per engagement today; tier-based keys arrive with commercial access.
Four tools, enforced by construction. The engine connector is a separate process that only registers these four research tools — operator data (scans, trades, reports) lives on a different service behind a different key and is never loaded here. A build test fails if that boundary ever drifts.

Connect a Client

claude mcp add harbor-engine \
  https://phillipsharbor.com/mcp \
  --transport http \
  --header "Authorization: Bearer <your-key>"

Works with any MCP-capable client — Claude connectors, Claude Code, or a custom agent stack speaking streamable HTTP.

Wire your agents into Harbor.

Access keys are provisioned per engagement while commercial tiers are finalized.

Request a Key Explore the Engine