Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Persona MCP by usefulapi

REMOTE · PERSONA.USEFULAPI.IO

Read Persona inquiries, accounts, verifications and reports.

0 this week 18 Trust /100

Last scanned (21 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “check_the_verifications_behind_one_inquiry” functional
    • New prompt “find_inquiries_by_status_account_or_reference” functional
    • New prompt “list_open_cases_waiting_for_manual_review” functional
    • New prompt “review_screening_reports_and_transactions” functional
    • New prompt “tag_an_account_for_review” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 +1
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 +1
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
Diagnostics

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 21 Nov 2026 · Probed https://persona.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 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 93e2fea3bbc31354138c8a47c5e87592
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 persona.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://persona.usefulapi.io/mcp Redirected 302 https://usefulapi.io/persona/
http (plaintext) http://persona.usefulapi.io/mcp Inconclusive 302 http://persona.usefulapi.io/mcp
MCP tools · 14 exposed · ~1,749 tokens

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 →

Tool Tokens
persona_add_account_tag ~99

WRITE: adds a tag to an account (mutates state). Tags label/segment accounts for review and automation. Sends JSON body { meta: { "tag-name": <tag_name> } }. Persona REST: POST /accounts/{account_id}/add-tag.

NameTypeReqDescription
account_idstringyesThe account id to tag (e.g. act_...).
tag_namestringyesThe tag name to add to the account.

No output schema declared.

No examples provided.

persona_get_account ~64

Get a single account by id — the persistent identity record for an end user. Returns JSON:API { data } containing PII. Persona REST: GET /accounts/{account_id}.

NameTypeReqDescription
account_idstringyesThe account id (e.g. act_...).

No output schema declared.

No examples provided.

persona_get_case ~61

Get a single case by id — a manual-review workflow item. Returns JSON:API { data } containing PII. Persona REST: GET /cases/{case_id}.

NameTypeReqDescription
case_idstringyesThe case id (e.g. case_...).

No output schema declared.

No examples provided.

persona_get_event ~68

Get a single audit-trail event by id, including its name and payload. Returns JSON:API { data } — payloads may reference PII. Persona REST: GET /events/{event_id}.

NameTypeReqDescription
event_idstringyesThe event id (e.g. evt_...).

No output schema declared.

No examples provided.

persona_get_inquiry ~76

Get a single identity-verification inquiry by id, including its status, template, and relationships (verifications, account). Returns JSON:API { data } containing PII. Persona REST: GET /inquiries/{inquiry_id}.

NameTypeReqDescription
inquiry_idstringyesThe inquiry id (e.g. inq_...).

No output schema declared.

No examples provided.

persona_get_report ~74

Get a single report by id — a screening/monitoring result (e.g. watchlist, adverse-media, business lookup). Returns JSON:API { data } containing PII. Persona REST: GET /reports/{report_id}.

NameTypeReqDescription
report_idstringyesThe report id (e.g. report_...).

No output schema declared.

No examples provided.

persona_get_transaction ~66

Get a single transaction by id — a record submitted for transaction fraud/monitoring analysis. Returns JSON:API { data } containing PII. Persona REST: GET /transactions/{transaction_id}.

NameTypeReqDescription
transaction_idstringyesThe transaction id (e.g. txn_...).

No output schema declared.

No examples provided.

persona_get_verification ~79

Get a single verification by id — one identity check within an inquiry (e.g. government-id, selfie, database, document). Returns JSON:API { data } with check results and PII. Persona REST: GET /verifications/{verification_id}.

NameTypeReqDescription
verification_idstringyesThe verification id (e.g. ver_...).

No output schema declared.

No examples provided.

persona_list_accounts ~162

List accounts (a persistent identity record for an end user, linking their inquiries/verifications over time). Optionally filter by reference_id and paginate via the JSON:API links.next cursor (page_after) / links.prev (page_before). Returns JSON:API { data:[...], links } — objects contain PII. Persona REST: GET /accounts.

NameTypeReqDescription
page_afterstring–Pagination cursor: return the page AFTER this record id (follow the links.next cursor).
page_beforestring–Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor).
page_sizeinteger–Page size — number of records per page.
reference_idstring–Filter by your own reference-id set on the account.

No output schema declared.

No examples provided.

persona_list_cases ~253

List cases (manual-review workflow items grouping inquiries/reports for an analyst to adjudicate). Optionally filter by status, case_template_id, account_id, reference_id, inquiry_id, report_id, and paginate via the JSON:API links.next cursor (page_after) / links.prev (page_before). Returns JSON:API { data:[...], links } — objects contain PII. Persona REST: GET /cases.

