Jumio MCP server

Read from the package source without running it. The installed server may list more.

• cancel_transactionwrite action

  Cancel an in-flight workflow execution (status 'INITIATED' or 'ACQUIRED'). Use when the user abandons the flow or you decide upstream not to proceed; finalises the workflow as cancelled and stops further processing.

• delete_accountwrite action

  Delete a Jumio end-user account and every workflow execution under it (GDPR right-to-erasure). Irreversible. For deleting only a single transaction, use delete_transaction instead.

• delete_transactionwrite action

  Delete a workflow execution (GDPR right-to-erasure). Removes captured images, extracted data, and decision audit trail for this transaction on Jumio's side.

• get_transaction

  Retrieve a workflow execution summary — status ('INITIATED' | 'PROCESSED' | 'SESSION_EXPIRED' | 'TOKEN_EXPIRED' | 'ACQUIRED'), decision outcome, and capability-level results. Poll this to track progress.

• get_transaction_details

  Retrieve the full result payload for a workflow execution — all capability outputs (extraction, liveness, similarity, watchlist, etc). Use after status = 'PROCESSED'.

• initiate_accountwrite action

  Create a persistent Jumio end-user account. An account groups all workflow executions (KYC transactions) for the same real-world user, enabling re-use of previously verified data and longitudinal fraud signals.

• initiate_transaction

  Start a new KYC workflow execution on an existing account. Returns a `redirectUrl` — redirect the end user there to complete the Jumio-hosted capture flow (document + selfie). Poll get_transaction for status afterwards.

• list_accounts

  List Jumio end-user accounts under your authorizer / merchant. Supports pagination + filtering by customerInternalReference. Useful for admin dashboards and back-office reconciliation.

• list_transactions

  List workflow executions for an account. Useful for auditing or rebuilding state after a webhook failure.

• register_callback_url

  Set or update the account-level webhook (callback) URL where Jumio POSTs workflow result notifications. Per-transaction callbackUrl overrides this. Validate signatures using the shared HMAC secret configured in the Jumio portal.

• retrieve_credentials

  List the credentials (captured artefacts: ID front/back, selfie, proof-of-address, etc) for a workflow execution. Each credential carries a parts[] array with URLs to download the stored images / PDFs.

• retrieve_data_export

  Retrieve a full GDPR-compliant data export for an account — every workflow execution, captured image URL, extracted field, decision, and audit log. Use to fulfil a Subject Access Request.

• retrieve_document_data

  Retrieve extracted fields from the ID document (name, DOB, document number, expiry, issuing country, MRZ, etc). Requires a completed workflow that included a document capability.

• retrieve_extraction_data

  Retrieve raw OCR / extraction capability output for a completed workflow — every extracted field with its source coordinates, MRZ raw lines, barcode contents, and confidence per field. Lower-level than retrieve_document_data.

• retrieve_facemap

  Retrieve the biometric facemap (face template) generated during a workflow. Used for downstream face-search / re-verification flows; subject to biometric-data retention rules — handle accordingly.

• retrieve_liveness_result

  Retrieve the liveness capability result — passive/active liveness decision plus per-frame anti-spoofing scores. Requires a workflow that included a liveness capability (selfie or video).

• retrieve_screening_result

  Retrieve AML / watchlist screening output for a workflow — sanctions hits, PEP hits, adverse-media hits with source citations and match confidence. Requires a workflow that included a screening capability.

• retrieve_similarity_score

  Retrieve the facial similarity result (selfie vs document photo). Returns match decision plus confidence score. Requires a completed workflow that included a similarity/selfie capability.

• retry_transaction

  Retry a failed, expired, or rejected workflow execution. Creates a new workflow execution on the same account, optionally re-using the original workflow definition and customer references.

• update_transaction_statuswrite action

  Update the merchant-side status of a workflow execution (PATCH). Use to record your final accept/reject decision back on the Jumio transaction — helpful for Jumio's fraud model feedback loop and for dashboard reporting.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

20

the typical server has 7

Tools that change things

25%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 28,688 servers

Jumio: common questions

Is Jumio MCP server safe?

Mostly: it is graded B (82/100). Read the Jumio safety report

How do I install Jumio?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Jumio need an API key?

Yes. The registry entry asks for JUMIO_API_SECRET.

Is Jumio maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.

How does Jumio compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 20 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.