Skip to content
Connect an agent

Connections

Check whether a sign-in link can still be answered

open for a link that can be approved or denied, used for one already answered by any account, expired for one past its ten minutes, invalid for one the MCP server did not sign.

GET/user/mcp/request

TL;DR

QuestionAnswer
What does it do?Check whether a sign-in link can still be answered.
What does it take?request in the query string.
What does it return?Status 200 with a body of type McpRequestState.
What can go wrong?400 no request was sent; 401 not signed in; 429 too many requests; 503 connecting an agent is not set up on this server. Every failure uses the one error envelope.

What it does

open for a link that can be approved or denied, used for one already answered by any account, expired for one past its ten minutes, invalid for one the MCP server did not sign. The approval checks again.

Query parameters

FieldTypeRequiredDescription
requeststringyesThe signed request the consent page was opened with, exactly as received.

Responses

StatusMeaningBody
200What the link is now.McpRequestState
400No request was sent.ErrorResponse
401Not signed in.ErrorResponse
429Too many requests.ErrorResponse
503Connecting an agent is not set up on this server.ErrorResponse

Response body

A 200 answer has the type McpRequestState.

FieldTypeRequiredDescription
state"open" | "used" | "expired" | "invalid"yesopen: it can be approved or denied. used: it was approved or denied already, by any account; each sign-in link works once. expired: its ten minutes are over. invalid: the MCP server did not sign it.
expiresIninteger | nullyesFor open, the seconds until it stops being good. Null otherwise.

See also

DocWhy
API referenceEvery endpoint, and the error envelope
SchemasEvery request and response type
Tool referenceThe operations as callable tools