SanctionsKit developer MCP

Reviewed 1d ago.

• tools: 9 tools scanned
• metadata: scanned

No findings.

Tools (9)

• 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. Cannot screen production or link counterparties.

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