io.usefulapi/persona
REMOTE · PERSONA.USEFULAPI.IO · SCANNED OCT 4
Read Persona inquiries, accounts, verifications and reports.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1749 tokens (~124/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 14 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
How do I install the io.usefulapi/persona MCP server?
io.usefulapi/persona 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
claude mcp add --transport http io-usefulapi-persona 'https://persona.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-persona": {
"url": "https://persona.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-persona": {
"type": "http",
"url": "https://persona.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-persona] url = "https://persona.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-persona": {
"type": "remote",
"url": "https://persona.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-persona --url 'https://persona.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-persona:
url: "https://persona.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-persona": {
"Transport": "http",
"Url": "https://persona.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-persona -t streamable-http -u 'https://persona.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-persona": {
"type": "http",
"url": "https://persona.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +59
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- 3 Oct 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 +58
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
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 4 Oct 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 | 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 persona.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://persona.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://persona.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://persona.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://persona.usefulapi.io/mcp |
| Authorisation server | https://persona.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://persona.usefulapi.io/mcp | HTTPS enforced | 301 | https://persona.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 →
persona_add_account_tag 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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | The account id to tag (e.g. act_...). |
| tag_name | string | yes | The tag name to add to the account. |
No output schema declared.
No examples provided.
persona_get_account 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | The account id (e.g. act_...). |
No output schema declared.
No examples provided.
persona_get_case 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | The case id (e.g. case_...). |
No output schema declared.
No examples provided.
persona_get_event 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The event id (e.g. evt_...). |
No output schema declared.
No examples provided.
persona_get_inquiry 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| inquiry_id | string | yes | The inquiry id (e.g. inq_...). |
No output schema declared.
No examples provided.
persona_get_report 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | The report id (e.g. report_...). |
No output schema declared.
No examples provided.
persona_get_transaction 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | string | yes | The transaction id (e.g. txn_...). |
No output schema declared.
No examples provided.
persona_get_verification 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}.
| Name | Type | Req | Description |
|---|---|---|---|
| verification_id | string | yes | The verification id (e.g. ver_...). |
No output schema declared.
No examples provided.
persona_list_accounts 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page_after | string | – | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | – | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
| page_size | integer | – | Page size — number of records per page. |
| reference_id | string | – | Filter by your own reference-id set on the account. |
No output schema declared.
No examples provided.
persona_list_cases 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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Filter by the associated account id. |
| case_template_id | string | – | Filter by the case template id. |
| inquiry_id | string | – | Filter by an associated inquiry id. |
| page_after | string | – | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | – | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
| page_size | integer | – | Page size — number of records per page. |
| reference_id | string | – | Filter by your own reference-id set on the case. |
| report_id | string | – | Filter by an associated report id. |
| status | string | – | Filter by case status (e.g. open, resolved, waiting). |
No output schema declared.
No examples provided.
persona_list_events 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page_after | string | – | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | – | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
| page_size | integer | – | Page size — number of records per page. |
No output schema declared.
No examples provided.
persona_list_inquiries 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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Filter by the associated account id. |
| created_at_end | string | – | Filter: inquiries created at/before this ISO 8601 timestamp. |
| created_at_start | string | – | Filter: inquiries created at/after this ISO 8601 timestamp. |
| inquiry_template_id | string | – | Filter by the inquiry template id (e.g. itmpl_...). |
| page_after | string | – | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | – | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
| page_size | integer | – | Page size — number of records per page. |
| reference_id | string | – | Filter by your own reference-id set on the inquiry. |
| status | string | – | Filter by inquiry status (e.g. created, pending, completed, failed, expired, approved, declined). |
No output schema declared.
No examples provided.
persona_list_reports 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page_after | string | – | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | – | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
| page_size | integer | – | Page size — number of records per page. |
No output schema declared.
No examples provided.
persona_list_transactions 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.
| Name | Type | Req | Description |
|---|---|---|---|
| page_after | string | – | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | – | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
| page_size | integer | – | Page size — number of records per page. |
| reference_id | string | – | Filter by your own reference-id set on the transaction. |
| transaction_type_id | string | – | Filter by the transaction type id. |
No output schema declared.
No examples provided.
What is the io.usefulapi/persona MCP server?
io.usefulapi/persona is an MCP server 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 io.usefulapi/persona MCP server safe to use?
io.usefulapi/persona scores 77 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 io.usefulapi/persona MCP server expose?
io.usefulapi/persona 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 io.usefulapi/persona MCP server require authentication?
Yes. io.usefulapi/persona 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 io.usefulapi/persona MCP server still maintained?
io.usefulapi/persona is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.