PEP Screening

io.github.Alex-Dev-Web-C-DEPublished by GitHub account Alex-Dev-Web-C-DEv1.0.0Updated Oct 29, 2026

Politically Exposed Persons screening for AI agents. 19K PEP records.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant screen names against a 19,000-record politically exposed persons (PEP) dataset.

What you can do
  • Screen individuals against a PEP dataset of about 19,000 records.
  • No tool list, instructions or README is published, so the exact operations and result fields are not documented; expect name-based screening lookups and match results.
When to use it
Useful when an assistant needs a quick PEP or sanctions-style check on a person, for example during onboarding, KYC-style due diligence or compliance research. Not a substitute for a vetted compliance provider.
Requirements
A remote streamable HTTP endpoint; no package, environment variable, header or authentication is declared. Network access to the provider's hosted endpoint is required.
Before you install
The endpoint is unauthenticated and the data source, freshness and coverage are undocumented, so matches may be incomplete or stale. Names submitted for screening are sent to a third-party server; avoid sending unnecessary personal data and verify results before relying on them.

Installation

In SourceWeft

  1. Open PEP Screening in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Alex-Dev-Web-C-DE%2Fpep-screening-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pep-screening": {
      "type": "http",
      "url": "https://pep-screening-mcp.boring-saas-infra.workers.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.