Connect-MCP

SanctionsKit developer MCP

io.github.SanctionsKit/sanctionskit · v1.0.1

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

MCPremoteno credentialsDocuments & PDF

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 9 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 80/100

What it does: 9 tools · 7 read, 2 write · Documents & PDF

Test call list_sources: needs a key: tool error: {"error":{"code":"authentication_required","message":"Connect a SanctionsKit sandbox account.","status":401}} (998 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +2
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://www.sanctionskit.com/mcp

Tools

9 tools listed at last check
  • 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.

Badge

Connect-MCP badge for io.github.SanctionsKit/sanctionskit

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.SanctionsKit/sanctionskit.svg)](https://clawy.uk/mcp/s/io.github.SanctionsKit/sanctionskit)

Repository · Website