Sanctions & Tariff Lookup
REMOTE · TRADECHECK.TRYSTARRYNIGHTOPS.COM
Screen names on US, UN, UK and EU sanctions lists; US HTS codes and total duty by origin.
Available components
Last scanned (18 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 Usability74
- 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 2149 tokens (~268/item across 8 items; 7 tools + 1 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 Management37
- Stability observed for 11 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 0
- Server version: 1.2.5 → 1.2.6 functional
- 19 Nov 26 +1
- Server version: 1.2.4 → 1.2.5 functional
- Server version: 1.2.3 → 1.2.4 functional
- Server version: 1.2.2 → 1.2.3 functional
- 17 Nov 26 +1
- Server version: 1.2.1 → 1.2.2 functional
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Server version: 1.2.0 → 1.2.1 functional
- 12 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.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ 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 Nov 2026 · Probed https://tradecheck.trystarrynightops.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trystarrynightops.com | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | d79f95e1b7da95fd0ea572463f0ee51a |
| SANs: trystarrynightops.com, tradecheck.trystarrynightops.com, *.tradecheck.trystarrynightops.com | ||||||
| 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 tradecheck.trystarrynightops.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| trystarrynightops.com. | No DS | 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://tradecheck.trystarrynightops.com/mcp | Verified | 200 | |
| http (plaintext) | http://tradecheck.trystarrynightops.com/mcp | Inconclusive | 405 |
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 →
compare_origins Compare the U.S. duty on one HTS line across countries of origin ~228
Computes the same duty total as duty_stack for one 8- or 10-digit HTS line across up to 30 countries of origin and returns them sorted from the lowest total, each with its base rate, the Chapter 99 headings applied and the number of open questions. Without "origins" it compares 20 large sources of U.S. imports. Each row uses default assumptions (no trade-agreement preference claimed, no special use).
| Name | Type | Req | Description |
|---|---|---|---|
| ad_valorem_equivalent_pct | number | – | Optional ad valorem equivalent, in percent, of a specific or compound column 1 rate. |
| answers | object | – | Optional answers applied to every origin, by question id, e.g. {"preference": true}. |
| hts_code | string | yes | HTS number with 8 or 10 digits, dotted or not, e.g. "9403.60.80". |
| origins | array | – | Countries of origin to compare: ISO 3166-1 alpha-2 codes or English names, e.g. ["CN", "VN", "MX"]. |
No output schema declared.
No examples provided.
duty_stack Total U.S. duty for an HTS line and a country of origin ~436
Adds up the U.S. import duty on one 8- or 10-digit HTS line for goods of one country of origin under the current HTS revision: the column 1 (or column 2) rate plus the Chapter 99 additional duties in force that this tool models (Section 232 actions on metals, vehicles and other products, the Section 301 actions on China, Brazil and the 60 economies of the forced-labor action, and the Section 338 duties on Canada). Returns each layer with its Chapter 99 heading, rate and U.S. note, the exemptions it found, the total, the assumptions it made with what changes if an assumption is wrong, measures that are printed in the schedule but not in force, and what is not covered (for example antidumping and countervailing duties). When a question cannot be settled from the code and origin, the result says so and gives a range.
| Name | Type | Req | Description |
|---|---|---|---|
| ad_valorem_equivalent_pct | number | – | Optional: for a line with a specific or compound column 1 rate, the duty payable divided by the customs value, in percent. Needed only when the result asks for it. |
| answers | object | – | Optional answers to the questions a previous result listed under "assumptions", by id, e.g. {"preference": true}. |
| customs_value_usd | number | – | Optional customs value in U.S. dollars; when given and the total is a percentage, an estimated duty amount is returned. |
| detail | string | – | "full" adds the complete text of each Chapter 99 heading. |
| hts_code | string | yes | HTS number with 8 or 10 digits, dotted or not, e.g. "6109.10.00" or "8471.30.01.00". Use hts_search to find a code from product words. |
| origin | string | yes | Country of origin of the goods: ISO 3166-1 alpha-2 code (e.g. "CN") or English name (e.g. "Vietnam"). For the European Union name the member state. |
No output schema declared.
No examples provided.
hts_rate Look up an HTS code and its duty rates ~176
Looks up one HTS code (4, 6, 8 or 10 digits, with or without dots) in the current Harmonized Tariff Schedule of the United States and returns its description, parent hierarchy, general, special (trade program) and column 2 duty rates, units, footnotes, Chapter 99 cross-references and the lines below it.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "summary" (default) shortens long texts and lists up to 25 lines below; "full" returns complete texts and up to 150 lines. |
| hts_code | string | yes | HTS number with 4, 6, 8 or 10 digits, dotted or not, e.g. "8471.30.01", "847130", "6109.10.00.12". |
No output schema declared.
No examples provided.
hts_search Search the U.S. tariff schedule (HTS) ~174
Searches the descriptions in the current Harmonized Tariff Schedule of the United States (USITC) for product words and returns matching 8- and 10-digit HTS lines with code, description, parent headings, general (column 1) duty rate and unit of quantity. Some everyday terms (for example laptop, drone, e-bike) are mapped to HTS wording, and the mapping is shown in the result.
| Name | Type | Req | Description |
|---|---|---|---|
| include_chapter_99 | boolean | – | Also return Chapter 99 lines (additional duties and temporary provisions). Default false. |
| keyword | string | yes | Product words, e.g. "copper wire", "lithium-ion batteries", "cotton t-shirts". |
| limit | integer | – | Maximum number of lines to return, 1 to 25 (default 10). |
No output schema declared.
No examples provided.
list_status Data versions and freshness ~80
Returns the versions of the mirrored data: each screening dataset (U.S. CSL, UN, UK, EU) with its as-of date, file timestamp, entry count and last update check, each list's name, agency, entry count and as-of date, the current HTS revision, and when the mirror was last built and last checked for updates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_parties Screen up to 25 names at once ~324
Screens up to 25 names in one call against the same list mirrors as screen_party (U.S. Consolidated Screening List, UN, UK and, when loaded, EU lists) and returns only the best possible match per name (or no match at the threshold) in compact form, with a summary count.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country filter: ISO 3166-1 alpha-2 code (e.g. "IR") or English name (e.g. "Iran"). Entries whose list record names only other countries are left out and counted; entries with no country on t… |
| lists | array | – | Optional: which lists to search. "us" = U.S. Consolidated Screening List (OFAC, BIS, State Department lists), "un" = UN Security Council Consolidated List, "uk" = UK Sanctions List (FCDO), "eu" = EU… |
| min_score | number | – | Similarity threshold from 0.5 to 1.0 (default 0.85). 1.0 = identical after normalization; lower values return more and weaker possible matches. |
| names | array | yes | Names to screen (1 to 25), e.g. ["Acme Trading LLC", "Mar Azul"]. |
| type | string | – | Optional entity type filter. Entries from lists that do not state a type are kept. |
No output schema declared.
No examples provided.
screen_party Screen a name against U.S. sanctions and export lists ~539
Screens one person, company, vessel or aircraft name against a mirrored copy of the U.S. Consolidated Screening List (trade.gov), which combines the export screening lists of the Departments of Commerce, State and the Treasury, including OFAC's Specially Designated Nationals (SDN) list and the BIS Entity List, and against mirrored copies of the UN Security Council Consolidated List, the UK Sanctions List (FCDO) and, when loaded, the EU consolidated financial sanctions list. Matches primary names and aliases while tolerating differences in case, accents, punctuation, word order, company suffixes (LLC, Ltd, GmbH, OOO), small typos, common transliterations and added place or office words (a city, a country, "head office", "branch"). Returns ranked possible matches with score, matched alias, list, programs, entity type, addresses, countries, IDs, a link to the official entry or list and the list's as-of date, or a no-match result at the chosen threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional country filter: ISO 3166-1 alpha-2 code (e.g. "IR") or English name (e.g. "Iran"). Entries whose list record names only other countries are left out and counted; entries with no country on t… |
| detail | string | – | "summary" (default) returns the key fields; "full" adds every alias, address, ID, date of birth and remark on the list entry. |
| limit | integer | – | Maximum number of matches to return, 1 to 25 (default 5). |
| lists | array | – | Optional: which lists to search. "us" = U.S. Consolidated Screening List (OFAC, BIS, State Department lists), "un" = UN Security Council Consolidated List, "uk" = UK Sanctions List (FCDO), "eu" = EU… |
| min_score | number | – | Similarity threshold from 0.5 to 1.0 (default 0.85). 1.0 = identical after normalization; lower values return more and weaker possible matches. |
| name | string | yes | Name to screen, as written on the document; any word order, with or without accents or a company suffix. Example: "Rosneft Oil Company". |
| type | string | – | Optional entity type filter. Entries from lists that do not state a type are kept. |
No output schema declared.
No examples provided.
How do I install the Sanctions & Tariff Lookup MCP server?
Sanctions & Tariff Lookup is a hosted endpoint at https://tradecheck.trystarrynightops.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 · tradecheck.trystarrynightops.com
claude mcp add --transport http com-trystarrynightops-sanctions-tariff-lookup 'https://tradecheck.trystarrynightops.com/mcp'
What is the Sanctions & Tariff Lookup MCP server?
Sanctions & Tariff Lookup is an MCP server listed in the public MCP registry as com.trystarrynightops/sanctions-tariff-lookup. Screen names on US, UN, UK and EU sanctions lists; US HTS codes and total duty by origin. This page covers its hosted endpoint (https://tradecheck.trystarrynightops.com/mcp).
Is the Sanctions & Tariff Lookup MCP server safe to use?
Sanctions & Tariff Lookup scores 72 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 Sanctions & Tariff Lookup MCP server expose?
Sanctions & Tariff Lookup exposes 7 tools: screen_party, screen_parties, list_status, hts_search, hts_rate, and 2 more. Their descriptions and schemas cost roughly 1,957 tokens of context every time the server is loaded.
Does the Sanctions & Tariff Lookup MCP server require authentication?
No. We connected to Sanctions & Tariff Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sanctions & Tariff Lookup MCP server still maintained?
Sanctions & Tariff Lookup is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Sanctions & Tariff Lookup MCP server?
VerifyMCP ran 13 checks on Sanctions & Tariff Lookup, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about Sanctions & Tariff Lookup: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.