Product Concierge MCP

Public, no-auth MCP server for learning about Arbiter. Answers come only from disclosure-boundary-reviewed product content — never customer org data.

Distinct from the authenticated MCP (mcp.arbiter.blockskunk.com) that runs RBAC tools over your register. Maturity: see Integration Surfaces.

LiveNo API keyArbiter · public concierge

Know what’s Live before you integrate

Install the public Concierge in Cursor. Ask about REST, MCP, and surface maturity — reviewed product docs only. Never customer org data.

Add to Cursor

Endpoint

https://ca-arbiter-concierge-dev.thankfulpond-c4b3beed.eastus2.azurecontainerapps.io/mcp

Production hostname after DNS: https://concierge-arbiter.blockskunk.com/mcp. Until then, Add to Cursor uses the live Azure URL above.

Accurate maturity

Live / gated / roadmap stays aligned with Integration Surfaces.

Disclosure-safe

Reviewed public content only. No org data, no invented SLAs or pricing.

No key required

Public endpoint for evaluators and agents exploring Arbiter.

Health check ↗Integration Surfaces

What it is

	Product Concierge	Authenticated MCP
Audience	Prospects, evaluators, agents exploring the product	Provisioned API key holders
Auth	None	`Authorization: Bearer arb_…`
Data	Public docs + curated talk tracks	Customer risks, controls, evidence, …
Status	Live	Live / Early Access

Tools

Tool	Purpose
`ask_product`	Natural-language Q&A over reviewed Arbiter content
`get_integration_surfaces`	Live maturity matrix (do not guess Live vs roadmap)
`request_demo`	Contact / briefing link (no CRM write)

Concierge tool handlers can run through OdinGard Cerberus (open core) for lethal-trifecta correlation. This is complementary agent-tool hardening — not Arbiter source of truth. Default mode is observe-only (CERBERUS_ALERT_MODE=log). See Integration Surfaces · cerberus-core.

Other clients

Claude Code

claude mcp add --transport http arbiter-concierge \
  https://ca-arbiter-concierge-dev.thankfulpond-c4b3beed.eastus2.azurecontainerapps.io/mcp

Claude Desktop / mcp.json

{
  "mcpServers": {
    "arbiter-concierge": {
      "url": "https://ca-arbiter-concierge-dev.thankfulpond-c4b3beed.eastus2.azurecontainerapps.io/mcp"
    }
  }
}

Local stdio

cd arbiter/concierge-mcp && npm run build
npx tsx src/index.ts --stdio

Test

1. Health

curl -sS https://ca-arbiter-concierge-dev.thankfulpond-c4b3beed.eastus2.azurecontainerapps.io/health

Expect {"status":"ok","product":"arbiter",...}.

2. MCP initialize

curl -sS -X POST \
  https://ca-arbiter-concierge-dev.thankfulpond-c4b3beed.eastus2.azurecontainerapps.io/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"smoke","version":"0.0.1"}}}'

Expect serverInfo.name = arbiter-concierge.

3. In Cursor

Click Add to Cursor above → approve install → ask: “What REST endpoints map controls and frameworks?”

CLI

npx @blockskunk/cli chat --product arbiter
npx @blockskunk/cli ask "How does evidence hashing work?" --product arbiter

Authenticated MCP

Integration Surfaces

Book a briefing