Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
JUMIO_API_TOKEN, JUMIO_API_SECRET, JUMIO_USER_AGENT, JUMIO_REGIONValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"jumio": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-jumio"
],
"env": {
"JUMIO_API_TOKEN": "your-value",
"JUMIO_API_SECRET": "your-value",
"JUMIO_USER_AGENT": "your-value",
"JUMIO_REGION": "your-value"
}
}
}
}Run this in your terminal
claude mcp add jumio --env JUMIO_API_TOKEN=your-value --env JUMIO_API_SECRET=your-value --env JUMIO_USER_AGENT=your-value --env JUMIO_REGION=your-value -- npx -y @codespar/mcp-jumioFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jumio": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-jumio"
],
"env": {
"JUMIO_API_TOKEN": "your-value",
"JUMIO_API_SECRET": "your-value",
"JUMIO_USER_AGENT": "your-value",
"JUMIO_REGION": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"jumio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-jumio"
],
"env": {
"JUMIO_API_TOKEN": "your-value",
"JUMIO_API_SECRET": "your-value",
"JUMIO_USER_AGENT": "your-value",
"JUMIO_REGION": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
JUMIO_REGION envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account codespar, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: JUMIO_API_TOKEN, JUMIO_API_SECRET, JUMIO_USER_AGENT
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Draugr
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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:
| Server | Strength |
|---|---|
| Unico | BR leader — local KYC, PEP, court records, Receita Federal biometric pool |
| Onfido | Global challenger — clean developer API, 195+ countries, strong SDK story |
| Jumio (this) | Global enterprise — deeper fraud-pattern detection, longer operator history, bank-grade |
Pair with Unico for Brazil-resident users (CPF + Receita biometric match); use Jumio for the rest of the world.
| Tool | Purpose | |||
|---|---|---|---|---|
initiate_account | Create a persistent Jumio end-user account. | |||
initiate_transaction | Start a new KYC workflow execution on an existing account. | |||
get_transaction | Retrieve a workflow execution summary — status ('INITIATED' \ | 'PROCESSED' \ | 'SESSION_EXPIRED' \ | 'TOKEN_EXPI... |
list_transactions | List workflow executions for an account. | |||
get_transaction_details | Retrieve the full result payload for a workflow execution — all capability outputs (extraction, liveness, s... | |||
retrieve_document_data | Retrieve extracted fields from the ID document (name, DOB, document number, expiry, issuing country, MRZ, e... | |||
retrieve_similarity_score | Retrieve the facial similarity result (selfie vs document photo). | |||
delete_transaction | Delete a workflow execution (GDPR right-to-erasure). | |||
update_transaction_status | Update the merchant-side status of a workflow execution (PATCH). | |||
retrieve_credentials | List the credentials (captured artefacts: ID front/back, selfie, proof-of-address, etc) for a workflow exec... | |||
cancel_transaction | Cancel an in-flight workflow execution (status 'INITIATED' or 'ACQUIRED'). | |||
retry_transaction | Retry a failed, expired, or rejected workflow execution. | |||
retrieve_extraction_data | Retrieve raw OCR / extraction capability output for a completed workflow — every extracted field with its s... | |||
retrieve_liveness_result | Retrieve the liveness capability result — passive/active liveness decision plus per-frame anti-spoofing sco... | |||
retrieve_facemap | Retrieve the biometric facemap (face template) generated during a workflow. | |||
retrieve_screening_result | Retrieve AML / watchlist screening output for a workflow — sanctions hits, PEP hits, adverse-media hits wit... | |||
retrieve_data_export | Retrieve a full GDPR-compliant data export for an account — every workflow execution, captured image URL, e... | |||
register_callback_url | Set or update the account-level webhook (callback) URL where Jumio POSTs workflow result notifications. | |||
delete_account | Delete a Jumio end-user account and every workflow execution under it (GDPR right-to-erasure). | |||
list_accounts | List Jumio end-user accounts under your authorizer / merchant. |
initiate_account (once per end-user)
-> initiate_transaction returns redirectUrl -> user completes capture at redirectUrl -> get_transaction poll until status = PROCESSED -> get_transaction_details full decision payload -> retrieve_document_data extracted ID fields -> retrieve_similarity_score face-match result -> update_transaction_status ("APPROVED" / "REJECTED" — feedback loop)
npm install @codespar/mcp-jumio
JUMIO_API_TOKEN="..." # API token (required)
JUMIO_API_SECRET="..." # API secret (required, secret) JUMIO_USER_AGENT="AcmeCorp KYX/1.0" # required by Jumio — identifies the caller JUMIO_REGION="us" # 'us' | 'eu' | 'sg'. Default 'us'.
HTTP Basic, with API token as user and API secret as password:
Authorization: Basic base64(JUMIO_API_TOKEN:JUMIO_API_SECRET)
User-Agent:
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.
| Region | Host |
|---|---|
| US (default) | https://api.amer-1.jumio.ai |
| EU | https://api.emea-1.jumio.ai |
| SG / APAC | https://api.apac-1.jumio.ai |
All endpoints live under /api/v1.
# stdio (default — for Claude Desktop, Cursor, etc)
npx @codespar/mcp-jumio
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-jumio
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.
MIT