Incode Idv Mcp

io.github.IncodeTechnologiesPublished by GitHub account IncodeTechnologiesv1.0.5Updated Oct 24, 2026

MCP server for Incode IDV, providing identity verification tools for AI assistants.

VerifiedSTDIODesktop onlySecurity & Monitoring

Server details

Identifier: io.github.IncodeTechnologies/incode-idv-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account IncodeTechnologies for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.IncodeTechnologies%2Fincode-idv-mcp.svg)](https://sourceweft.com/mcp/io.github.IncodeTechnologies%2Fincode-idv-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that exposes Incode identity verification tools to AI assistants, authenticated with an Incode API key.

What you can do: Provides identity verification capabilities from Incode IDV to an assistant.
No tool list is published, so the exact operations available cannot be confirmed from the supplied material.
Runs as a local stdio process started on the user's machine.
When to use it: Consider it when you want an assistant to work with Incode identity verification from a desktop setup and you already have an Incode API key.
Requirements: Runs locally over stdio from the npm package @incodetech/incode-idv-mcp, so a Node.js runtime is needed. Requires an API_KEY environment variable holding an Incode API key. Desktop only; no web execution.

Before you install

The server needs an Incode API key in the API_KEY environment variable, so keep that secret out of shared configuration and logs. Identity verification typically involves personal identity data sent to Incode; the published material does not describe which data is transmitted or whether any actions are irreversible.

Installation

In SourceWeft

Open Incode Idv Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.