headless.biddevelopers
v1Sandbox console
Sandbox available · Production unavailable

Inspect Sandbox through hosted MCP

Connect an OAuth-capable MCP client to https://mcp.headless.bid/mcp. The resource discovers oauth.sandbox.headless.bid through RFC 9728 and accepts only tokens issued for this exact MCP audience.

Try the Sandbox path

  1. 1

    Open your Sandbox first

    Complete Sandbox signup so the client can ask you to choose a real Workspace and Environment.

  2. 2

    Add the hosted endpoint

    Configure https://mcp.headless.bid/mcp as a remote MCP server in a client that supports OAuth.

  3. 3

    Review consent in the browser

    Sign in and approve only the displayed Sandbox, redirect origin and scopes.

  4. 4

    Ask a useful first question

    Try: List the lots in my current headless.bid Sandbox, then show the live state of the first open lot.

OAuth client requirements

Dynamic Client Registration is intentionally unavailable. The authorization screen shows the client, Workspace, Environment, scopes and exact redirect origin before approval. Access tokens last five minutes; refresh grants last at most 24 hours and are rechecked against current Membership.

Tool surface

ToolResultAuthority
workspace_contextSelected opaque Workspace and EnvironmentRead-only
inventory_listBounded auction or Lot pageRead-only
lot_snapshotSanitized authoritative Lot stateRead-only
attention_listDelivery attention metadataRead-only
evidence_listSealed-evidence metadataRead-only
prepare_pauseExpiring Web review linkRead-only handoff; Web + tenant approval required

Data boundary

The MCP Worker has no database, R2, Queue, Durable Object, Engine or credential-custodian binding. It sends a bearer-free principal to a narrow Platform read service, which rechecks the live Workspace membership. Tool results reject secret, token, private-key, subject and bidder-identity fields and are capped at 256 KiB.