Batch Sanctions Screening
REMOTE · SANCTIONS-BATCH-PRODUCTION.UP.RAILWAY.APP
Screen up to 100 names vs sanctions and US export lists. $0.50/batch via x402.
Available components
Last scanned (16 hours ago)
Scores higher than 6% of remote servers
Reachable. Last reached 19 Oct 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
- 17 Oct 26 −42
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool “batch_sanctions_screen” rewrote its description, which is the text the model reads security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Server version: 0.1.0 → 0.2.0 functional
- 16 Oct 26 65
First indexed and scored.
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 19 Oct 2026 · Probed https://sanctions-batch-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sanctions-batch-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sanctions-batch-production.up.railway.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://sanctions-batch-production.up.railway.app/mcp | HTTPS enforced | 301 | https://sanctions-batch-production.up.railway.app/mcp |
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 →
batch_sanctions_screen ~214
$0.50 per batch of up to 100 names. Screens person or company names vs OFAC SDN + Consolidated, EU and UK sanctions lists (UN via EU/UK) and optionally the US Consolidated Screening List. Per name: no_match, possible_match, confirmed_match or unable_to_determine, confidence, sources, top matches. Use when you must screen a whole customer, supplier or payee list (up to 100 names per call) against sanctions and US export-control lists, e.g. for onboarding backlogs or periodic re-screening. Paid per call via x402 (USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| include_export_control | boolean | – | Default true |
| matches_per_name | integer | – | Default 3 |
| min_score | number | – | Default 0.88 |
| names | array | yes | Names to screen (max 100) |
| payment_signature | string | – | x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements. |
No output schema declared.
No examples provided.
How do I install the Batch Sanctions Screening MCP server?
Batch Sanctions Screening is a hosted endpoint at https://sanctions-batch-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.
remote · sanctions-batch-production.up.railway.app
claude mcp add --transport http pcp183-sanctions-batch 'https://sanctions-batch-production.up.railway.app/mcp'
What is the Batch Sanctions Screening MCP server?
Batch Sanctions Screening is an MCP server listed in the public MCP registry as io.github.pcp183/sanctions-batch. Screen up to 100 names vs sanctions and US export lists. $0.50/batch via x402. This page covers its hosted endpoint (https://sanctions-batch-production.up.railway.app/mcp).
Is the Batch Sanctions Screening MCP server safe to use?
Batch Sanctions Screening 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 Batch Sanctions Screening MCP server expose?
Batch Sanctions Screening exposes 1 tool: batch_sanctions_screen. Their descriptions and schemas cost roughly 214 tokens of context every time the server is loaded.
Does the Batch Sanctions Screening MCP server require authentication?
Its publisher declares no required credentials for Batch Sanctions Screening. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Batch Sanctions Screening MCP server still maintained?
Batch Sanctions Screening 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.