
Mcp Jumio
io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026
MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening
Overview
MCP server for Jumio identity verification: create end-user accounts, run KYC workflows, and pull document, liveness, face-match and AML results.
- What you can do
- Create, list and delete Jumio end-user accounts, and register an account-level callback URL
- Start, list, cancel, retry and delete KYC workflow executions, and update their merchant-side status
- Read transaction summaries and full result payloads, including raw OCR extraction data
- Retrieve captured credentials, document fields, facial similarity scores, liveness results and biometric facemaps
- Retrieve AML and watchlist screening output, and full GDPR data exports for an account
- When to use it
- For regulated onboarding and KYC/KYX flows where an assistant should drive Jumio checks: starting verification sessions, polling results, reading extracted ID data and screening hits, and handling erasure requests. Suited to banks, fintechs and high-value onboarding already using or evaluating Jumio.
- Requirements
- Runs locally over stdio via the npm package (npx @codespar/mcp-jumio), so Node.js is needed. Requires a Jumio API token and API secret (HTTP Basic auth), a merchant User-Agent string, and optionally a region (us, eu or sg; default us). Network access to the Jumio regional API host is required.
Installation
In SourceWeft
- Open Mcp Jumio 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
@codespar/mcp-jumio
MCP server for Jumio — global enterprise identity verification (KYX / Netverify).
Jumio is the identity layer banks and large regulated fintechs reach for when Onfido isn't deep enough on fraud-pattern detection. Longer operator history, richer risk intelligence, purpose-built for regulated commerce at scale.
Third entry in CodeSpar's identity category. Completes the tier:
When to pick Jumio
- Regulated bank or tier-1 fintech where auditors expect a legacy-credible vendor
- High-value onboarding where fraud-loss >> verification cost
- Deep fraud intelligence matters (velocity checks, device/session signals, longitudinal identity graph)
- You already run Jumio elsewhere in the org and want a single KYC stack
Pair with Unico for Brazil-resident users (CPF + Receita biometric match); use Jumio for the rest of the world.
Tools (20)
Flow
Install
Environment
Authentication
HTTP Basic, with API token as user and API secret as password:
Jumio rejects requests without a custom User-Agent header — use something that identifies your merchant + integration (e.g. "AcmeCorp KYX/1.0"). The server wires both headers automatically.
Regional hosts
All endpoints live under /api/v1.
Run
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Source: packages/identity/jumio/README.md at commit d0a519a
Tools
0Version history
1- v0.2.2LatestSep 16, 2026
Score
50% 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
- License10 pts