Next free-source huntWe check for new free data every weekday.
OSINTMCP serverFirst audited Nov 13, 2026

SanctionsKit developer MCP

Sanctions API docs and request validation, with account-linked synthetic sandbox testing.The vendor's description, from its MCP Registry listing.

Passed public checksAudited Nov 13, 2026

Every public check ran and passed. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesConnected in 190 ms.
Sign-up?
None neededIt answered without any account or key.
Can it change things?
YesSome tools say they can change things. Your AI client should ask you first.
Endpointhttps://www.sanctionskit.com/mcp

Source code Website Streamable HTTP · protocol 2025-11-25 · server version 1.0.0

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

  • Passed: No hidden instructions found in tool text.

Safety labels

  • Note: 2 tools are labelled as able to change things.

    Expected for tools that send, write or buy. Your AI client should ask before calling them.

    • run_sandbox_screening
    • get_screening_result
  • Passed: Every tool says whether it only reads or can change things.

Tools

  • Passed: 9 tools listed.

  • Passed: Every tool describes its inputs with a valid schema.

Protocol

  • Passed: The MCP handshake works (Streamable HTTP).

  • Passed: Protocol version 2025-11-25 (latest).

  • Passed: Unknown requests are refused.

Connection

  • Passed: The server responds.

Tools (9)

As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.

  • search_docsFind current integration documentation and guides by keyword. Returns document slugs for get_doc. Public; no account needed.Read-only
  • get_docRead a document returned by search_docs, including code examples and error handling. Uses a fixed local document catalog; does not fetch arbitrary URLs.Read-only
  • get_api_schemaWithout 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…Read-only
  • validate_screening_requestValidate 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.Read-only
  • list_sourcesRead current source metadata and qualification from the connected sandbox workspace, with bounded pagination. Catalog/production source availability does not enable live MCP screenings; sandbox scree…Read-only
  • run_sandbox_screeningSubmit 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…Can change things
  • get_screening_resultRetrieve 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.Can change things
  • get_usageRead the connected sandbox workspace allowance, completed subjects and pending reservations.Read-only
  • get_profileIdentify the sandbox profile represented by the authenticated connection. Takes no user or workspace selector.Read-only

Audit history

  1. Nov 13Passed

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 200190 ms
initializedHTTP 20253 ms
tools/listHTTP 200331 ms
resources/listHTTP 20071 ms
prompts/listHTTP 20061 ms
unknown-methodHTTP 200116 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.