SanctionsKit developer MCP
io.github.sanctionskit/sanctionskitSanctions API docs and request validation, with account-linked synthetic sandbox testing.
Score: 100/100
Handshake verified by our own probe.
Tools · 9
Find current integration documentation and guides by keyword. Returns document slugs for get_doc. Public; no account needed.
Read a document returned by search_docs, including code examples and error handling. Uses a fixed local document catalog; does not fetch arbitrary URLs.
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;…
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.
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 screen…
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 …
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.
Read the connected sandbox workspace allowance, completed subjects and pending reservations.
Identify the sandbox profile represented by the authenticated connection. Takes no user or workspace selector.
Resources · 116
sanctionskit://api/operations
Start with 250 free lifetime live screenings. Use the API or dashboard, review possible matches, and invite your team. Sandbox tests are optional.
sanctionskit://docs/docs/onboarding
Choose required lists, review steps, and retention rules. Publish a policy version so each screening uses the controls your team approved.
sanctionskit://docs/docs/policies
Save customer or vendor details, link them to screenings, and keep each record's history. Use explicit references to avoid merging similar names.
sanctionskit://docs/docs/counterparties
Find a screening's case, read its current review status, and send decisions to an authorized reviewer. Keep identity findings and business actions separate.
sanctionskit://docs/docs/review
Choose who can screen, review, approve, and manage your workspace. Set up document links, notices, and dates for your team.
sanctionskit://docs/docs/governance
Create a live API key, choose an available source, and run your first check with your free lifetime allowance. Sandbox testing is optional.
sanctionskit://docs/docs/quickstart
Create a key for your server, choose its permissions, and send it in the Authorization header. Keep sandbox and production keys separate.
sanctionskit://docs/docs/authentication
Find source IDs, check whether each list is available, and choose sources or a versioned package for your screening request.
sanctionskit://docs/docs/sources
Send one subject, choose its source coverage, and handle a possible match, no-match, or error. See the complete request and result fields.
sanctionskit://docs/docs/screenings
Send up to 100 subjects as JSON or upload a larger JSONL file. Track each row, inspect failures, and retry only the work that needs a new check.
sanctionskit://docs/docs/batches
Save a subject for regular sanctions checks. Set the cadence, read changes and failures, and pause or stop monitoring when your workflow needs it.
sanctionskit://docs/docs/monitoring
Use a screening ID to read its saved result, find the review case, or export evidence. Choose the right format and check what retention still permits.
sanctionskit://docs/docs/evidence
Receive screening and monitoring events, check their signatures, and process each event once. Fetch the saved result when you need its evidence.
sanctionskit://docs/docs/webhooks
Find the cause of a failed API request and choose the next step. Handle bad inputs, key errors, usage limits, and unavailable coverage separately.
sanctionskit://docs/docs/errors
Give each check a saved operation key. Reuse it after a timeout so one intended screening does not become two checks or duplicate usage.
sanctionskit://docs/docs/idempotency
Choose how long to keep screening evidence, understand minimal retention, and apply holds. Check what remains before relying on an older result.
sanctionskit://docs/docs/retention
Keep the source and matching versions used by each screening. Learn what changed and what each timestamp means when reviewing an older result.
sanctionskit://docs/docs/versions
Read your used, reserved, and remaining screening allowance. Count completed subjects across API requests, batches, dashboard checks, and monitoring.
sanctionskit://docs/docs/usage
Use the official SanctionsKit SDK or a Node.js fetch example. Run a sandbox check and retry requests without duplicating work.
sanctionskit://docs/integrations/typescript
Run a Python sanctions screening API example with no extra packages. Save results, handle failed requests, and retry the same check safely.
sanctionskit://docs/integrations/python
Add sanctions screening to an n8n workflow. Install the community node, connect a sandbox key, and try a sample that screens an invented person and retrieves evidence.
sanctionskit://docs/integrations/n8n
Give an AI SDK tool one retained sanctions screening result for human review. Preserve source records and retention limits without starting a new screening.
sanctionskit://docs/integrations/ai-sdk
Compare a possible sanctions match with reliable identity facts, explain your decision, and keep unresolved questions visible in SanctionsKit.
sanctionskit://docs/guides/false-positive-review
See why a company name check can miss an ownership issue. Work through OFAC's 50 Percent Rule examples and record separate owner screenings.
sanctionskit://docs/guides/ownership
Learn how sanctions name matching finds candidates, why a score is not proof of identity, and which facts help a reviewer resolve a match.
sanctionskit://docs/guides/name-matching
Use a birth year, month or full date without inventing detail. Learn how to compare partial sanctions dates and explain what remains unknown.
sanctionskit://docs/guides/uncertain-dates
Connect a sanctions screening API to real review work. Test result handling, retries, source failures, monitoring, and evidence before Production.
sanctionskit://docs/guides/rollout
Sanctions screening compares a person or business with selected sanctions lists. Learn what a result means and how to review it in SanctionsKit.
sanctionskit://docs/guides/what-is-sanctions-screening
Understand the sanctions step in AML screening, from customer details and source selection to case review, outside checks, and repeat screening.
sanctionskit://docs/guides/aml-screening
Learn how OFAC screening differs from a wider AML process and keep sanctions results, activity reviews, and business decisions separate.
sanctionskit://docs/guides/ofac-screening-vs-aml
KYC establishes who a customer is. Sanctions screening checks selected lists. Learn how both fit into AML work without merging their results.
sanctionskit://docs/guides/kyc-vs-aml-vs-sanctions-screening
Assess the sanctions-screening part of an AML software stack: test source scope, analyst review, approvals, evidence and repeat checks.
sanctionskit://docs/guides/aml-compliance-software
Connect sanctions evidence and analyst decisions to an AML case while keeping identity findings, activity reviews, and approvals clear.
sanctionskit://docs/guides/aml-case-management
Learn how to screen a customer, review a possible match, save the evidence, and keep future checks linked to the right person or business.
sanctionskit://docs/guides/customer-screening
Screen a supplier or customer without writing code. Learn how to choose coverage, review uncertain matches, keep evidence, and plan repeat checks.
sanctionskit://docs/guides/sanctions-screening-for-small-business
Learn what a sanctions review case contains, how to compare each candidate, and when outside checks and a second approval are needed.
sanctionskit://docs/guides/what-is-sanctions-case-management
Write a review note that explains the facts, missing evidence, identity decision, and business action, with examples for SanctionsKit cases.
sanctionskit://docs/guides/document-sanctions-screening-decision
Sort sanctions matches, changed evidence, failed checks, and pending approvals into the right work queues, with clear owners and follow-up.
sanctionskit://docs/guides/sanctions-alert-management
Investigate a possible sanctions match using the original record, reliable identity facts, and a clear handoff for any unresolved decision.
sanctionskit://docs/guides/sanctions-investigation
Trace a sanctions decision from the original check to analyst notes, outside evidence, and approval. Learn which records and exports to use.
sanctionskit://docs/guides/sanctions-screening-audit-trail
Set sources, review rules, matching sensitivity, outside checks, and monitoring in a versioned SanctionsKit policy your team can follow.
sanctionskit://docs/guides/sanctions-screening-policy
Test API results, failed checks, analyst review, monitoring, and evidence with synthetic cases, then record exactly what each test proves.
sanctionskit://docs/guides/sanctions-screening-testing
Evaluate matching sensitivity with the same labeled cases. Compare missed candidates and extra alerts before changing a SanctionsKit policy.
sanctionskit://docs/guides/sanctions-screening-matching-thresholds
Find why an expected sanctions candidate did not reach review by checking submitted facts, source versions, matching policy, and the handoff.
sanctionskit://docs/guides/sanctions-screening-false-negatives
Connect to the OFAC screening API, choose SDN or non-SDN coverage, and send matches to your review team. Start with a working sandbox example.
sanctionskit://docs/guides/ofac-api
Estimate sanctions screening API cost with worked examples for check volume and review time. Count completed checks, batch subjects and repeat monitoring.
sanctionskit://docs/guides/sanctions-screening-api-cost
Run an OFAC check for each required buyer, connect potential matches to the deal file, and handle purchaser changes before the next sales checkpoint.
sanctionskit://docs/guides/ofac-screening-for-auto-dealers
Build a real estate party roster, screen each required identity, record separate ownership work and reconcile changes before the transaction handoff.
sanctionskit://docs/guides/ofac-screening-for-real-estate
Connect required OFAC checks with the closing roster, resolve candidate matches and recheck changed payees before the settlement decision.
sanctionskit://docs/guides/ofac-screening-for-title-companies
Connect account intake, API results, analyst review and ongoing monitoring while keeping incomplete sanctions checks visible in fintech onboarding.
sanctionskit://docs/guides/sanctions-screening-for-fintech
Implement the sanctions-screening step in fintech onboarding with a synthetic request, safe retries, retained results and a clear analyst handoff.
sanctionskit://docs/guides/aml-screening-api-for-fintech
Screen required borrowers and guarantors, retain each result with the loan, and handle changed parties before funding and servicing handoffs.
sanctionskit://docs/guides/ofac-screening-for-lenders
Learn how to check policy and claim parties, review possible OFAC matches, and keep the right records when a beneficiary or payee changes.
sanctionskit://docs/guides/ofac-screening-for-insurance
Screen crypto customers by legal identity, connect candidates to account review and keep wallet analytics separate from the name-screening result.
sanctionskit://docs/guides/sanctions-screening-for-crypto
Keep MSB transfer parties distinct, recover incomplete screening requests and connect retained results with reviewers and ongoing customer checks.
sanctionskit://docs/guides/sanctions-screening-for-msbs
Check nonprofit partners and grant recipients, review possible sanctions matches, and keep separate approval and legal assessments linked to the program file.
sanctionskit://docs/guides/sanctions-screening-for-nonprofits
Build a Node.js OFAC API check with native fetch. Keep keys on the server, retry one saved operation, and send SDN matches to review.
sanctionskit://docs/guides/ofac-api-node
Run an OFAC API check in Python without extra packages. Use the standard library, preserve retry keys, and save SDN evidence for customer review.
sanctionskit://docs/guides/ofac-api-python
Add an OFAC API check to a PHP onboarding form with cURL. Keep the key on the server and link SDN results to the customer’s review.
sanctionskit://docs/guides/ofac-api-php
Use the OFAC API in a Ruby background job with Net::HTTP. Save the screening ID and reuse the same operation key when retrying a customer check.
sanctionskit://docs/guides/ofac-api-ruby
Build a Go service for OFAC API checks using the standard HTTP client. Select SDN coverage, handle failed requests, and save results for review.
sanctionskit://docs/guides/ofac-api-go
Call the OFAC API from a Rust worker with a blocking HTTP client. Keep request failures separate from SDN matches and completed no-match results.
sanctionskit://docs/guides/ofac-api-rust
Connect a Swift backend to the OFAC API. Keep secret keys out of distributed apps and route SDN matches into a saved review record.
sanctionskit://docs/guides/ofac-api-swift
Add OFAC API checks to a Java onboarding service. Run the Java 21 example with Jackson, then save SDN results and handle retries without duplicate checks.
sanctionskit://docs/guides/ofac-api-java
Connect an ASP.NET service to the OFAC API with C# and HttpClient. Run a sandbox check, preserve retry keys, and link SDN evidence to review.
sanctionskit://docs/guides/ofac-api-csharp
Call the UK sanctions API from Node.js with native fetch. Select the FCDO UK Sanctions List and keep source references with each customer check.
sanctionskit://docs/guides/uk-sanctions-api-node
Build a Python worker for UK sanctions API checks. Screen a customer portfolio against the FCDO list and retain partial dates for review.
sanctionskit://docs/guides/uk-sanctions-api-python
Select the FCDO list in a Go UK sanctions API request. Keep the source ID explicit and treat missing required coverage as a failed check.
sanctionskit://docs/guides/uk-sanctions-api-go
Use the Canadian sanctions API in Python for the autonomous list. Check customer records and preserve the cited regulation with each possible match.
sanctionskit://docs/guides/canada-sanctions-api-python
Add Canadian autonomous sanctions checks to a Swift backend. Keep API keys on the server and link source records to your identity review.
sanctionskit://docs/guides/canada-sanctions-api-swift
Screen suppliers with the Canadian sanctions API in PHP. Select the autonomous list and keep bilingual names and company IDs with the result.
sanctionskit://docs/guides/canada-sanctions-api-php
Add Australian sanctions API checks to Node.js onboarding. Select the DFAT list and retain its record references when aliases produce a possible match.
sanctionskit://docs/guides/australia-sanctions-api-node
Run Australian sanctions API checks in a Ruby background job. Use DFAT source IDs and save alias evidence with the customer’s review.
sanctionskit://docs/guides/australia-sanctions-api-ruby
Call the Australian sanctions API from an ASP.NET service. Use C# to select DFAT coverage, inspect errors, and retain evidence for review.
sanctionskit://docs/guides/australia-sanctions-api-csharp
Screen shipment parties through the U.S. CSL API in Java. Keep each candidate’s originating list and restriction with the review evidence.
sanctionskit://docs/guides/us-csl-api-java
Use the U.S. CSL API in a Rust trade-screening service. Preserve the component list behind each candidate so reviewers can check the actual restriction.
sanctionskit://docs/guides/us-csl-api-rust
Build a Go worker for U.S. CSL API checks on trading partners. Link results to local records and keep the originating list visible during review.
sanctionskit://docs/guides/us-csl-api-go
Use the EU sanctions API from Node.js to check financial-sanctions records. Preserve source IDs, partial dates and regulation references for review.
sanctionskit://docs/guides/eu-sanctions-data-node
Build a Python worker for the EU sanctions API’s financial list. Save each screening ID and compare the listed party with known customer details.
sanctionskit://docs/guides/eu-sanctions-data-python
Use the UN sanctions API in Node.js for listed people and entities. Keep UN references and aliases with results; vessels need separate coverage.
sanctionskit://docs/guides/un-sanctions-data-node
Use the UN sanctions API in a Python worker for people and entities. Save screening IDs and preserve weak-alias labels for review.
sanctionskit://docs/guides/un-sanctions-data-python
Learn how ongoing sanctions monitoring saves a subject, runs repeat checks, and sends changed evidence back to a reviewer in SanctionsKit.
sanctionskit://docs/guides/what-is-continuous-sanctions-monitoring
Set six-hour, daily, or weekly rescreening, estimate the workload, and check completed results instead of relying on a schedule alone.
sanctionskit://docs/guides/sanctions-screening-frequency
Compare customer rescreening, transaction-party screening, and activity monitoring, then keep their results and follow-up tasks clear.
sanctionskit://docs/guides/sanctions-monitoring-vs-transaction-monitoring
Build a webhook receiver that checks signatures, handles duplicate deliveries, retrieves current evidence, and keeps human review separate.
sanctionskit://docs/guides/monitoring-alerts-and-webhooks
Check that the right customers are enrolled, saved facts are current, scheduled screenings finish, and new evidence reaches a reviewer.
sanctionskit://docs/guides/sanctions-monitoring-program
Learn what OFAC does, how its sanctions lists fit into a customer check, and what to do with a possible match or a no-match result.
sanctionskit://docs/guides/what-is-ofac
Understand the OFAC SDN list, the people and entities it covers, and how to compare a possible match with the identity you are screening.
sanctionskit://docs/guides/what-is-ofac-sdn-list
Find OFAC's official search tool, then learn how to run a saved check, review possible matches and keep the evidence in SanctionsKit.
sanctionskit://docs/guides/what-is-ofac-check
Follow an OFAC screening process from legal-name input and source selection to match review, saved evidence and repeat checks in SanctionsKit.
sanctionskit://docs/guides/how-to-perform-ofac-search
Review an OFAC match by comparing identity facts, recording missing evidence and separating the match finding from the business decision.
sanctionskit://docs/guides/how-to-handle-ofac-match
Turn approved OFAC screening requirements into a working process. Set sources, reviewer roles, outside checks, repeat screening and recordkeeping.
sanctionskit://docs/guides/ofac-screening-requirements
Understand the scope of OFAC compliance and build a party roster that keeps customer, company, owner and payment-recipient checks distinct.
sanctionskit://docs/guides/who-must-comply-with-ofac
Learn why OFAC SDN and non-SDN coverage are separate, how to select both when required, and why the underlying list matters during review.
sanctionskit://docs/guides/ofac-sdn-vs-non-sdn
Connect OFAC recordkeeping duties with screening retention, case evidence, original documents, holds and exports in SanctionsKit.
sanctionskit://docs/guides/ofac-recordkeeping
Plan an OFAC API migration that preserves customer references, checks source availability and connects results to review, evidence and monitoring.
sanctionskit://docs/guides/ofac-api-vs-official-downloads
Run bulk OFAC screening for customers or suppliers. Prepare a CSV, check each row, resolve matches, and keep failed checks visible.
sanctionskit://docs/guides/ofac-batch-screening
Choose an OFAC guide for your next task: understand the lists, run a search, review a candidate, screen a portfolio or keep the evidence.
sanctionskit://docs/guides/ofac
Learn where sanctions screening fits into AML and KYC work, then connect customer checks, external assessments, case review and monitoring.
sanctionskit://docs/guides/aml
Find practical guides for match investigation, decision notes, approvals, audit history and the policies behind a sanctions review queue.
sanctionskit://docs/guides/case-management
Learn how to enroll subjects, choose repeat checks, investigate monitor failures and send new screening results to the right reviewer.
sanctionskit://docs/guides/monitoring
Choose available watchlist sources, understand different record types and keep PEP, adverse-media and ownership assessments connected to review.
sanctionskit://docs/guides/watchlists
Build a screening integration with language examples, source discovery, result handling and a clear handoff to dashboard review.
sanctionskit://docs/guides/developers
Find practical sanctions screening guides for deals, lending, insurance, fintech, money transfers, crypto businesses, and nonprofit partners.
sanctionskit://docs/guides/industries
Learn what a watchlist check covers, how to choose available sources, and why each possible match needs its own source context and review.
sanctionskit://docs/guides/what-is-watchlist-screening
Understand why sanctions records, other watchlists, and PEP findings need different evidence, review, and business decisions.
sanctionskit://docs/guides/watchlist-vs-sanctions-vs-pep
PEP screening checks whether a person holds a prominent public role. Learn how to verify identity, assess role evidence and record a review, with a worked example.
sanctionskit://docs/guides/pep-screening
Map required authorities to available sanctions sources, keep underlying list identities clear, and verify which versions each check used.
sanctionskit://docs/guides/global-sanctions-lists
Distinguish source imports, active versions, and completed customer screenings so a recent timestamp does not hide an outdated check.
sanctionskit://docs/guides/sanctions-data-freshness
Screen buyers, consignees, and end users against selected trade sources while keeping goods, licensing, and shipment decisions separate.
sanctionskit://docs/guides/restricted-party-screening
Compare news-based due diligence with sanctions list checks and record external media evidence without turning allegations into official findings.
sanctionskit://docs/guides/adverse-media-vs-sanctions-screening
Compare building a sanctions screening system with buying one, including data upkeep, matching tests, analyst review, evidence and operating cost.
sanctionskit://docs/guides/build-vs-buy-sanctions-screening
Use this checklist to compare manual lookup, an internal build and SanctionsKit on source coverage, match review, evidence and operating cost.
sanctionskit://docs/guides/sanctions-screening-software-comparison
Connect SanctionsKit to your coding agent so it can read the docs, write your integration, and test it with sample data.
sanctionskit://docs/resources/mcp
Connect your coding agent, sign in, and ask it to build a SanctionsKit integration. Start with these three steps.
sanctionskit://docs/guides/mcp-integration
Prompts · 1
Read current API contracts, implement server-side screening and test with synthetic sandbox subjects.
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://www.sanctionskit.com/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"sanctionskit_developer_mcp": {
"url": "https://www.sanctionskit.com/mcp",
"transport": "streamable-http"
}
}
}