Sanctions & PEP Screening
PYPI · MACAROONNETWORK-MCP-SANCTIONS-PEP-SCREENING-V1
Screen a name in one call against US OFAC SDN, the EU Consolidated Financial Sanctions List, UK…
Available components
Last scanned (8 hours ago)
Scores higher than 65% of PyPI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 54 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 189 tokens (~189/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 −2
- Stability: pass → 0.80 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/macaroonnetwork-mcp-sanctions-pep-screening-v1@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sanctions_pep_screening ~189
Screen a name in one call against US OFAC SDN, the EU Consolidated Financial Sanctions List, UK OFSI, the UN Security Council Consolidated List, and Wikidata-derived Politically Exposed Persons (PEP) data -- with fuzzy name matching, not exact-only. Real competitor research (2026-09-11) found this exact bundle+fuzzy-match shape is what actually converts in this niche; the single-source exact-match ofac-sanctions-search-v1 listing did not.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | Only set this after a prior call returned x402_payment_required and you've since signed the exact-scheme USDC payment it described with your own wallet -- set it to the resulting signed proof. Omit o… |
| query | string | yes | Name to screen, for example 'Vladimir Putin' or 'Banco Nacional de Cuba'. |
No output schema declared.
No examples provided.
How do I install the Sanctions & PEP Screening MCP server?
Sanctions & PEP Screening runs locally as a PyPI package, launched with uvx macaroonnetwork-mcp-sanctions-pep-screening-v1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · macaroonnetwork-mcp-sanctions-pep-screening-v1
claude mcp add com-macaroonnetwork-sanctions-pep-screening-v1 -- uvx macaroonnetwork-mcp-sanctions-pep-screening-v1
What is the Sanctions & PEP Screening MCP server?
Sanctions & PEP Screening is an MCP server listed in the public MCP registry as com.macaroonnetwork/sanctions-pep-screening-v1. Screen a name in one call against US OFAC SDN, the EU Consolidated Financial Sanctions List, UK… This page covers its PyPI package (macaroonnetwork-mcp-sanctions-pep-screening-v1).
Is the Sanctions & PEP Screening MCP server safe to use?
Sanctions & PEP Screening scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Sanctions & PEP Screening MCP server expose?
Sanctions & PEP Screening exposes 1 tool: sanctions_pep_screening. Their descriptions and schemas cost roughly 189 tokens of context every time the server is loaded.
Is the Sanctions & PEP Screening MCP server still maintained?
Sanctions & PEP Screening is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sanctions & PEP Screening MCP server under?
Sanctions & PEP Screening declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.