MCP server

A remote MCP server mounted on the same harness base URL. The server is a thin protocol adapter over the existing authenticated routes; it adds no new billing, auth, or compute path. Every tool below resolves to one call to an existing endpoint, settled exactly once.

Endpoint

text

POST https://harness.example.com/mcp

Auth

The primary scheme is Authorization: Bearer <VEDIKA_AGENT_KEY>. Hosts that require OAuth use the standard 2.1 flow with audience binding to the /mcp endpoint.

A 401 from the server carries WWW-Authenticate: Bearer resource_metadata=... with a PRM document so hosts can complete discovery.

Protocol versions

The server advertises two protocol versions:

2026-07-28 (latest)
2025-11-25 (compatibility)

Tool catalog

Idempotency

The harness derives an idempotency key as a hash of (key id, tool name, canonical args, time bucket). An identical question re-asked inside the bucket replays the first answer without a second bill. Clients should not pass their own Idempotency-Key; the harness rejects keys that conflict with its derivation.

Limits

Tool count per request: 16 (the catalog is currently 15).
Origin header: required and validated against the allow-list.
Body limit: 4 MiB by default.
Global timeout: 180 s. Long-lived subscriptions are not supported in v1.

Discovery

Hosts that support tools/list receive a deterministic list with ttlMs of about one hour and cacheScope of public. Re-issue tools/list after the cache expires to pick up new tools.