MCP onboarding

One tool set, two transports: CLI stdio for local compute, Streamable HTTP for remote agents. The four tool names are identical on both.

Option A — stdio (local)

voltbase mcp

Stdio mode has full local compute, including the reliability rollups below. Point any MCP-compatible client at the command above.

POST /mcp   # JSON-RPC: tools/list, then tools/call
GET /mcp    # 405 — stateless, there is no session stream to hold

Tool	Arguments	Answers
`voltbase_search_sites`	`bbox`, `connector`, `minPower`, `openOnly`, `limit`, `offset`	Paged servable rows plus per-partition attribution credits
`voltbase_site_detail`	`id` (for example `OCM:900000`)	One servable row, or typed `NOT_FOUND`
`voltbase_status`	`id`, optional `after` (ISO instant, newer-only polling)	Status plus the 60-minute stale label; `newer:false` when nothing is newer than `after`
`voltbase_reliability`	`id`	Uptime rollups for the site from the prebuilt reliability cut, with attribution; the stale label applies beyond the refresh SLO

Results are JSON-in-text; every served payload carries attribution and provenance.
Unknown arguments answer typed INVALID_ARGUMENTS (strict schemas, no silent drops).
Closed or unknown ids answer typed NOT_FOUND — the tools never confirm that a closed row exists.
BYOK is per request and by name (OCM_API_KEY); key values are never logged, stored or echoed. Missing key means a typed skip, not a failure.