SanctionsKit developer MCP
REMOTE · WWW.SANCTIONSKIT.COM
Sanctions API docs and request validation, with account-linked synthetic sandbox testing.
Available components
Last scanned (22 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 22 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 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 Usability84
- 99% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 4681 tokens (~37/item across 124 items; 9 tools + 115 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.
- 9 Oct 26 +2
- Stability: unverified → 0.17 ▲ functional
- 4 Oct 26 73
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 22 Oct 2026 · Probed https://www.sanctionskit.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.sanctionskit.com | CN=YR2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 555838926b576d6ee43c292fe2eac924cb2 |
| SANs: *.sanctionskit.com, sanctionskit.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.sanctionskit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sanctionskit.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=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self' https://vercel.com/api/blob/ https://*.blob.vercel-storage.com; worker-src 'self' blob:; media-src 'self' blob:; manifest-src 'self'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.sanctionskit.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.sanctionskit.com/mcp | HTTPS enforced | 308 | https://www.sanctionskit.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_api_schema Inspect the REST API contract ~68
Without path, list consumer REST operations. With a path such as /screenings and lowercase method, retrieve its OpenAPI request, response, examples and referenced schemas. Describes REST capabilities; MCP account tools are sandbox only.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | – |
| path | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_doc Read an integration document ~43
Read a document returned by search_docs, including code examples and error handling. Uses a fixed local document catalog; does not fetch arbitrary URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_profile Identify the connected profile ~25
Identify the sandbox profile represented by the authenticated connection. Takes no user or workspace selector.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| id | string | yes | – |
| name | string | – | – |
| nickname | string | – | – |
No examples provided.
get_screening_result Read a sandbox screening result ~48
Retrieve retained evidence by screening ID from the connected sandbox workspace. An expired result is an error. Preserve coverage, versions, warnings and potential-match review requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
get_usage Check sandbox allowance ~21
Read the connected sandbox workspace allowance, completed subjects and pending reservations.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
list_sources Discover source coverage ~64
Read current source metadata and qualification from the connected sandbox workspace, with bounded pagination. Catalog/production source availability does not enable live MCP screenings; sandbox screening uses sandbox@1.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
run_sandbox_screening Test a sandbox screening ~101
Submit invented data to sandbox@1. Requires synthetic=true and an idempotencyKey of 8–128 URL-safe characters, reused unchanged with the same request for retries. Retains screening evidence according to policy and may create a review case; consumes sandbox allowance, never paid production allowance. Cannot screen production or link counterparties.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | yes | – |
| request | object | yes | – |
| synthetic | boolean | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
search_docs Search SanctionsKit documentation ~45
Find current integration documentation and guides by keyword. Returns document slugs for get_doc. Public; no account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
validate_screening_request Validate a screening request ~45
Validate request structure against the runtime REST screening schema without submitting or retaining it. Does not check live source eligibility or grant clearance. Use synthetic development inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| request | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No examples provided.
How do I install the SanctionsKit developer MCP server?
SanctionsKit developer MCP is a hosted endpoint at https://www.sanctionskit.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 · www.sanctionskit.com
claude mcp add --transport http sanctionskit-sanctionskit 'https://www.sanctionskit.com/mcp'
What is the SanctionsKit developer MCP server?
SanctionsKit developer MCP is listed in the public MCP registry as io.github.SanctionsKit/sanctionskit. Sanctions API docs and request validation, with account-linked synthetic sandbox testing. This page covers its hosted endpoint (https://www.sanctionskit.com/mcp).
Is the SanctionsKit developer MCP server safe to use?
SanctionsKit developer MCP scores 81 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 SanctionsKit developer MCP server expose?
SanctionsKit developer MCP exposes 9 tools: search_docs, get_doc, get_api_schema, validate_screening_request, list_sources, and 4 more. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.
Does the SanctionsKit developer MCP server require authentication?
No. We connected to SanctionsKit developer MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SanctionsKit developer MCP server still maintained?
SanctionsKit developer MCP is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.