MCP integration preview

Transport and current availability

The proposed endpoint is https://optinrouter.ai/mcp. All methods currently return HTTP 401, including supplied keys. The downloadable manifest is a design artifact, not a running MCP server. This compatibility profile pins MCP 2025-11-25 Streamable HTTP and its initialization lifecycle; it does not claim support for every newer protocol version or every client. Origin validation, version negotiation, tenant authentication and protocol conformance must pass certification before access opens.

json

{
  "url": "https://optinrouter.ai/mcp",
  "profile": "2025-11-25-compatibility-preview",
  "status": "access_closed"
}

Tools and authority

Agents may request only approved tools with narrow projections. Tool annotations are descriptive; authorization is enforced by the server using tenant identity, required scopes and active policy. The initial tool set provides route explanation, synthetic graph simulation, policy validation, trace metadata aggregate usage, buyer offer eligibility and provider certification requirements. It excludes shell execution, arbitrary network requests, purchases, messages, policy activation and data delivery.

Tool	Scope	Input / output
routes_explain	routing:read	Pinned policy + candidate IDs → eligibility/reasons
actions_simulate	actions:simulate	Pinned graph + named synthetic fixture → event metadata
policies_validate	policies:validate	Policy document → validation issues
traces_get	traces:read	Trace ID → authorized metadata
usage_list	usage:read	Bounded filters → aggregate usage
buyer_offer_preview	marketplace:read	Dataset + purpose + region → consent/license eligibility; no purchase
provider_certification_preview	provider:validate	Endpoint + profile → capability checks; no registration

Context and action isolation

A request or model response is untrusted data. It cannot register tools, grant scopes, change location policy, expand a projection or authorize effects. The action graph pins tool revisions, dependencies, phases, output slots, concurrency and branch deadlines. Required unknown or failed controls block release. Synthetic action simulation performs no provider inference and no external side effects; production execution is a separate gateway operation with its own usage accounting.

Errors, cancellation and evidence

The future authenticated MCP layer must map policy denial, unsupported grammar, stale revision, missing regional evidence, scope denial and cancellation into structured bounded results. The compatibility transport uses JSON-RPC, version headers and explicit cancellation notifications. Closing a connection alone does not establish cancellation. Logs and resources exclude raw content by default. Conformance cases cover cross-tenant IDs, prompt-injection attempts, output-slot conflicts, cancellation after dispatch and absent evidence.

json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "routes_explain",
    "arguments": {
      "policy_ref": "pol_engineering@3",
      "candidate_ids": [
        "eu-fra"
      ]
    }
  }
}