Incode Idv Mcp
Expose Incode identity verification flows to your agent while you integrate KYC or onboarding into a fintech or regulated SaaS.
Overview
Incode IDV MCP is a Ship-phase MCP server that exposes Incode identity verification tools to AI assistants over stdio with an API key.
What is this MCP server?
- stdio MCP package @incodetech/incode-idv-mcp on npm (version 1.0.5)
- Identity verification tools tailored for AI assistant workflows
- Requires API_KEY environment variable for Incode service access
- GitHub source at IncodeTechnologies/incode-idv-mcp
- npm registry install path for local MCP process
- npm package version 1.0.5
- Transport: stdio
- Required secret: API_KEY environment variable
What problem does it solve?
Integrating real IDV providers into an agent-assisted codebase is slow when verification APIs live outside your editor context.
Who is it for?
Solo builders adding Incode-powered KYC or identity checks to SaaS or mobile backends before launch.
Skip if: Apps with no identity compliance needs, or teams not using Incode as their IDV vendor.
What do I get? / Deliverables
After install and API_KEY setup, your agent can invoke Incode IDV MCP tools while you build and harden onboarding flows.
- Local stdio MCP server exposing Incode IDV tools
- Agent-assisted IDV integration and test calls against Incode
- Documented API_KEY setup for team MCP configs
Recommended MCP Servers
Journey fit
How it compares
Vendor IDV MCP bridge, not a generic OAuth skill or self-hosted document OCR pipeline.
Common Questions / FAQ
Who is Incode IDV MCP for?
Developers using Incode for identity verification who want MCP tools available to Claude Code, Cursor, or similar agents.
When should I use Incode IDV MCP?
Use it during ship security work when implementing or testing Incode IDV in your onboarding or compliance flows.
How do I add Incode IDV MCP to my agent?
Install @incodetech/incode-idv-mcp from npm, configure stdio transport, and set the API_KEY environment variable to your Incode API key.