Incode IDV MCP Server

An MCP server implementation that integrates with the Incode IDV service, providing identity verification tools for AI assistants.

Tools

• generate_interview_link - Create a new identity verification session

  • Inputs: None (all values are configured on the backend)
  • Returns: Interview ID and verification URL

• get_interview_status - Check the current status of an identity verification session

  • Inputs:
    • interviewId (string): The interview ID returned from generate_interview_link
  • Returns: Current status and progress information

• get_interview_score - Retrieve verification results and score for a completed session

  • Inputs:
    • interviewId (string): The interview ID returned from generate_interview_link
  • Returns: Verification result, score, and detailed information

• get_interview_auth_code - Get authorization code with (5 min TTL on issuance) for successfully completed interviews.

  • Inputs:
    • interviewId (string): The interview ID returned from generate_interview_link
  • Returns: Authorization code for successful verifications

• exchange_code_for_token - Exchange authorization code for JWT access token (20 min TTL)

  • Inputs:
    • code (string): Authorization code from get_interview_auth_code
  • Returns: JWT access token and metadata

• validate_token - Validate JWT token and return claims

  • Inputs:
    • token (string): JWT token to validate
  • Returns: Validation result and token claims if valid

• get_user_token - Retrieve existing valid JWT token by email address. This can only be done for your own email.

  • Inputs:
    • email (string): User's email address
  • Returns: JWT access token if valid and not expired

Workflow

The typical identity verification workflow follows these steps:

1. Generate Interview Link → Get verification URL for user
2. Get Interview Status → Check if user completed verification
3. Get Interview Score → Get verification results and score
4. Get Authorization Code → Get Auth code for successful interview session.
5. Exchange Code for Token → Get JWT access token
6. Validate Token → Verify token validity when needed
7. Get User Token → Retrieve existing valid token by email for reusable identity.

Configuration

Getting an API Key 🔑

1. Visit https://mcp-playground.labs.incode.com/
2. Sign up for an account
3. After you verify your email get an API KEY.

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "incode-idv": {
      "command": "npx",
      "args": ["-y", "@incodetech/incode-idv-mcp"],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE" # Replace with your API-KEY
      }
    }
  }
}

Note: Replace the path with your actual project directory path.

Setting Claude Desktop Config 💻

1. Open Claude Desktop App
2. Open Settings
3. Go To Developer
4. Click Edit Config
5. Add the incode-idv config above appropriately with your API-KEY from signup. (see Getting an API Key section above)
6. Restart Claude Desktop for claude to load new update config.

Troubleshooting

If you encounter issues with the MCP server, here are some helpful resources:

MCP Debugging Tools 🔧

For advanced debugging and troubleshooting MCP server issues:

• Check your Claude Desktop Logs
• See MCP Debugging Guide

Common Issues

• Calls Not Working: Check that your API_KEY set correctly in configuration with valid value.
• Check Your Path: Ensure the value in project directory is correct. This should be an absolute path.
• Server not Starting: Ensure your json for your claude desktop config is valid.

Report Issues

• GitHub Issues: Report bugs and request features
• Email Support: support@incode.com for urgent issues
• Troubleshooting: See the troubleshooting section for common solutions

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License.