Koskamo

Canada Sanctions Screening MCP

An MCP server that allows AI agents to screen names against Canada's consolidated autonomous sanctions list (SEMA). It supports single name checks, batch screening of up to 200 names with fuzzy matching, and retrieving regime-specific listings. The service offers a free tier for basic checks and a paid Pro tier for advanced features.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Canada Sanctions Screening MCP logo, by Donnie MorrisonCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-01Published by Donnie Morrison
MCP endpoint (Streamable HTTP)
https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp
Vendor documentation

What you can do with it

  • Screen one person, company or vessel name against Canada's consolidated autonomous sanctions list
  • Screen up to 200 names at once with an adjustable fuzzy threshold
  • Retrieve all listings for a country or regime, optionally filtered by date

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
ca-sanctions-screen-mcp 1.0.0
MCP protocol
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Canada Sanctions Screening. sanctions_check is free. Subscribe (C$25/month, cancel anytime) at https://ca-sanctions-screen-mcp.donniertf.workers.dev/buy for the paid tools, then pass access_token.

Tools

3 advertised

sanctions_check
Advertised by the server during the last successful anonymous check.

FREE. Screen one person, company or vessel name against Canada's consolidated autonomous sanctions list (SEMA / JVCFOA), incl. aliases. Best 3 matches.

sanctions_check input schema
{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    }
  }
}
batch_screen
Advertised by the server during the last successful anonymous check.

PRO. Screen up to 200 names at once with an adjustable fuzzy threshold (50–100). Audit-ready output with list version.

batch_screen input schema
{
  "type": "object",
  "required": [
    "names"
  ],
  "properties": {
    "names": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "threshold": {
      "type": "number"
    },
    "access_token": {
      "type": "string",
      "description": "Subscriber token from /success (or Authorization: Bearer)"
    }
  }
}
regime_list
Advertised by the server during the last successful anonymous check.

PRO. All listings for a country/regime (e.g. Russia, Iran, Belarus), optionally only those listed since a date.

regime_list input schema
{
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "type": {
      "type": "string"
    },
    "since": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "access_token": {
      "type": "string",
      "description": "Subscriber token from /success (or Authorization: Bearer)"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
630 ms
95th percentile latency
630 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 630 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http canada-sanctions-screening-mcp https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add canada-sanctions-screening-mcp --url https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable canada-sanctions-screening-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "canada-sanctions-screening-mcp": {
      "url": "https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "canada-sanctions-screening-mcp": {
      "type": "streamableHttp",
      "url": "https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start canada-sanctions-screening-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "canada-sanctions-screening-mcp": {
      "type": "http",
      "url": "https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http canada-sanctions-screening-mcp https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "canada-sanctions-screening-mcp": {
      "url": "https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "canada-sanctions-screening-mcp": {
      "serverUrl": "https://ca-sanctions-screen-mcp.donniertf.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Canada Sanctions Screening MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.