Agent surface · Model Context Protocol

MCP

Chromatic for agents: the same live reads and versioned libraries this site renders, as machine-readable JSON today and a remote MCP server next.

Read surface · public, no keys

What an agent can read right now

Every surface below is already serving. Nothing here needs an account, a key, or a wallet.

Live · JSON/api/live-proposals

Confirmed Futarchy v0.6 program state: pending markets, proposal thresholds, and current pass/fail TWAPs, with retained observation series.

 Live · JSON/api/protocol-quotes

Price, 24-hour change, market cap, and volume for tracked protocols, from public ticker and pair feeds.

 Versioned · JSON/vectors/library.json

The attack-vector library: monitored and documented vectors, their indicators, the evidence each detector consumes, and published case provenance.

 Versioned · JSON/vectors/teams.json

The six bounded color-team contracts: versioned inputs, outputs, handoffs, and boundary rules.

 Sourced · JSON/data/catalog.json

The cited protocol catalog rendered from the sourced cache, with each row's provenance.

 Sourced · JSON/data/history.json

The append-only history lane: dated treasury readings and every proposal identity a pull has seen.

 Versioned · JSON/faq/faq.json

The public FAQ as a saved data structure — scope, classifications, and engagement boundaries.

 Index · text/llms.txt

The plain-text site index written for language models.
Endpoint · Streamable HTTP

The MCP server wraps these as tools

Standing up

A remote MCP server is standing up on the same Cloudflare account that serves this site: the reads above wrapped as typed, read-only tools, so an agent can call them without scraping HTML. The read surface stays public — no accounts and no keys. Until the endpoint ships, the JSON above is the agent surface.

Tools answer with the same restraint as the pages. Withheld lanes return withheld, documented vectors never classify, and missing evidence never becomes a rating.

Waitlist

One email when it ships

Leave an address and we send a single note when the endpoint is live. The address, the optional note, this page's name, and the submission time are the only things stored — the privacy page is the contract.

Checking whether signups are open…

Back to Chromatic