# MCP_REQUEST_INVALID

Canonical page: https://docs.ovok.com/errors/mcp-request-invalid

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/mcp-request-invalid`](https://docs.ovok.com/errors/mcp-request-invalid).

## What this means [#what-this-means]

The console asked Ovok about a connection request for an AI client, and the request is not one this Ovok environment issued, or it expired. Ovok refused it and connected nothing.

## Troubleshooting [#troubleshooting]

1. Start the connection again from the AI client. A request is valid for 10 minutes, so a consent page left open longer fails.
2. Open the consent page from the link the client opens for you. The request is signed, and a link that was edited, cut off or copied together with other text no longer verifies.
3. Check that the consent page talks to the environment that issued the request. Another environment cannot read it.

## Retry safely [#retry-safely]

Do not resubmit the same request. Start a new connection from the client. Nothing was connected, so there is nothing to clean up.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
