Mcp Jumio

io.github.codespar由 GitHub 账号 codespar 发布v0.2.2更新于 Oct 24, 2026

MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening

已验证STDIO仅桌面安全与监控商业与电商

概览

AI 生成的概览

Jumio 身份验证 MCP 服务器：创建终端用户账户、发起 KYC 流程，并获取证件、活体检测、人脸比对与 AML 筛查结果。

可以做什么
  • 创建、列出和删除 Jumio 终端用户账户，并注册账户级回调地址
  • 发起、列出、取消、重试和删除 KYC 流程执行，并更新商户侧状态
  • 读取流程摘要与完整结果数据，包括原始 OCR 提取结果
  • 获取采集的凭证材料、证件字段、人脸相似度、活体检测结果与生物特征 facemap
  • 获取 AML 与监控名单筛查结果，以及账户的完整 GDPR 数据导出
适用场景
适用于受监管的开户与 KYC/KYX 流程，让助手驱动 Jumio 核验：发起验证会话、轮询结果、读取证件提取字段与筛查命中，并处理数据删除请求。适合银行、金融科技公司及高价值开户场景，尤其是已在或计划使用 Jumio 的机构。
运行要求
通过 npm 包以 stdio 在本地运行（npx @codespar/mcp-jumio），需要 Node.js。需要 Jumio API token 与 API secret（HTTP Basic 认证）、商户 User-Agent 字符串，可选区域（us、eu 或 sg，默认 us）。需要能访问 Jumio 各区域 API 主机的网络。
安装前请注意
需要 Jumio API token 与 secret，可访问身份核验数据，请勿放入共享配置。涉及敏感个人数据：证件、自拍、生物特征 facemap 及 AML/PEP 筛查结果。多个工具会写入或销毁数据，包括删除账户与流程（GDPR 删除权）、取消或重试流程、修改状态。验证会话可能产生 Jumio 计费。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Jumio，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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:

ServerStrength
UnicoBR leader — local KYC, PEP, court records, Receita Federal biometric pool
OnfidoGlobal challenger — clean developer API, 195+ countries, strong SDK story
Jumio (this)Global enterprise — deeper fraud-pattern detection, longer operator history, bank-grade

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)

ToolPurpose
initiate_accountCreate a persistent Jumio end-user account.
initiate_transactionStart a new KYC workflow execution on an existing account.
get_transactionRetrieve a workflow execution summary — status ('INITIATED' | 'PROCESSED' | 'SESSION_EXPIRED' | 'TOKEN_EXPI...
list_transactionsList workflow executions for an account.
get_transaction_detailsRetrieve the full result payload for a workflow execution — all capability outputs (extraction, liveness, s...
retrieve_document_dataRetrieve extracted fields from the ID document (name, DOB, document number, expiry, issuing country, MRZ, e...
retrieve_similarity_scoreRetrieve the facial similarity result (selfie vs document photo).
delete_transactionDelete a workflow execution (GDPR right-to-erasure).
update_transaction_statusUpdate the merchant-side status of a workflow execution (PATCH).
retrieve_credentialsList the credentials (captured artefacts: ID front/back, selfie, proof-of-address, etc) for a workflow exec...
cancel_transactionCancel an in-flight workflow execution (status 'INITIATED' or 'ACQUIRED').
retry_transactionRetry a failed, expired, or rejected workflow execution.
retrieve_extraction_dataRetrieve raw OCR / extraction capability output for a completed workflow — every extracted field with its s...
retrieve_liveness_resultRetrieve the liveness capability result — passive/active liveness decision plus per-frame anti-spoofing sco...
retrieve_facemapRetrieve the biometric facemap (face template) generated during a workflow.
retrieve_screening_resultRetrieve AML / watchlist screening output for a workflow — sanctions hits, PEP hits, adverse-media hits wit...
retrieve_data_exportRetrieve a full GDPR-compliant data export for an account — every workflow execution, captured image URL, e...
register_callback_urlSet or update the account-level webhook (callback) URL where Jumio POSTs workflow result notifications.
delete_accountDelete a Jumio end-user account and every workflow execution under it (GDPR right-to-erasure).
list_accountsList Jumio end-user accounts under your authorizer / merchant.

Flow

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)

Install

bash
npm install @codespar/mcp-jumio

Environment

bash
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 callerJUMIO_REGION="us"           # 'us' | 'eu' | 'sg'. Default 'us'.

Authentication

HTTP Basic, with API token as user and API secret as password:

Authorization: Basic base64(JUMIO_API_TOKEN:JUMIO_API_SECRET)User-Agent:    <JUMIO_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.

Regional hosts

RegionHost
US (default)https://api.amer-1.jumio.ai
EUhttps://api.emea-1.jumio.ai
SG / APAChttps://api.apac-1.jumio.ai

All endpoints live under /api/v1.

Run

bash
# stdio (default — for Claude Desktop, Cursor, etc)npx @codespar/mcp-jumio
# HTTP (for server-to-server testing)MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-jumio

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

来源：packages/identity/jumio/README.md，提交 d0a519a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.2.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分