# SanctionsKit developer MCP

- Registry name: `io.github.SanctionsKit/sanctionskit` · version 1.0.1
- Categories (automatic, keyword rules): APIs & integrations, Developer tools
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.SanctionsKit%2Fsanctionskit
- Server page: https://mcpstation.net/s/io.github.SanctionsKit--sanctionskit.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

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

## Tools (as reported by the server, not verified)

- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html