Check if a person is a PEP (Wikidata public offices) during KYC. $0.02/call via x402.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 1 tool
With only a single tool, there is no possibility of confusion or misselection; the purpose is unambiguous. An agent choosing this server has exactly one action available and the description clearly delimits it.
The lone tool name screen_pep follows a clean verb_noun snake_case convention that matches the domain vocabulary. There is no competing convention to create inconsistency.
One tool is thin for a PEP/KYC screening domain, which typically supports batch screening, source listing, candidate detail retrieval, and audit-history lookups. The single call is well-scoped to its narrow task, but the server surface feels minimal.
The core screening operation is robustly described (match states, confidence, sources, coverage caveats), but the surface exposes no batch screening, source/coverage listing, candidate detail endpoint, or audit retrieval. These are notable gaps for production KYC/AML workflows, though agents can work around them with repeated single calls.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
screen_pepChecks whether a person is a Politically Exposed Person (PEP) from the CPF, for compliance and AML d
Screen a party vs OFAC, EU and UK sanctions lists before paying. $0.02/call via x402.
Politically Exposed Persons screening for AI agents. 19K PEP records.
Checks whether a person is Politically Exposed (PEP) or is related to a PEP, from the CPF. Platform-
Add one secure layer between your agents and this server.