Onfido MCP by usefulapi
REMOTE · ONFIDO.USEFULAPI.IO
Create and read Onfido applicants, documents, checks and reports.
Available components
Last scanned (13 minutes ago)
Scores higher than 68% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1418 tokens (~101/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
- 23 Oct 26 0
- Server version: 1.16.4 → 1.17.0 functional
- 22 Oct 26 +1
- Server version: 1.16.3 → 1.16.4 functional
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.14.0 → 1.16.3 functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: unverified → 100 ▲ functional
- The server now declares the “prompts” capability functional
- New prompt “getting_started” functional
- Server version: 1.13.0 → 1.14.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://onfido.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of onfido.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://onfido.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://onfido.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://onfido.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://onfido.usefulapi.io/mcp |
| Authorisation server | https://onfido.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://onfido.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/onfido/ |
| http (plaintext) | http://onfido.usefulapi.io/mcp | Inconclusive | 302 | http://onfido.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
onfido_create_applicant Create applicant ~200
Creates an applicant (person) record in Onfido. Onfido API: POST /applicants. Creates a PII record only — runs NO verification check and costs nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | Address object (building_number, street, town, postcode, country, …). Passed through as-is. |
| dob | string | – | Date of birth, yyyy-mm-dd. |
| string | – | Applicant email address. | |
| first_name | string | yes | Applicant's first name (required). |
| id_numbers | array | – | Array of id-number objects ({ type, value, state_code? }). Passed through as-is. |
| last_name | string | yes | Applicant's last name (required). |
| location | object | – | Location object (ip_address, country_of_residence, …) for consent tracking. Passed through as-is. |
| phone_number | string | – | Phone number in E.164 or local format. |
No output schema declared.
No examples provided.
onfido_get_applicant Get applicant ~46
Retrieve a single applicant record by id. Onfido API: GET /applicants/{applicant_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | The applicant id. |
No output schema declared.
No examples provided.
onfido_get_check Get check ~49
Retrieve a single check (status + report ids + result) by id. Onfido API: GET /checks/{check_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check id. |
No output schema declared.
No examples provided.
onfido_get_document Get document ~43
Retrieve a single document's metadata by id. Onfido API: GET /documents/{document_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document id. |
No output schema declared.
No examples provided.
onfido_get_report Get report ~48
Retrieve a single report (detailed breakdown + result) by id. Onfido API: GET /reports/{report_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | The report id. |
No output schema declared.
No examples provided.
onfido_get_workflow_run Get workflow run ~57
Retrieve a single Studio workflow run (status, output, task history) by id. Onfido API: GET /workflow_runs/{workflow_run_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_run_id | string | yes | The workflow run id. |
No output schema declared.
No examples provided.
onfido_list_applicants List applicants ~91
List applicant (person) records in the Onfido account, paginated. Onfido API: GET /applicants.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Include applicants scheduled for deletion. Default false. |
| page | integer | – | Page number (1-based). Default 1. |
| per_page | integer | – | Results per page (max 500). Default 20. |
No output schema declared.
No examples provided.
onfido_list_checks List checks ~57
List the verification checks run for an applicant (results/status, read-only). Onfido API: GET /checks?applicant_id=….
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | The applicant id whose checks to list (required). |
No output schema declared.
No examples provided.
onfido_list_documents List documents ~54
List the identity documents uploaded for an applicant (metadata only). Onfido API: GET /documents?applicant_id=….
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | The applicant id whose documents to list (required). |
No output schema declared.
No examples provided.
onfido_list_live_photos List live photos ~59
List the live photos captured for an applicant (metadata only). Onfido API: GET /live_photos?applicant_id=….
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | The applicant id whose live photos to list (required). |
No output schema declared.
No examples provided.
onfido_list_live_videos List live videos ~59
List the live videos captured for an applicant (metadata only). Onfido API: GET /live_videos?applicant_id=….
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | The applicant id whose live videos to list (required). |
No output schema declared.
No examples provided.
onfido_list_reports List reports ~61
List the individual reports that make up a check (document, facial similarity, watchlist, …). Onfido API: GET /reports?check_id=….
| Name | Type | Req | Description |
|---|---|---|---|
| check_id | string | yes | The check id whose reports to list (required). |
No output schema declared.
No examples provided.
onfido_list_workflow_runs List workflow runs ~153
List Onfido Studio workflow runs (status/output, read-only — does NOT start a run). Onfido API: GET /workflow_runs.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | – | Filter to a single applicant's workflow runs. |
| created_at_gt | string | – | Only runs created after this ISO-8601 timestamp. |
| created_at_lt | string | – | Only runs created before this ISO-8601 timestamp. |
| page | integer | – | Page number (1-based). Default 1. |
| sort | string | – | Sort by creation time. Default desc. |
| status | string | – | Filter by status, e.g. processing | awaiting_input | approved | declined | abandoned | error. |
No output schema declared.
No examples provided.
onfido_update_applicant Update applicant ~171
Updates an applicant's details (reversible; runs no verification). Onfido API: PUT /applicants/{applicant_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | Address object (building_number, street, town, postcode, country, …). Passed through as-is. |
| applicant_id | string | yes | The applicant id to update (required). |
| dob | string | – | Date of birth, yyyy-mm-dd. |
| string | – | Applicant email address. | |
| first_name | string | – | Updated first name. |
| id_numbers | array | – | Array of id-number objects ({ type, value, state_code? }). Passed through as-is. |
| last_name | string | – | Updated last name. |
| phone_number | string | – | Phone number in E.164 or local format. |
No output schema declared.
No examples provided.
How do I install the Onfido MCP by usefulapi server?
Onfido MCP by usefulapi is a hosted endpoint at https://onfido.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · onfido.usefulapi.io
claude mcp add --transport http io-usefulapi-onfido 'https://onfido.usefulapi.io/mcp'
What is the Onfido MCP by usefulapi server?
Onfido MCP by usefulapi is listed in the public MCP registry as io.usefulapi/onfido. Create and read Onfido applicants, documents, checks and reports. This page covers its hosted endpoint (https://onfido.usefulapi.io/mcp).
Is the Onfido MCP by usefulapi server safe to use?
Onfido MCP by usefulapi scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Onfido MCP by usefulapi server expose?
Onfido MCP by usefulapi exposes 14 tools: onfido_list_applicants, onfido_get_applicant, onfido_list_documents, onfido_get_document, onfido_list_checks, and 9 more. Their descriptions and schemas cost roughly 1,148 tokens of context every time the server is loaded.
Does the Onfido MCP by usefulapi server require authentication?
Yes. Onfido MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Onfido MCP by usefulapi server still maintained?
Onfido MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.