Jithox EU Counterparty Sanctions Preflight
REMOTE · SANCTIONS.MCP.JITHOX.COM
Read-only EU sanctions preflight: screen names/IDs against EU list. Evidence, not a verdict.
Available components
Last scanned (9 hours ago)
Scores higher than 42% of remote servers
Unreachable for 4 days in a row. Last reached 1 Nov 2026.
Category Security
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- 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 not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- 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 we couldn't connect to verify it. 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.
- 5 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 0
- Server version: 0.2.1 → 0.2.2 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Server version: 0.2.0 → 0.2.1 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://sanctions.mcp.jithox.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sanctions.mcp.jithox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jithox.com. | 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 |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sanctions.mcp.jithox.com/mcp | Unreachable | ||
| http (plaintext) | http://sanctions.mcp.jithox.com/mcp | HTTPS enforced |
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 →
get_sanctions_listing Get an official listing detail ~107
Return the full official listing detail (names, programme, legal basis, listing date, identifier types, countries) for a candidate logicalId surfaced by a prior screen, with provenance. 'found' / 'not_found' / 'unavailable'. Screening evidence only; not a legal/compliance determination, not a clearance. Every result carries source, publication date, checksum and retrieval time.
| Name | Type | Req | Description |
|---|---|---|---|
| logicalId | string | – | The listing's logicalId (from a prior screen candidate). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
list_sanctions_regimes List EU sanctions regimes ~70
Enumerate the EU sanctions programmes/regimes present in the snapshot (regulation/legal basis, since date, subject count) — the policy-layer read. 'found' / 'unavailable'. Reference only, not legal advice. Every result carries source, publication date, checksum and retrieval time.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
prepare_screening_receipt Prepare a screening receipt ~124
Bundle the screening checks into one idempotent Ed25519-signed receipt committing to the HASHED inputs, sources, snapshot checksum, retrieval times and decision states — provable evidence of WHAT was screened and WHEN. Attests the checks, not a clearance or a 'not sanctioned' claim. Screening evidence only; not a legal/compliance determination, not a clearance.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | The screening results to attest (hashed inputs, sources, decision states — no raw PII). |
| createdAt | string | yes | ISO timestamp the bundle was assembled. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
screen_sanctioned_identifier Screen an identifier ~117
Deterministic EXACT match of an identifier (passport / national id / registration / other) against listed designations' identifiers — no fuzzy matching. 'match' / 'clear' / 'unavailable'. Screening evidence only; not a legal/compliance determination, not a clearance. A 'clear' is not a guarantee of non-designation — snapshot-scoped.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | – | The identifier value to check. |
| type | string | – | Optional identifier type (e.g. passport, national_id, registration). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
screen_sanctioned_name Screen a counterparty name ~170
Screen a counterparty name against a dated snapshot of the official EU Consolidated Financial Sanctions List. Returns ranked CANDIDATE designations with deterministic match scores, or 'clear'/'needs_review'/'possible_match'/'match'; no snapshot → 'unavailable'. Never a false clear on outage or fuzzy input. Screening evidence only; not a legal/compliance determination, not a clearance. A 'clear' is not a guarantee of non-designation — snapshot-scoped. Every result carries source, publication date, checksum and retrieval time.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO alpha-2 country to narrow. |
| name | string | – | Counterparty name to screen (test/non-production data). |
| subjectType | string | – | Optional narrowing to a person or an entity. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
How do I install the Jithox EU Counterparty Sanctions Preflight MCP server?
Jithox EU Counterparty Sanctions Preflight is a hosted endpoint at https://sanctions.mcp.jithox.com/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.mcp.jithox.com
claude mcp add --transport http com-jithox-eu-sanctions-preflight 'https://sanctions.mcp.jithox.com/mcp'
What is the Jithox EU Counterparty Sanctions Preflight MCP server?
Jithox EU Counterparty Sanctions Preflight is an MCP server listed in the public MCP registry as com.jithox/eu-sanctions-preflight. Read-only EU sanctions preflight: screen names/IDs against EU list. Evidence, not a verdict. This page covers its hosted endpoint (https://sanctions.mcp.jithox.com/mcp).
Is the Jithox EU Counterparty Sanctions Preflight MCP server safe to use?
Jithox EU Counterparty Sanctions Preflight scores 53 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 Jithox EU Counterparty Sanctions Preflight MCP server expose?
Jithox EU Counterparty Sanctions Preflight exposes 5 tools: screen_sanctioned_name, screen_sanctioned_identifier, get_sanctions_listing, list_sanctions_regimes, prepare_screening_receipt. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.
Does the Jithox EU Counterparty Sanctions Preflight MCP server require authentication?
Its publisher declares that Jithox EU Counterparty Sanctions Preflight requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Jithox EU Counterparty Sanctions Preflight MCP server still maintained?
Jithox EU Counterparty Sanctions Preflight is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.