NameTypeReqDescription
account_idstring–Filter by the associated account id.
case_template_idstring–Filter by the case template id.
inquiry_idstring–Filter by an associated inquiry id.
page_afterstring–Pagination cursor: return the page AFTER this record id (follow the links.next cursor).
page_beforestring–Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor).
page_sizeinteger–Page size — number of records per page.
reference_idstring–Filter by your own reference-id set on the case.
report_idstring–Filter by an associated report id.
statusstring–Filter by case status (e.g. open, resolved, waiting).

No output schema declared.

No examples provided.

persona_list_events ~145

List audit-trail events (an immutable log of actions across your Persona account — inquiry/account/case state changes, etc.). Paginate via the JSON:API links.next cursor (page_after) / links.prev (page_before). Returns JSON:API { data:[...], links } — payloads may reference PII. Persona REST: GET /events.

NameTypeReqDescription
page_afterstring–Pagination cursor: return the page AFTER this record id (follow the links.next cursor).
page_beforestring–Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor).
page_sizeinteger–Page size — number of records per page.

No output schema declared.

No examples provided.

persona_list_inquiries ~285

List identity-verification inquiries (an end-user's KYC verification session). Optionally filter by status, account_id, reference_id, inquiry_template_id, and a created-at date range, and paginate via the JSON:API links.next cursor (page_after) / links.prev (page_before). Returns JSON:API { data:[...], links } — objects contain PII. Persona REST: GET /inquiries.

NameTypeReqDescription
account_idstring–Filter by the associated account id.
created_at_endstring–Filter: inquiries created at/before this ISO 8601 timestamp.
created_at_startstring–Filter: inquiries created at/after this ISO 8601 timestamp.
inquiry_template_idstring–Filter by the inquiry template id (e.g. itmpl_...).
page_afterstring–Pagination cursor: return the page AFTER this record id (follow the links.next cursor).
page_beforestring–Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor).
page_sizeinteger–Page size — number of records per page.
reference_idstring–Filter by your own reference-id set on the inquiry.
statusstring–Filter by inquiry status (e.g. created, pending, completed, failed, expired, approved, declined).

No output schema declared.

No examples provided.

persona_list_reports ~141

List reports (screening/monitoring results such as watchlist, adverse-media, or business lookups). Paginate via the JSON:API links.next cursor (page_after) / links.prev (page_before). Returns JSON:API { data:[...], links } — objects may contain PII. Persona REST: GET /reports.

NameTypeReqDescription
page_afterstring–Pagination cursor: return the page AFTER this record id (follow the links.next cursor).
page_beforestring–Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor).
page_sizeinteger–Page size — number of records per page.

No output schema declared.

No examples provided.

persona_list_transactions ~176

List transactions (records submitted for transaction fraud/monitoring analysis). Optionally filter by reference_id and transaction_type_id, and paginate via the JSON:API links.next cursor (page_after) / links.prev (page_before). Returns JSON:API { data:[...], links } — objects may contain PII. Persona REST: GET /transactions.

NameTypeReqDescription
page_afterstring–Pagination cursor: return the page AFTER this record id (follow the links.next cursor).
page_beforestring–Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor).
page_sizeinteger–Page size — number of records per page.
reference_idstring–Filter by your own reference-id set on the transaction.
transaction_type_idstring–Filter by the transaction type id.

No output schema declared.

No examples provided.

Install

How do I install the Persona MCP by usefulapi server?

Persona MCP by usefulapi is a hosted endpoint at https://persona.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 · persona.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-persona 'https://persona.usefulapi.io/mcp'
Common questions

What is the Persona MCP by usefulapi server?

Persona MCP by usefulapi is listed in the public MCP registry as io.usefulapi/persona. Read Persona inquiries, accounts, verifications and reports. This page covers its hosted endpoint (https://persona.usefulapi.io/mcp).

Is the Persona MCP by usefulapi server safe to use?

Persona MCP by usefulapi scores 18 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 Persona MCP by usefulapi server expose?

Persona MCP by usefulapi exposes 14 tools: persona_list_inquiries, persona_get_inquiry, persona_list_accounts, persona_get_account, persona_get_verification, and 9 more. Their descriptions and schemas cost roughly 1,749 tokens of context every time the server is loaded.

Does the Persona MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Persona MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Persona MCP by usefulapi server still maintained?

Persona MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Persona MCP by usefulapi server?

VerifyMCP ran 4 checks on Persona MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Persona MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.