# PEP Screening (Politically Exposed Persons) (remote · pep-screen-production.up.railway.app)

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

- Trust score: 23/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- remote · `pep-screen-production.up.railway.app`: 23/100 (this document), [markdown](https://verifymcp.io/servers/pcp183-pep-screen/pep-screen-production.md), [page](https://verifymcp.io/servers/pcp183-pep-screen/pep-screen-production)

## Channel facts

- Endpoint: `https://pep-screen-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-19.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the PEP Screening (Politically Exposed Persons) MCP server?

PEP Screening (Politically Exposed Persons) is a hosted endpoint at https://pep-screen-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http pcp183-pep-screen 'https://pep-screen-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pcp183-pep-screen": {
      "url": "https://pep-screen-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pcp183-pep-screen": {
      "type": "http",
      "url": "https://pep-screen-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pcp183-pep-screen]
url = "https://pep-screen-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pcp183-pep-screen": {
      "type": "remote",
      "url": "https://pep-screen-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pcp183-pep-screen --url 'https://pep-screen-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pcp183-pep-screen:
    url: "https://pep-screen-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pcp183-pep-screen": {
      "Transport": "http",
      "Url": "https://pep-screen-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pcp183-pep-screen -t streamable-http -u 'https://pep-screen-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pcp183-pep-screen": {
      "type": "http",
      "url": "https://pep-screen-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 23, −42)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-16 (score 65)

First indexed and scored.

## MCP tools (1)

### `screen_pep` (~208 tokens)

Screen a person's name for politically exposed person (PEP) status worldwide: ranked candidates with public offices held (head of state, minister, MP, judge, ambassador...), start/end dates, current vs former, country, party, birth year and match score. Optional country and birth_year filters. Open CC0 Wikidata. Use when onboarding a customer, director or counterparty and you must check whether the person is a politically exposed person (PEP) before KYC/AML sign-off. Paid per call via x402 (USDC on Base).

Input parameters:

- `birth_year` (integer): Birth year to disambiguate
- `country` (string): ISO 3166-1 alpha-2 country, e.g. DE
- `limit` (integer): Max candidates (default 5)
- `name` (string, required): Full name of the person to screen
- `payment_signature` (string): x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pcp183-pep-screen/pep-screen-production#diagnostics

## Score history

- 2026-10-19: 23
- 2026-10-18: 23
- 2026-10-17: 23
- 2026-10-16: 65

## Common questions

### What is the PEP Screening (Politically Exposed Persons) MCP server?

PEP Screening (Politically Exposed Persons) is an MCP server listed in the public MCP registry as io.github.pcp183/pep-screen. Check if a person is a PEP (Wikidata public offices) during KYC. $0.02/call via x402. This page covers its hosted endpoint (https://pep-screen-production.up.railway.app/mcp).

### Is the PEP Screening (Politically Exposed Persons) MCP server safe to use?

PEP Screening (Politically Exposed Persons) scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the PEP Screening (Politically Exposed Persons) MCP server expose?

PEP Screening (Politically Exposed Persons) exposes 1 tool: screen_pep. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.

### Does the PEP Screening (Politically Exposed Persons) MCP server require authentication?

Its publisher declares no required credentials for PEP Screening (Politically Exposed Persons). We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the PEP Screening (Politically Exposed Persons) MCP server still maintained?

PEP Screening (Politically Exposed Persons) is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pep-screen-production.up.railway.app/mcp
- Repository: https://github.com/pcp183/pep-screen
- Website: https://pep-screen-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/pcp183-pep-screen/pep-screen-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/pcp183-pep-screen/pep-screen-production.json
- HTML version of this page: https://verifymcp.io/servers/pcp183-pep-screen/pep-screen-production