MCP_UNVERIFIED_CLIENT

Unverified MCP client: what the MCP_UNVERIFIED_CLIENT error means and how to fix it.

HTTP 422. Problem type: https://docs.ovok.com/errors/mcp-unverified-client.

What this means

An admin allowed a connection request from an AI client whose answer goes to a host that is not a known MCP client or the admin's own computer. Ovok issued no code, because the admin has not confirmed that host.

Troubleshooting

  1. Read the host the console shows, in client.redirectHost. Check that it belongs to the AI client you started the connection from.
  2. If you recognise the host, allow again and confirm it. The console then sends confirmUnverified: true.
  3. If you do not recognise the host, deny the request with allow: false. The name a client gives itself is its own claim, and Ovok does not check it.

Retry safely

Resend the answer with confirmUnverified: true only after the admin accepted the host. The request stays valid for 10 minutes. Nothing was issued, so an unchanged resend returns the same error.

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 explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page