GCC Sanctions & Terror-List Screener
REMOTE · SCREEN.NOAHSARCH.TECH
Screen names vs OFAC, UN, EU, UK and UAE terrorist lists with Arabic-aware matching.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1811 tokens (~258/item across 7 items; 5 tools + 2 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 Management13
- Stability observed for 4 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
- 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 7 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 67
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 4 Nov 2026 · Probed https://screen.noahsarch.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noahsarch.tech | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 470026e1ea46ecc0e06d5a5a9df0965 |
| SANs: noahsarch.tech, *.noahsarch.tech | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of screen.noahsarch.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| noahsarch.tech. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://screen.noahsarch.tech/mcp | Verified | 200 | |
| http (plaintext) | http://screen.noahsarch.tech/mcp | Inconclusive | 406 |
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 →
audit_report Produce an HTML audit report of a screening ~323
Screens 1–50 subjects and returns a self-contained HTML report (result.html): timestamp, each list with its version / fetched-at / SHA-256, the inputs, every hit with its explanation, and an explicit no-match statement for clear subjects — suitable for the client's AML file (open in a browser, print to PDF). One charge per report. Example: subjects [{name:'Qusay Saddam Hussein', dob:'1966'}], case_reference 'KYC-2026-0412', prepared_by 'MLRO'. Response: result plus data_confidence, estimated_items[], sources[] (official list pages), data_version (snapshot id), warnings[] (e.g. a list snapshot older than 7 days) and a disclaimer. Lists: ofac_sdn, ofac_cons, un, eu, uk, uae. Names are never logged; matching is deterministic (no AI) and runs offline against the bundled snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| case_reference | – | – | Your case / client file reference, printed on the report. |
| lists | – | – | Subset of lists to screen (default all): ofac_sdn, ofac_cons, un, eu, uk, uae. |
| min_score | number | – | Minimum score (0–100) for a hit to be returned; default 85. 80 widens the net for onboarding, 92 for alert review. |
| prepared_by | – | – | Name / role of the compliance officer, printed on the report. |
| subjects | array | yes | 1 to 50 subjects to include in one report. |
Structured output declared, but exposes no named fields.
No examples provided.
explain_match Show why two names do or don't match ~217
Normalises both names step by step (Unicode, Arabic letter folding, honorifics/particles dropped, merged 'Abdul…' forms split, romanisation variants folded) and returns every score component (token_sort, token_set, Jaro-Winkler, subset, or the cross-script skeleton) and the resulting score / strength. Free. Example: name_a 'Abd al-Rahman Al Shaikh', name_b 'عبدالرحمن الشيخ'. Response: result plus data_confidence, estimated_items[], sources[] (official list pages), data_version (snapshot id), warnings[] (e.g. a list snapshot older than 7 days) and a disclaimer. Lists: ofac_sdn, ofac_cons, un, eu, uk, uae. Names are never logged; matching is deterministic (no AI) and runs offline against the bundled snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| name_a | string | yes | First name to compare (Latin or Arabic). |
| name_b | string | yes | Second name to compare (Latin or Arabic). |
Structured output declared, but exposes no named fields.
No examples provided.
list_status Freshness and provenance of every bundled list ~167
Per list: entries (individuals / entities / vessels / aircraft), aliases, fetched_at, days_since_fetch (stale flag when older than 7 days), official source URL and page, SHA-256 of the downloaded file, licence/terms, and any failures of the last refresh. Free. Call it before relying on a 'clear' result in a regulated process. Response: result plus data_confidence, estimated_items[], sources[] (official list pages), data_version (snapshot id), warnings[] (e.g. a list snapshot older than 7 days) and a disclaimer. Lists: ofac_sdn, ofac_cons, un, eu, uk, uae. Names are never logged; matching is deterministic (no AI) and runs offline against the bundled snapshot.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
screen_batch Screen up to 500 names in one call ~314
Each subject may carry dob, nationality, entity_type, id_number and your reference. Identical rows are screened once (charged once). Returns per-subject decision_hint, hit_count, top_score and the top 5 hits, plus summary counts (clear / review / likely_match). Charged per unique name. Example: subjects [{name:'Ali Kony', reference:'C-17'}, {name:'شركة الأمل للتجارة', entity_type:'entity'}], default_nationality 'AE'. Response: result plus data_confidence, estimated_items[], sources[] (official list pages), data_version (snapshot id), warnings[] (e.g. a list snapshot older than 7 days) and a disclaimer. Lists: ofac_sdn, ofac_cons, un, eu, uk, uae. Names are never logged; matching is deterministic (no AI) and runs offline against the bundled snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| default_nationality | – | – | ISO2 applied to rows without a nationality. |
| lists | – | – | Subset of lists to screen (default all): ofac_sdn, ofac_cons, un, eu, uk, uae. |
| min_score | number | – | Minimum score (0–100) for a hit to be returned; default 85. 80 widens the net for onboarding, 92 for alert review. |
| subjects | array | yes | Up to 500 subjects (name + optional dob / nationality / entity_type / id_number / reference). Identical rows are screened once. |
Structured output declared, but exposes no named fields.
No examples provided.
screen_name Screen one name against sanctions and terror lists ~452
Screen a person, company, vessel or aircraft name against OFAC SDN + Consolidated, UN, EU, UK and the UAE Local Terrorist List. Returns up to 20 hits sorted by score with list, listed_name, aliases_matched, score, match_strength (exact / strong / possible / weak), matched_on (which alias, which normalisation, DOB / nationality / type agreement), programs, listed_on, DOBs, nationalities, id_numbers, reference and source_url, plus decision_hint. Example: name 'Mohamed Hussein Al-Tikriti', dob '1966', nationality 'IQ', entity_type 'individual'. Response: result plus data_confidence, estimated_items[], sources[] (official list pages), data_version (snapshot id), warnings[] (e.g. a list snapshot older than 7 days) and a disclaimer. Lists: ofac_sdn, ofac_cons, un, eu, uk, uae. Names are never logged; matching is deterministic (no AI) and runs offline against the bundled snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| dob | – | – | Date of birth 'YYYY', 'YYYY-MM' or 'YYYY-MM-DD'. Year match adds, mismatch subtracts; omit if unknown. |
| entity_type | string | – | individual | entity | vessel | aircraft | any (default). Disagreement with the listed type costs 20 points. |
| id_number | – | – | Passport / national ID / registration number. An exact match on a listed number is reported as 'exact' (score 100). |
| lists | – | – | Subset of lists to screen (default all): ofac_sdn, ofac_cons, un, eu, uk, uae. |
| min_score | number | – | Minimum score (0–100) for a hit to be returned; default 85. 80 widens the net for onboarding, 92 for alert review. |
| name | string | yes | Full name to screen, Latin or Arabic script (e.g. 'Mohamed Al Rashid' or 'محمد الراشد'). |
| nationality | – | – | Nationality / country of incorporation as ISO 3166-1 alpha-2 ('AE', 'IR', 'GB'). Omit if unknown. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the GCC Sanctions & Terror-List Screener MCP server?
GCC Sanctions & Terror-List Screener is a hosted endpoint at https://screen.noahsarch.tech/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 · screen.noahsarch.tech
claude mcp add --transport http tech-noahsarch-sanctions-screener 'https://screen.noahsarch.tech/mcp'
What is the GCC Sanctions & Terror-List Screener MCP server?
GCC Sanctions & Terror-List Screener is an MCP server listed in the public MCP registry as tech.noahsarch/sanctions-screener. Screen names vs OFAC, UN, EU, UK and UAE terrorist lists with Arabic-aware matching. This page covers its hosted endpoint (https://screen.noahsarch.tech/mcp).
Is the GCC Sanctions & Terror-List Screener MCP server safe to use?
GCC Sanctions & Terror-List Screener scores 69 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 GCC Sanctions & Terror-List Screener MCP server expose?
GCC Sanctions & Terror-List Screener exposes 5 tools: screen_name, screen_batch, audit_report, list_status, explain_match. Their descriptions and schemas cost roughly 1,473 tokens of context every time the server is loaded.
Does the GCC Sanctions & Terror-List Screener MCP server require authentication?
No. We connected to GCC Sanctions & Terror-List Screener without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GCC Sanctions & Terror-List Screener MCP server still maintained?
GCC Sanctions & Terror-List Screener is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.