Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
JUMIO_API_TOKEN, JUMIO_API_SECRET, JUMIO_USER_AGENT, JUMIO_REGION标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
}
}
}
}在终端中运行这条命令
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-jumio运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
JUMIO_REGION env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 codespar 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:JUMIO_API_TOKEN, JUMIO_API_SECRET, JUMIO_USER_AGENT
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.2.2)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SuperCollider
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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