Skip to content
Official MCP RegistryListed

SanctionsKit developer MCP

Sanctions API docs and request validation, with account-linked synthetic sandbox testing.

First seen 4 Oct 2026. Evidence as of 6 Oct 2026.

9
Tools
From an anonymous probe
1
Source listings
Each with its own history
2
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
get_api_schemaWithout 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.Read-only
get_docRead a document returned by search_docs, including code examples and error handling. Uses a fixed local document catalog; does not fetch arbitrary URLs.Read-only
get_profileIdentify the sandbox profile represented by the authenticated connection. Takes no user or workspace selector.Read-only
get_screening_resultRetrieve 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.Changes data
get_usageRead the connected sandbox workspace allowance, completed subjects and pending reservations.Read-only
list_sourcesRead 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.Read-only
run_sandbox_screeningSubmit 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.Changes data
search_docsFind current integration documentation and guides by keyword. Returns document slugs for get_doc. Public; no account needed.Read-only
validate_screening_requestValidate 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.Read-only

Change history

  1. Repository changed (registry)
  2. Listed (registry)
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.SanctionsKit/sanctionskit4 Oct 20266 Oct 20262