CRUX distribution

Connect the underwriting system you can inspect.

Choose a client route, then verify discovery and execution separately. CRUX keeps credential scope, revocation, and unresolved hosted-client proof visible before setup.

Canonical MCP endpointhttps://crux-harness.vercel.app/api/mcp

91canonical skills

10outcome agents

15workflow entries

347sanitized tool contracts

Access comes first

Two credentials. Different authority.

Client configuration does not determine authorization. Select the credential profile deliberately and keep its removal path with the handoff.

connect_read_only

Connect read-only

crux_sk_ro_…

A signed-in user mints this database-backed key at /connect. Clerk and the application database must be available.

Scopes: read:engines · read:skills · read:deals · read:artifacts · read:receipts
Write boundary: No own-context or general deal write scope.
Revocation: The user can revoke an individual key from /connect; the database row is marked revoked.

347 visible344 list-visible339 policy-callable

This profile can read the caller’s authorized deal, artifact, and receipt records. It is not an anonymous public key.

partner_own_context

Partner read plus own-context write

crux_partner_…

A CRUX owner mints this stateless, expiring HMAC-signed token for a named partner.

Scopes: read:engines · read:skills · write:own_context
Write boundary: write:own_context permits create, enrich, and underwrite operations only inside that token’s isolated partner tenant.
Revocation: There is no individual-token revocation list. Stop access by waiting for expiry or rotating the shared signing secret, which invalidates every token signed with it.

347 visible344 list-visible342 policy-callable

This is not read-only. It does not grant write:deals, cross-tenant access, lab, task, export, or admin scopes.

Client routes

Select the host you already use.

Repository-verified means the checked-in package and configuration agree. It does not mean the package is published or that a hosted client has executed a CRUX tool.

Hosted remote server

Claude

Registration and live call proof required

The canonical HTTPS MCP endpoint is documented. Existing hosted-client evidence does not prove a current authenticated tools/call.

Authentication

Hosted Claude custom connectors support unauthenticated servers or OAuth. CRUX authenticated hosted use requires a proven OAuth/DCR flow; a static bearer handoff is not a supported setup route.

Access profile

Keep this route blocked until CRUX OAuth/DCR proves the intended read-only or isolated own-context authority end to end.

Setup

Open Claude’s connector settings and register a custom remote MCP server.
Enter the canonical endpoint only after the CRUX OAuth/DCR issuer and client registration are production-ready.
Do not paste a CRUX bearer token into chat, a URL, or an unsupported static-header field.

Success check

resources/list or tools/list proves discovery only.
Capture an authenticated tools/call receipt with the same endpoint and credential before claiming execution.

Removal, revocation, and limitation

Remove: Remove or disable the remote server in Claude, then revoke the OAuth grant or token at its issuer.

Current boundary: OAuth/DCR issuer, audience, authorization, token, refresh, and revocation flows still require an end-to-end hosted smoke.

Proof boundary

Static policy is the starting point.

Generated from committed product, workflow, MCP exposure, scope, and gate registries.

successful tools/call execution
hosted deployment parity
production authentication
artifact circulation or external-send approval

Contract projection: 2026-07-31. The legacy MCPB catalog contains 458 registered server tools; the sanitized buyer contract intentionally discloses 347.