Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.

Is persona-mcp free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does persona-mcp have?

14 tools: persona_list_accounts, persona_list_reports, persona_get_event, persona_get_verification, persona_get_case, persona_get_account, persona_get_report, persona_list_transactions, ….

Is persona-mcp safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 2h ago

persona-mcp

https://persona.usefulapi.io

Registry code: ea5d104a863f16a8

api record

Tools for Persona, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Persona data. Free plan: 100 tool calls per month. Run persona_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run persona_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run persona_upgrade; it returns a Stripe Checkout link for the user to open. persona_cancel_subscription…

endpoint: https://persona.usefulapi.io/mcp
protocol: streamable-http ·2025-06-18
authentication: bearer
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is persona-mcp live?: Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is persona-mcp free to use?: Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does persona-mcp have?: 14 tools: persona_list_accounts, persona_list_reports, persona_get_event, persona_get_verification, persona_get_case, persona_get_account, persona_get_report, persona_list_transactions, ….
Is persona-mcp safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

98.4%

90 days 98.7%· all time 98.7%

latency

1,130ms

last good check

priced tools

of 14 tools

_ answered our checks, 90 days 303 checks · signed record

2026-11-14 00:08 degraded → live
2026-11-12 16:04 live → degraded· timeout after 20000ms
2026-10-18 18:20 degraded → live
2026-10-18 16:21 live → degraded· timeout after 20000ms
2026-10-12 10:04 degraded → live

_ what it is for

topic: security & compliance identity & verification
used for: list identity verification inquiries
get a kyc verification
get screening reports
list review cases
tag an account
takes → gives: text → data
tools: 13 reads1 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 14 tools

14 never probed 0 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

persona_list_accounts reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "page_size": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Page size — number of records per page."
    },
    "page_after": {
      "type": "string",
      "description": "Pagination cursor: return the page AFTER this record id (follow the links.next cursor)."
    },
    "page_before": {
      "type": "string",
      "description": "Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor)."
    },
    "reference_id": {
      "type": "string",
      "description": "Filter by your own reference-id set on the account."
    }
  }
}

arguments 24 lines

persona_list_reports reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "page_size": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Page size — number of records per page."
    },
    "page_after": {
      "type": "string",
      "description": "Pagination cursor: return the page AFTER this record id (follow the links.next cursor)."
    },
    "page_before": {
      "type": "string",
      "description": "Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor)."
    }
  }
}

arguments 20 lines

persona_get_event reads unknown never probed
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}.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "event_id" ], "properties": { "event_id": { "type": "string", "description": "The event id (e.g. evt_...)." } } }
arguments 13 lines
persona_get_verification reads unknown never probed
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}.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "verification_id" ], "properties": { "verification_id": { "type": "string", "description": "The verification id (e.g. ver_...)." } } }
arguments 13 lines

persona_get_case reads unknown never probed

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

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "case_id"
  ],
  "properties": {
    "case_id": {
      "type": "string",
      "description": "The case id (e.g. case_...)."
    }
  }
}

arguments 13 lines

persona_get_account reads unknown never probed
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}.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "account_id" ], "properties": { "account_id": { "type": "string", "description": "The account id (e.g. act_...)." } } }
arguments 13 lines
persona_get_report reads unknown never probed
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}.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "report_id" ], "properties": { "report_id": { "type": "string", "description": "The report id (e.g. report_...)." } } }
arguments 13 lines

persona_list_transactions reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "page_size": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Page size — number of records per page."
    },
    "page_after": {
      "type": "string",
      "description": "Pagination cursor: return the page AFTER this record id (follow the links.next cursor)."
    },
    "page_before": {
      "type": "string",
      "description": "Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor)."
    },
    "reference_id": {
      "type": "string",
      "description": "Filter by your own reference-id set on the transaction."
    },
    "transaction_type_id": {
      "type": "string",
      "description": "Filter by the transaction type id."
    }
  }
}

arguments 28 lines

