PayPerScreen vs mcp-sanctions
PayPerScreen is an MCP server published by TonytheTiger22. Marketplaces we read that list it: 1 (Official MCP Registry). mcp-sanctions is an MCP server published by atomno-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  PayPerScreen |  mcp-sanctions |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 64 Downloads/week (npm): 64 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (PyPI): 92 Downloads/week (PyPI): 74 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | PayPerScreen | mcp-sanctions |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-14 | Not published |
| Where it runs (differs) | On your machine (payperscreen-mcp) | On your machine (atomno-mcp-sanctions) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/tonythetiger22/payperscreen | github.com/atomno-mcp/mcp-sanctions |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
PayPerScreen
Sanctions, crypto wallet, email and IP screening for agents. Pay per check in USDC via x402.
mcp-sanctions
Sanctions/watchlist screening (RF, OFAC, EU, UK, UN) with confidence levels for KYC/AML.
How to run each
PayPerScreen As a local MCP server: npm package
claude mcp add --env "PAYPERSCREEN_PRIVATE_KEY=<YOUR_PAYPERSCREEN_PRIVATE_KEY>" --transport stdio payperscreen -- npx -y payperscreen-mcpRequires: PAYPERSCREEN_PRIVATE_KEY (secret)
mcp-sanctions As a local MCP server: PyPI package
claude mcp add --env "MCP_SANCTIONS_API_KEY=<YOUR_MCP_SANCTIONS_API_KEY>" --transport stdio mcp-sanctions -- uvx atomno-mcp-sanctionsRequires: MCP_SANCTIONS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only PayPerScreen asks for
PAYPERSCREEN_MAX_SPENDPAYPERSCREEN_NETWORKPAYPERSCREEN_PRIVATE_KEY (secret)
Only mcp-sanctions asks for
MCP_SANCTIONS_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: PayPerScreen · What it can do: mcp-sanctions · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.