Persona MCP server

Read from the package source without running it. The installed server may list more.

• add_case_tag

  Add a tag to a case. Tags are operator-facing labels useful for grouping / filtering investigations (e.g. 'high-risk', 'manual-review', 'compliance-2026-q2').

• approve_inquiry

  Mark an inquiry as approved. This records your final decision on the Persona inquiry — useful for dashboard reporting and Persona's feedback loop. Does NOT itself gate the user; you must still enforce the decision in your app.

• create_accountwrite action

  Create a persistent Persona account — a long-lived end-user record that multiple inquiries can attach to. Enables re-use of previously verified fields and longitudinal fraud signals across sessions.

• create_casewrite action

  Open a case — a workspace for an ongoing investigation tied to one or more inquiries / accounts. Useful for manual review, periodic re-verification, or flagged users that need operator follow-up.

• create_inquirywrite action

  Create a Persona inquiry — a verification session bound to an inquiry template you configured in the Persona dashboard. The template defines which verifications run (document, selfie, database, phone, etc). Returns an inquiry id and (for hosted flows) a one-time link for the end user.

• decline_inquiry

  Mark an inquiry as declined. Records your final reject decision on the Persona inquiry for reporting and feedback.

• list_accounts

  List Persona accounts, filterable by reference-id (your internal user id) or email. Useful for looking up a persistent end-user record before creating duplicates.

• list_cases

  List investigation cases, filterable by status, assignee, or priority. Useful for operator dashboards or batch automation over the review queue.

• list_inquiries

  List inquiries, filterable by reference-id (your internal user id) or status. Useful for reconciling state or finding a user's inquiry history.

• list_reports

  List reports — individual verification artifacts (e.g. watchlist, adverse media, business lookup). Filterable by account and type. Each report is a standalone verification separate from inquiry-flow verifications.

• list_templates

  List inquiry templates configured in your Persona dashboard — returns each template's id (itmpl_...), name, and active version. Use this to discover available templates before calling create_inquiry.

• list_webhooks

  List configured webhook subscriptions (Persona calls them 'Webhook subscriptions'). Each entry shows the URL, subscribed event types, and enabled state. Use this to audit delivery endpoints for inquiry / verification / case events.

• redact_inquiry

  Redact an inquiry (GDPR right-to-erasure). Scrubs PII, captured images, and verification detail for this inquiry on Persona's side. Irreversible.

• resume_inquiry

  Resume a paused inquiry — returns a fresh one-time session token / link so the end user can continue a flow that was abandoned or needs additional steps (e.g. after a 'pending' webhook).

• retrieve_account

  Retrieve a Persona account by id, including summary PII and linked inquiries / verifications.

• retrieve_case

  Retrieve a case by id — full detail including status, assignee, linked objects, attached fields, and tags.

• retrieve_inquiry

  Retrieve an inquiry by id. Response includes overall status ('created' | 'pending' | 'completed' | 'expired' | 'failed' | 'needs_review' | 'approved' | 'declined') and embedded verifications / reports. Poll this to track progress.

• retrieve_report

  Retrieve a single report by id — returns the full verification detail (matches, scores, raw source data).

• run_reportwrite action

  Create and run a standalone Persona report — not tied to an inquiry flow. Use for ad-hoc watchlist screening, adverse media, business (KYB) lookups, address verification, or profile checks against a known identity. Pass the appropriate `report-type` plus the query fields the report needs.

• update_accountwrite action

  Patch attributes on an existing Persona account (e.g. update address, phone, tags). Use this to keep a persistent end-user record in sync with your system of record.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

20

the typical server has 7

Tools that change things

25%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 28,688 servers

Persona: common questions

Is Persona MCP server safe?

Mostly: it is graded B (82/100). Read the Persona safety report

How do I install Persona?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Persona need an API key?

Yes. The registry entry asks for PERSONA_API_KEY.

Is Persona maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.

What can I use instead of Persona?

Servers from other publishers that do the same job: Nautilus Compass Memory MCP server.

How does Persona compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 20 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.