Skip to content
CribScore
Skip to content
CribScore Docs

MCP

Remote MCP (hosted)

Hosted MCP endpoint with the same tool surface as the local package — one config block, no install state.

Endpoint#

One URL, one header. The endpoint speaks the streamable-HTTP MCP transport, which most modern agent clients support natively.

  • URL: https://api.cribscore.co/mcp
  • Auth: `Authorization: Bearer YOUR_API_KEY`
  • Transport: streamable HTTP (MCP spec)
{
  "cribscore": {
    "type": "streamable-http",
    "url": "https://api.cribscore.co/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_API_KEY"
    }
  }
}

When to choose remote#

Remote is the right default for evaluation, prototype agents, and most production deploys. You get the same tool surface as the local package without managing transport state, version pinning, or process lifetimes.

  • Zero install — works from any host with HTTP egress.
  • Always current — no version drift between you and the published tools.
  • Scales with CribScore — no per-host throughput ceiling.

When to choose local#

If your agent platform does not yet support remote MCP, or you need deterministic version pinning / offline operation, install the npm package locally (see /docs/mcp/local).

Authentication#

Same bearer key as the REST API and webhooks. Rotate the key in your dashboard; clients pick up the new value on next launch.

Related#