# io.usefulapi/persona (remote · persona.usefulapi.io)

Read Persona inquiries, accounts, verifications and reports.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `persona.usefulapi.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-persona/persona.md), [page](https://verifymcp.io/servers/io-usefulapi-persona/persona)

## Channel facts

- Endpoint: `https://persona.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-persona 'https://persona.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-persona": {
      "url": "https://persona.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-persona": {
      "type": "http",
      "url": "https://persona.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-persona]
url = "https://persona.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-persona": {
      "type": "remote",
      "url": "https://persona.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-persona --url 'https://persona.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-persona:
    url: "https://persona.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-persona": {
      "Transport": "http",
      "Url": "https://persona.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-persona -t streamable-http -u 'https://persona.usefulapi.io/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 77, +59)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07

### 2026-10-03 (score 18, −58)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-02 (score 76, +58)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (14)

### `persona_list_inquiries` (~285 tokens)

List inquiries

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.

Input parameters:

- `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).

### `persona_get_inquiry` (~76 tokens)

Get inquiry

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}.

Input parameters:

- `inquiry_id` (string, required): The inquiry id (e.g. inq_...).

### `persona_list_accounts` (~162 tokens)

List accounts

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.

Input parameters:

- `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.

### `persona_get_account` (~64 tokens)

Get account

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}.

Input parameters:

- `account_id` (string, required): The account id (e.g. act_...).

### `persona_get_verification` (~79 tokens)

Get verification

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}.

Input parameters:

- `verification_id` (string, required): The verification id (e.g. ver_...).

### `persona_list_reports` (~141 tokens)

List reports

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.

Input parameters:

- `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.

### `persona_get_report` (~74 tokens)

Get report

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}.

Input parameters:

- `report_id` (string, required): The report id (e.g. report_...).

### `persona_list_cases` (~253 tokens)

List cases

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.

Input parameters:

- `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).

### `persona_get_case` (~61 tokens)

Get case

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

Input parameters:

- `case_id` (string, required): The case id (e.g. case_...).

### `persona_list_transactions` (~176 tokens)

List transactions

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.

Input parameters:

- `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.

### `persona_get_transaction` (~66 tokens)

Get transaction

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}.

Input parameters:

- `transaction_id` (string, required): The transaction id (e.g. txn_...).

### `persona_list_events` (~145 tokens)

List events

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.

Input parameters:

- `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.

### `persona_get_event` (~68 tokens)

Get event

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}.

Input parameters:

- `event_id` (string, required): The event id (e.g. evt_...).

### `persona_add_account_tag` (~99 tokens)

Add account tag

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.

Input parameters:

- `account_id` (string, required): The account id to tag (e.g. act_...).
- `tag_name` (string, required): The tag name to add to the account.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-persona/persona#diagnostics

## Score history

- 2026-10-04: 77
- 2026-10-03: 18
- 2026-10-02: 76
- 2026-10-01: 18
- 2026-09-30: 18
- 2026-09-29: 18

## Common questions

### 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.

## Links

- Remote endpoint: https://persona.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-persona/persona.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-persona/persona.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-persona/persona