MCP Status, Support, and Deprecation
Support bundle
Provide the request ID, UTC timestamp, endpoint form, workspace UID or slug, client name and version, negotiated protocol version, method, and safe error code. Never include bearer credentials, connector credentials, unrestricted tool payloads, or private resource bodies.
Status
Repeated transport or 5xx failures may indicate unavailable schema, policy, or runtime dependencies. Use bounded retries for transient failures and avoid reconnect loops that amplify an incident.
Deprecation
Notices identify the protocol version or alias, migration target, notice date, intended sunset, and support path. A deprecation must not silently change tool semantics or authorization.
The current /ai-gateway/mcp/{workspace}/ address is a compatibility alias for /mcp/{workspace}/. No removal date is approved. Batoi measures credential-free alias usage, and the alias must remain until an approved notice of at least 180 days has elapsed, the prior 30 days contain zero calls, named consumers are cleared, compatibility tests pass, rollback is rehearsed, and the owner approves removal.
Security revocation may be immediate. Revoked hosts, policies, and credentials fail even if a client retains cached capability metadata.