Persona MCP by usefulapi
io.usefulapi/personausefulapi.iostreamable-httpv1.40.4Scanned
Read Persona inquiries, accounts, verifications and reports.
14 tools: 1 can delete or cancel things and 13 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Persona MCP by usefulapi can do
The Persona MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: persona_add_account_tag). 13 tools only read.
2 tools bring in text other people can write (persona_list_cases and persona_get_case).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 1Claude Code: deny
persona_add_account_tagWRITE: adds a tag to an account (mutates state).No findings
Why it is in this group
- The name "persona_add_account_tag" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Add account tag
- destructiveHint: true
Only reads 13Show 13 read-only tools
persona_get_accountGet a single account by id — the persistent identity record for an end user.No findings
Why it is in this group
- The name "persona_get_account" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get account
- readOnlyHint: true
persona_get_caseGet a single case by id — a manual-review workflow item.Reads text others writeNo findings
Why it is in this group
- The name "persona_get_case" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "review": it reads comments, which other people can write.
Description, as the server wrote it Get a single case by id — a manual-review workflow item. Returns JSON:API { data } containing PII. Persona REST: GET /cases/{case_id}.
Annotations the server declares
- title: Get case
- readOnlyHint: true
persona_get_eventGet a single audit-trail event by id, including its name and payload.No findings
Why it is in this group
- The name "persona_get_event" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get event
- readOnlyHint: true
persona_get_inquiryGet a single identity-verification inquiry by id, including its status, template, and relationships (verifications, account).No findings
Why it is in this group
- The name "persona_get_inquiry" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get inquiry
- readOnlyHint: true
persona_get_reportGet a single report by id — a screening/monitoring result (e.g.No findings
Why it is in this group
- The name "persona_get_report" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get report
- readOnlyHint: true
persona_get_transactionGet a single transaction by id — a record submitted for transaction fraud/monitoring analysis.No findings
Why it is in this group
- The name "persona_get_transaction" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get transaction
- readOnlyHint: true
persona_get_verificationGet a single verification by id — one identity check within an inquiry (e.g.No findings
Why it is in this group
- The name "persona_get_verification" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get verification
- readOnlyHint: true
persona_list_accountsList accounts (a persistent identity record for an end user, linking their inquiries/verifications over time).No findings
Why it is in this group
- The name "persona_list_accounts" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List accounts
- readOnlyHint: true
persona_list_casesList cases (manual-review workflow items grouping inquiries/reports for an analyst to adjudicate).Reads text others writeNo findings
Why it is in this group
- The name "persona_list_cases" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List cases
- readOnlyHint: true
persona_list_eventsList audit-trail events (an immutable log of actions across your Persona account — inquiry/account/case state changes, etc.).No findings
Why it is in this group
- The name "persona_list_events" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List events
- readOnlyHint: true
persona_list_inquiriesList identity-verification inquiries (an end-user's KYC verification session).No findings
Why it is in this group
- The name "persona_list_inquiries" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List inquiries
- readOnlyHint: true
persona_list_reportsList reports (screening/monitoring results such as watchlist, adverse-media, or business lookups).No findings
Why it is in this group
- The name "persona_list_reports" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List reports
- readOnlyHint: true
persona_list_transactionsList transactions (records submitted for transaction fraud/monitoring analysis).No findings
Why it is in this group
- The name "persona_list_transactions" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List transactions
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://persona.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://persona.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://persona.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://persona.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http persona https://persona.usefulapi.io/mcpclaude mcp add --transport http persona https://persona.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__persona__persona_list_inquiries",
"mcp__persona__persona_get_inquiry",
"mcp__persona__persona_list_accounts",
"mcp__persona__persona_get_account",
"mcp__persona__persona_get_verification",
"mcp__persona__persona_list_reports",
"mcp__persona__persona_get_report",
"mcp__persona__persona_list_cases",
"mcp__persona__persona_get_case",
"mcp__persona__persona_list_transactions",
"mcp__persona__persona_get_transaction",
"mcp__persona__persona_list_events",
"mcp__persona__persona_get_event"
],
"ask": [],
"deny": [
"mcp__persona__persona_add_account_tag"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as persona. Review it before you use it.
Capability tags behind 2 rules
- mcp__persona__persona_list_cases untrusted-input
- mcp__persona__persona_get_case untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/persona/verify?hash=9b35f6077a26ea0e318e7a89ea3bc60e8b6a17836a250baa2df4b3641a9e1e9b" | jq -e '.changed == false'Pinned hash 9b35f6077a26, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/persona/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/persona)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Persona MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Persona MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 14 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Persona MCP by usefulapi delete data?
- Yes. 1 tool can delete, cancel or revoke something: persona_add_account_tag.
Can the Persona MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Persona MCP by usefulapi have?
- 14 tools: 1 destructive, 13 read. persona_add_account_tag, persona_list_inquiries, persona_get_inquiry, persona_list_accounts, persona_get_account, persona_get_verification, persona_list_reports, persona_get_report and 6 more.
Does the Persona MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Persona MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Persona MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.