Phase 1
MCP servers

Source: c81 phase1-pages — MCP servers (PRO-29); Cam's Directive 1 (Configured vs Connected two-state panel, tool manifest with ghosted approval) + report-inventory-v1 reviewed/unreviewed rows, re-derived from the phase1 world

fixture state

12 MCP servers, 11 reviewed — browser on 2 installs, calling, unreviewed and undeclared.

212 calls · 30d · hubspot configured on 1 install, never connected (OAuth pending since Aug 18) · +1 more

Configured vs Connectedof 12 servers · 33 install declarations · 31 install connections

Servers

ranked unreviewed → connected-undeclared → configured-never-connected → calls
Transport
Provenance
Configured
Connected
Calls · 30d
Denied
Tools
OAuth
Reviewed
Last call
browserstdioobserved0
undeclared
221203
0 allowlisted
noneunreviewed3h ago
hubspothttpdeclared10
never connected
001pendingAug 18never
githubstdiodeclared87
1 idle
1,84003noneJun 22h ago
google-drivehttpdeclared7773002connectedMay 122h ago
filesystemstdiodeclared1159002noneJun 22h ago
slackhttpdeclared6641222connectedMay 124h ago
postgresstdiodeclared21
1 idle
31201noneJun 22h ago
linearhttpdeclared3324402connectedJul 144h ago
figmahttpdeclared118801connectedJun 235h ago
sentryhttpdeclared21
1 idle
6102connectedJun 22d ago
snowflake-readonlyhttpdeclared112701noneJul 2814d ago
postgres-prodstdiodeclared11111
0 allowlisted
noneJul 2814d ago

12 servers — 11 configured (33 install declarations), 11 connected (31 install connections), 10 both; 1 connected without a declaration, 1 configured and never connected, 4 idle declarations across installs; 1 unreviewed. Calls and denials are 30-day fleet totals summed from each server's tools; sessions are the 7-day sample on record.

Composition notes

  • Question: what's wired in, what's actually used, did anyone review it? Wired in = configured (declared in a synced config, instance.mcpServerIds); used = connected (observed at runtime, mcpServer.connectedOnInstanceIds) and calling; reviewed = the review record. The two witnesses disagree on purpose — Cam's Directive 1 — and the disagreement is the page.
  • Verdict line from mcpVerdict(world) (derived/mcp.ts, to fold into verdicts.mcp): names the unreviewed server with its install and call counts, then the idle server and the stale declarations in the sub line. The clear state keeps the stale-declaration sentence — drift is a fact, not an alarm.
  • Framing band = the Configured vs Connected two-state panel: two 44px claims with their definitions as labels and the two disagreements (connected-undeclared · configured-never-connected) as smaller claims, all filter buttons; denominators at server grain in the values and at install grain in the caption. "Both" is configured ∧ connected — derivable at a glance, so it is a footer number, not a block. Outside the panel, unreviewed is the page's one attention device — the only amber on the page. Configured-vs-connected disagreement is said in words, never in color.
  • Table is the raw UxTableList family so ?id= can pre-open a row. Rows from mcpRollup(world), pre-ranked unreviewed → connected-undeclared → configured-never-connected → calls; sorters on every column; search rides the Server header (name, transport, provenance, people, tools). Provenance follows c68: undeclared = observed — a structural fact, so the pill is grey on every row; the Reviewed cell is the row's one colored element. Tools prints the count with "n allowlisted" beneath it when not all are; OAuth weights only pending; Reviewed prints the date alone (the reviewer is in the expand). The configured/connected cells carry undeclared / never connected / n idle as plain sub-words — the idle-server angle stated, not colored.
  • Expand = header (situation in one sentence + the server's note) → tool manifest (calls, denied, allowlisted as a quiet column with a ghosted approval toggle that links to the MCP allow-list policy page — approval is configured there, not here; the toggle is an affordance, not a control) → callers (installs as agent chips with each install's own configured/connected state, person, device; a people row) → sessions on record (→ Session detail) → an honest "view details →" stub: there is no MCP detail page in Phase 1.
  • Derivation: every number traces to mcpRollup / mcpBand / mcpConfiguredInstances / connectedOnInstanceIds / toolsForMcp / sessionsForMcp; per-server calls are the sum of the server's tools, never stored; nothing is fabricated for this page.
  • Open: the band counts "connected, undeclared" at server grain and prints the install pairs beside it — Cam's panel may have meant pairs; whether idle config graduates from words to an attention state needs a stated threshold.

Qpoint Brand Style Guide