mcpbeat Sign in

PEP Screening (Politically Exposed Persons) MCP Server

not responding

PEP Screening (Politically Exposed Persons) is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Check if a person is a PEP (Wikidata public offices) during KYC. $0.02/call via x402.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 23 days of history · worst day 0%
23 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
269 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct a tool description was rewritten screen_pep

PEP Screening (Politically Exposed Persons) does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add pep-screen --transport http https://pep-screen-production.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://pep-screen-production.up.railway.app/mcp
~/.codex/config.toml
[mcp_servers.pep-screen]
url = "https://pep-screen-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pep-screen": {
      "url": "https://pep-screen-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pep-screen": {
      "type": "http",
      "url": "https://pep-screen-production.up.railway.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

screen
screen_pep
Check whether a person is a politically exposed person (PEP) during KYC/AML onboarding. Screens a name (optional country, birth year) against public offices in Wikidata (CC0). Returns no_match, possible_match, confirmed_match or unable_to_determine with confidence, sources, coverage_limitations and candidates with offices held. Not complete PEP coverage; no relatives or associates. Use when onboarding a customer, director or beneficial owner. $0.02 per call, USDC on Base (x402).

Endpoints

URLTransportStateLatencyChecked
https://pep-screen-production.up.railway.app/mcp streamable-http answering 269 ms 9 min ago

Alternatives to PEP Screening (Politically Exposed Persons)

same job, measured the same way
ScrapeMole Wiki
by pages-scrapemole

Pay-per-call x402 Wikipedia summaries/search and Wikidata facts, with CC BY-SA attribution.

3 tools answering
Pyfile LLM & Data API
by pyfile-toolkit

Pay-per-call LLM chat plus data tools: DNS, crypto, Base gas, Wikipedia. x402 USDC or Lightning.

13 tools answering
YRUZ x402 tools
by xzntexe

Pay-per-call x402 tools: package advisories, EU tenders, Wikidata facts, promo board, web, crypto

56 tools answering
Wiki Title Check
by sadri-dridi

Check whether a Wikipedia title exists. Title discarded after the call.

30 tools answering
Politeia Agents
by politeia-agents

Public governance wiki where AI agents propose, debate, amend and vote.

16 tools answering
Wikidata + Google Knowledge Graph MCP
by dondego

Read-only Wikidata tools and identity evidence. Local optional Google KG; bounded public remote.

147 installs/wk 8 tools answering
Better Notion
by ai-aviate

Operate Notion with a single Markdown document — read, create, and update pages in one call.

61 installs/wk local only
E
Entity-ID Resolver
by entityresolver

Ambiguous name/ticker to verified IDs: SEC CIK, GLEIF LEI, ISIN, Wikidata, CoinGecko. Non-US too.

65 installs/wk local only

PEP Screening (Politically Exposed Persons) — questions

Answers built from our own checks of this server.

What can PEP Screening (Politically Exposed Persons) do?
It exposes 1 tools, read directly from the server on our last check. Among them: screen_pep. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is PEP Screening (Politically Exposed Persons) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 269 ms. The bar chart above shows every period we have measured.
Is PEP Screening (Politically Exposed Persons) still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists PEP Screening (Politically Exposed Persons) as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect PEP Screening (Politically Exposed Persons)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PEP Screening (Politically Exposed Persons) need an API key?
No. PEP Screening (Politically Exposed Persons) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.