Jithox EU Counterparty Sanctions Preflight
REMOTE · SANCTIONS.MCP.JITHOX.COM · SCANNED SEP 21
Read-only EU counterparty sanctions preflight over MCP: screen names & identifiers, evidence
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 680 tokens (~136/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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'
{
"mcpServers": {
"com-jithox-eu-sanctions-preflight": {
"url": "https://sanctions.mcp.jithox.com/mcp"
}
}
} {
"servers": {
"com-jithox-eu-sanctions-preflight": {
"type": "http",
"url": "https://sanctions.mcp.jithox.com/mcp"
}
}
} [mcp_servers.com-jithox-eu-sanctions-preflight] url = "https://sanctions.mcp.jithox.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-jithox-eu-sanctions-preflight": {
"type": "remote",
"url": "https://sanctions.mcp.jithox.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-jithox-eu-sanctions-preflight --url 'https://sanctions.mcp.jithox.com/mcp' --transport streamable-http
mcp_servers:
com-jithox-eu-sanctions-preflight:
url: "https://sanctions.mcp.jithox.com/mcp" {
"McpServers": {
"com-jithox-eu-sanctions-preflight": {
"Transport": "http",
"Url": "https://sanctions.mcp.jithox.com/mcp"
}
}
} assistant mcp add com-jithox-eu-sanctions-preflight -t streamable-http -u 'https://sanctions.mcp.jithox.com/mcp'
{
"mcpServers": {
"com-jithox-eu-sanctions-preflight": {
"type": "http",
"url": "https://sanctions.mcp.jithox.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Sept 26 0
- Server version: 0.2.0 → 0.2.1 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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
- 7 Aug 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.0 → 0.2.0 functional
- 31 Jul 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
- 30 Jul 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 21 Sept 2026 · Probed https://sanctions.mcp.jithox.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sanctions.mcp.jithox.com | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 69385b20494b4c9f7383683fd8b6c9b9b3a |
| SANs: sanctions.mcp.jithox.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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.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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
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 | Verified | 200 | |
| http (plaintext) | http://sanctions.mcp.jithox.com/mcp | HTTPS enforced | 308 | https://sanctions.mcp.jithox.com/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 →
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.
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 counterparty sanctions preflight over MCP: screen names & identifiers, evidence. 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 88 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?
No. We connected to Jithox EU Counterparty Sanctions Preflight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jithox EU Counterparty Sanctions Preflight MCP server still maintained?
Jithox EU Counterparty Sanctions Preflight is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.