85trust / 100

SanctionsKit developer MCP

by sanctionskit.com in Security & trust

MCP serverPassing, checked 1 h ago

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

https://www.sanctionskit.com/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
478 ms typical, 478 ms slowest 5%
Last check
1 h ago
Next check
in 4 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "sanctionskit-developer-mcp": {
      "type": "http",
      "url": "https://www.sanctionskit.com/mcp"
    }
  }
}

9 tools

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

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

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
1 h agoPassed200478 ms