Reference

MCP

The same four questions as an agent's tools, over the same key, reaching the same endpoints. One way in and one meter.

Connect

A remote server over streamable HTTP. The trailing slash matters — /mcp redirects to it.

{ "mcpServers": {
    "priorcase": {
      "type": "http",
      "url": "https://priorcase.com/mcp/",
      "headers": { "Authorization": "Bearer pc_live_…" }
    } } }

A client that speaks RFC 9728 needs no header here: an unauthenticated call answers 401 naming /.well-known/oauth-protected-resource/mcp, and the client goes there for where to send a token. See authentication.

The four

Each reaches the endpoint beside it, carrying your key, and is counted the same way.

find_analogsGET /v1/search: The past moments whose price path most resembles a given one, with what followed each.
market_stateGET /v1/moment/{at}: What the market was at one moment: the returns over 1h to 30d, the day's high and low, the volume, and how wild it was against its own month.
query_historyGET /v1/when: The moments a condition became true, most recent first, each with what was known then and what followed.
outcomesGET /v1/paths: The paths a search compared, to draw side by side or over each other.

What an agent is told first

The server's own instructions say what it will and will not do, so a model does not have to infer it from the tool names: it answers what happened, not what will happen; every tool returns past moments and the price paths that actually followed them; there are no forecasts, probabilities or averages; and nothing in it is advice.

It is listed in the public MCP registry as com.priorcase/priorcase.