idnow-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_flowsA | List the identity-verification flows available to this IDnow account. Returns each flow's id, name, and description. Call this first to discover a flowId before creating or listing sessions. |
| create_sessionA | Create a new identity-verification session for a given flow. Requires the flowId (from list_flows) and a subjectId (your internal reference for the person being verified - never a real name or other PII). Returns the sessionId and a playerUrl and the initial sessionStatus, which is the link the end-user opens to complete verification. Session starts in CREATED and moves to RUNNING once the user begins. |
| list_sessionsA | List verification sessions for a flow, newest first. If flowId is omitted, the account's first available flow is used automatically. Returns each session's sessionId, sessionStatus (CREATED/RUNNING/COMPLETED/EXPIRED/ABORTED/ERROR), outcome, and createdAt. Use this to find the sessionId of a session you just created, then pass it to get_session for full detail. |
| get_sessionA | Retrieve full detail and current status for ONE verification session by its sessionId. Use this after create_session (or after finding a sessionId via list_sessions) to check the progress or outcome of a specific session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct resource and action: listing flows, listing sessions, creating a session, and retrieving a single session. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern (list_flows, list_sessions, create_session, get_session) with no mixed conventions or deviations.
Four tools is well-scoped for an identity verification server, covering discovery, creation, and status retrieval without unnecessary bloat.
The core workflow is fully covered: discover flows, create sessions, list and retrieve session details. However, an explicit cancel or abort session operation is missing, which might be a minor gap given the session statuses include ABORTED.