persona_add_account_tag changes data unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "account_id",
    "tag_name"
  ],
  "properties": {
    "tag_name": {
      "type": "string",
      "description": "The tag name to add to the account."
    },
    "account_id": {
      "type": "string",
      "description": "The account id to tag (e.g. act_...)."
    }
  }
}

arguments 18 lines

persona_get_inquiry reads unknown never probed
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}.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "inquiry_id" ], "properties": { "inquiry_id": { "type": "string", "description": "The inquiry id (e.g. inq_...)." } } }
arguments 13 lines

persona_list_inquiries reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "status": {
      "type": "string",
      "description": "Filter by inquiry status (e.g. created, pending, completed, failed, expired, approved, declined)."
    },
    "page_size": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Page size — number of records per page."
    },
    "account_id": {
      "type": "string",
      "description": "Filter by the associated account id."
    },
    "page_after": {
      "type": "string",
      "description": "Pagination cursor: return the page AFTER this record id (follow the links.next cursor)."
    },
    "page_before": {
      "type": "string",
      "description": "Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor)."
    },
    "reference_id": {
      "type": "string",
      "description": "Filter by your own reference-id set on the inquiry."
    },
    "created_at_end": {
      "type": "string",
      "description": "Filter: inquiries created at/before this ISO 8601 timestamp."
    },
    "created_at_start": {
      "type": "string",
      "description": "Filter: inquiries created at/after this ISO 8601 timestamp."
    },
    "inquiry_template_id": {
      "type": "string",
      "description": "Filter by the inquiry template id (e.g. itmpl_...)."
    }
  }
}

arguments 44 lines

persona_list_cases reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "status": {
      "type": "string",
      "description": "Filter by case status (e.g. open, resolved, waiting)."
    },
    "page_size": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Page size — number of records per page."
    },
    "report_id": {
      "type": "string",
      "description": "Filter by an associated report id."
    },
    "account_id": {
      "type": "string",
      "description": "Filter by the associated account id."
    },
    "inquiry_id": {
      "type": "string",
      "description": "Filter by an associated inquiry id."
    },
    "page_after": {
      "type": "string",
      "description": "Pagination cursor: return the page AFTER this record id (follow the links.next cursor)."
    },
    "page_before": {
      "type": "string",
      "description": "Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor)."
    },
    "reference_id": {
      "type": "string",
      "description": "Filter by your own reference-id set on the case."
    },
    "case_template_id": {
      "type": "string",
      "description": "Filter by the case template id."
    }
  }
}

arguments 44 lines

persona_get_transaction reads unknown never probed
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}.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "transaction_id" ], "properties": { "transaction_id": { "type": "string", "description": "The transaction id (e.g. txn_...)." } } }
arguments 13 lines

persona_list_events reads unknown never probed

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.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "page_size": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": -9007199254740991,
      "description": "Page size — number of records per page."
    },
    "page_after": {
      "type": "string",
      "description": "Pagination cursor: return the page AFTER this record id (follow the links.next cursor)."
    },
    "page_before": {
      "type": "string",
      "description": "Pagination cursor: return the page BEFORE this record id (follow the links.prev cursor)."
    }
  }
}

arguments 20 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ea5d104a863f16a8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ea5d104a863f16a8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/ea5d104a863f16a8/badge.svg)](https://brick.blue/agent/ea5d104a863f16a8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on usefulapi.io 202 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

fleetio.usefulapi.io fleetio-mcp mcp · 44 tools
runcloud.usefulapi.io runcloud-mcp mcp · 36 tools
billomat.usefulapi.io billomat-mcp mcp · 34 tools
teamgate.usefulapi.io teamgate-mcp mcp · 34 tools
synchroteam.usefulapi.io synchroteam-mcp mcp · 33 tools
klippa-dochorizon.usefulapi.io klippa-dochorizon-mcp mcp · 30 tools
pipeline-crm.usefulapi.io pipeline-crm-mcp mcp · 30 tools
waitwhile.usefulapi.io waitwhile-mcp mcp · 29 tools

194 more sit on this domain. All of them.