All servers · APIs & integrations

SanctionsKit developer MCP

io.github.SanctionsKit/sanctionskit · v1.0.1

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Can write (some tools are not declared read-only)
Capabilities declared	prompts, resources, tools
Tool definitions	9 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

Description written by the publisher, not verified

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

Connect

streamable-http · https://www.sanctionskit.com/mcp

claude mcp add --transport http sanctionskit https://www.sanctionskit.com/mcp

{
  "mcpServers": {
    "sanctionskit": {
      "url": "https://www.sanctionskit.com/mcp"
    }
  }
}

Tools as reported by the server

search_docs
Find current integration documentation and guides by keyword. Returns document slugs for get_doc. Public; no account needed.
get_doc
Read a document returned by search_docs, including code examples and error handling. Uses a fixed local document catalog; does not fetch arbitrary URLs.
get_api_schema
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.
validate_screening_request
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.
list_sources
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.
run_sandbox_screening
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.
get_screening_result
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.
get_usage
Read the connected sandbox workspace allowance, completed subjects and pending reservations.
get_profile
Identify the sandbox profile represented by the authenticated connection. Takes no user or workspace selector.

Repository · Website · JSON · Text for agents · Registry updated 2026-10-06