Persona MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026

Read Persona inquiries, accounts, verifications and reports.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Hosted remote MCP server that lets an assistant read Persona identity-verification inquiries, accounts, verifications, reports, cases, transactions and audit…

What you can do
  • List and fetch identity-verification inquiries, with status, account, template and date filters
  • List and fetch accounts, the persistent identity records linking a user's inquiries and verifications
  • Fetch individual verifications with their check results
  • List and fetch screening reports such as watchlist, adverse-media and business lookups
  • List and fetch manual-review cases and transaction records submitted for fraud analysis
  • List and fetch audit-trail events, and add a tag to an account (the only write tool)
When to use it
Useful when you want to ask questions about a Persona account in plain language, such as how many verification inquiries are pending or failed this week, which cases are still open for manual review, or what a specific verification or screening report found.
Requirements
Remote endpoint at persona.usefulapi.io/mcp; no local install. Sign-in uses OAuth, and the login page asks for your Persona credentials, which are validated and stored per user. Do not add an Authorization header or API key to the client config. Free plan allows 50 tool calls per month.
Before you install
Responses contain PII from identity checks, so data passes through the hosted service and into the assistant's context. persona_add_account_tag changes Persona data. Paid plans cost $9/month or $90/year (Pro) and $39/month or $390/year (Pro+), billed through a Stripe Checkout link; upgrades charge the price difference immediately and cancellations are not refunded for the current period. Your Persona credentials are stored by the third-party host.

Installation

In SourceWeft

  1. Open Persona MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fpersona/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "persona-by-usefulapi": {
      "type": "http",
      "url": "https://persona.usefulapi.io/mcp"
    }
  }
}

README

Persona MCP by usefulapi

Read Persona inquiries, accounts, verifications and reports. Hosted, no local install.

Live endpoint: https://persona.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://persona.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http persona https://persona.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "persona": {      "url": "https://persona.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Persona credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/persona/

On first connect you'll paste your Persona credentials. They are validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
persona_list_inquiriesreadList inquiries
persona_get_inquiryreadGet inquiry
persona_list_accountsreadList accounts
persona_get_accountreadGet account
persona_get_verificationreadGet verification
persona_list_reportsreadList reports
persona_get_reportreadGet report
persona_list_casesreadList cases
persona_get_casereadGet case
persona_list_transactionsreadList transactions
persona_get_transactionreadGet transaction
persona_list_eventsreadList events
persona_get_eventreadGet event
persona_add_account_tagwriteAdd account tag
persona_usage_statusmetaUsage status (free-tier meter)
persona_request_featuremetaRequest a missing feature
persona_upgrademetaUpgrade to Pro or Pro+
persona_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this server only. Ask your AI to run persona_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with persona_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with persona_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT

Source: servers/persona/README.md at commit f22f848

Tools

14

persona_list_inquiries

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.

Parametersstatuspage_sizeaccount_idpage_afterpage_beforereference_idcreated_at_endcreated_at_startinquiry_template_id

persona_get_inquiry

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

Parametersinquiry_idrequired

persona_list_accounts

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.

Parameterspage_sizepage_afterpage_beforereference_id

persona_get_account

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

Parametersaccount_idrequired

persona_get_verification

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

Parametersverification_idrequired

persona_list_reports

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.

Parameterspage_sizepage_afterpage_before

persona_get_report

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

Parametersreport_idrequired

persona_list_cases

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.

Parametersstatuspage_sizereport_idaccount_idinquiry_idpage_afterpage_beforereference_idcase_template_id

persona_get_case

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

Parameterscase_idrequired

persona_list_transactions

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.

Parameterspage_sizepage_afterpage_beforereference_idtransaction_type_id

persona_get_transaction

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

Parameterstransaction_idrequired

persona_list_events

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.

Parameterspage_sizepage_afterpage_before

persona_get_event

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

Parametersevent_idrequired

persona_add_account_tag

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.

Parameterstag_namerequiredaccount_idrequired

Version history

26
  1. v1.39.2LatestNov 14, 2026
  2. v1.39.1Nov 13, 2026
  3. v1.38.0Nov 12, 2026
  4. v1.37.3Nov 11, 2026
  5. v1.36.5Nov 8, 2026
  6. v1.36.4Nov 7, 2026
  7. v1.35.3Nov 5, 2026
  8. v1.35.2Nov 5, 2026
  9. v1.35.1Nov 4, 2026
  10. v1.35.0Nov 3, 2026
  11. v1.34.1Nov 3, 2026
  12. v1.33.0Nov 1, 2026
  13. v1.31.0Oct 31, 2026
  14. v1.30.0Oct 31, 2026
  15. v1.29.2Oct 30, 2026
  16. v1.29.0Oct 30, 2026
  17. v1.24.0Oct 26, 2026
  18. v1.21.3Oct 25, 2026
  19. v1.21.0Oct 25, 2026
  20. v1.20.0Oct 24, 2026
  21. v1.17.0Oct 23, 2026
  22. v1.16.4Oct 22, 2026
  23. v1.16.3Oct 21, 2026
  24. v1.11.1Oct 9, 2026
  25. v1.10.0Oct 9, 2026
  26. v1.0.0Sep 29, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations