Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call
Nothing to run from here
Persona is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Persona inquiries, accounts, verifications and reports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-persona-mcp https://persona.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# persona_list_inquiries, persona_get_inquiry, persona_list_accounts and 11 more
Persona costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-persona-mcp https://persona.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by inquiry status (e.g. created, pending, completed, failed, expired, approved, declined). |
| account_id | string | no | Filter by the associated account id. |
| reference_id | string | no | Filter by your own reference-id set on the inquiry. |
| inquiry_template_id | string | no | Filter by the inquiry template id (e.g. itmpl_...). |
| created_at_start | string | no | Filter: inquiries created at/after this ISO 8601 timestamp. |
| created_at_end | string | no | Filter: inquiries created at/before this ISO 8601 timestamp. |
| page_size | integer | no | Page size — number of records per page. |
| page_after | string | no | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | no | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inquiry_id | string | yes | The inquiry id (e.g. inq_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference_id | string | no | Filter by your own reference-id set on the account. |
| page_size | integer | no | Page size — number of records per page. |
| page_after | string | no | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | no | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | The account id (e.g. act_...). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| verification_id | string | yes | The verification id (e.g. ver_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_size | integer | no | Page size — number of records per page. |
| page_after | string | no | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | no | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | yes | The report id (e.g. report_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by case status (e.g. open, resolved, waiting). |
| case_template_id | string | no | Filter by the case template id. |
| account_id | string | no | Filter by the associated account id. |
| reference_id | string | no | Filter by your own reference-id set on the case. |
| inquiry_id | string | no | Filter by an associated inquiry id. |
| report_id | string | no | Filter by an associated report id. |
| page_size | integer | no | Page size — number of records per page. |
| page_after | string | no | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | no | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
Get a single case by id — a manual-review workflow item. Returns JSON:API { data } containing PII. Persona REST: GET /cases/{case_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | The case id (e.g. case_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference_id | string | no | Filter by your own reference-id set on the transaction. |
| transaction_type_id | string | no | Filter by the transaction type id. |
| page_size | integer | no | Page size — number of records per page. |
| page_after | string | no | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | no | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction_id | string | yes | The transaction id (e.g. txn_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_size | integer | no | Page size — number of records per page. |
| page_after | string | no | Pagination cursor: return the page AFTER this record id (follow the links.next cursor). |
| page_before | string | no | Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (e.g. evt_...). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | The account id to tag (e.g. act_...). |
| tag_name | string | yes | The tag name to add to the account. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Persona or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Persona can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.