Incode IDV

You can run an MCP server that brings Incode’s identity verification directly into your AI workflows. This server enables you to create verification sessions, monitor progress, retrieve results and scores, obtain short-lived tokens, and validate tokens, all through simple commands from your MCP client.

How to use

You will interact with the MCP server through an MCP client integrated in your AI environment. Use the available tools to generate a verification session, monitor its status, fetch the verification score, obtain a temporary JWT token after a successful interview, and validate tokens when needed. Follow the quick start steps to configure your client, then invoke the tools in natural language prompts or through your MC P client calls.

How to install

Prerequisites: you need Node.js installed on your system to run the MCP client commands. You may also use the MCP command runner provided in the setup. Install the MCP client as described in the quick start configuration.

# Step 1: Install the MCP client package (example using npx as shown in the configuration)

Additional setup and usage notes

Configure the MCP client with your API key to enable identity verification functionality. The following configuration snippet shows the required settings, including the command to run the MCP server and the environment variable for authentication.

{
  "mcpServers": {
    "incode_idv": {
      "command": "npx",
      "args": ["-y", "@incodetech/incode-idv-mcp"],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Configuration and security notes

• Keep your API key secure and do not share it publicly. Use environment isolation where possible. - Ensure the MCP server is enabled in your client settings after you add the configuration. - Tokens have a short TTL and should be refreshed as needed. - Validate tokens before relying on them for authentication or session verification.

Troubleshooting

If you run into issues, verify that your API key is correctly set in the configuration and that the MCP server command is accessible. Check that the client configuration is properly loaded after you restart the application. If a token expires, generate a new one before continuing.

Common issues include tools not working due to an invalid API key, path errors from misconfigured project directories, server startup problems from syntax issues in the client config, or token expiration requiring a new token.

Available tools

generate_interview_link

Create a new verification session and return an interview ID and URL for the user to complete verification.

get_interview_status

Check the current status of an identity verification session using the interviewId and receive progress details.

get_interview_score

Retrieve the verification results and scores for a completed session identified by interviewId.

get_interview_token

Obtain a JWT access token for a successfully completed interview, with a 15-minute TTL.

validate_token

Validate a JWT token and return the claims if the token is valid.