Home / MCP registry index / io.github.cyanheads/sanctions-screening-mcp-server

io.github.cyanheads/sanctions-screening-mcp-server

io.github.cyanheads/sanctions-screening-mcp-server in the official MCP registry. Endpoint https://sanctions-screening.caseyjhand.com/mcp. Source: github.com/cyanheads/sanctions-screening-mcp-server.

The registry describes it as: Screen names against OFAC, EU, UK, UN sanctions lists; resolve entities via GLEIF. Screening aid.

We read its 7 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http sanctions-screening-mcp-server https://sanctions-screening.caseyjhand.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "sanctions-screening-mcp-server": {
      "url": "https://sanctions-screening.caseyjhand.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"sanctions-screening-mcp-server","type":"http","url":"https://sanctions-screening.caseyjhand.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

sanctions_screen_name sanctions_screen_identifier sanctions_get_designation sanctions_list_sources sanctions_resolve_entity sanctions_get_entity sanctions_trace_ownership

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-cyanheads-sanctions-screening-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-cyanheads-sanctions-screening-mcp-server)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.