Log inSubmit server

OFAC SDN Screening vs Kastell

A side-by-side look at the OFAC SDN Screening and Kastell MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

O
OFAC SDN ScreeningSecurityScreen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.38FairAuth: not declaredKastell logoKastellSecurity · Local subprocess (stdio)Server security auditing and hardening toolkit. 413 security checks across 29 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 19-step production hardening, fleet management, and forensic evidence collection. Supports Hetzner, DigitalOcean, Vultr, and Linode. 13 MCP tools.61GoodAuth: no auth required

Verdict: choose OFAC SDN Screening for security work; choose Kastell for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

O
Choose OFAC SDN Screening when

  • You need dedicated capabilities in the Security domain.
Explore OFAC SDN Screening

Kastell logoChoose Kastell when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Kastell

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
O
OFAC SDN Screening		Kastell logoKastell
CategorySecuritySecurity
Quality signal38/100 · Fair61/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—60
Directory activity 2 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView OFAC SDN Screening View Kastell

Tools & capabilities

OFAC SDN Screening tools

No tool names declared yet. Check the project README from the listing page.

Kastell tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

OFAC SDN Screening

No confirmed install command for OFAC SDN Screening yet — follow the setup steps linked from its listing page rather than a guessed package name.

Kastell

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kastelldev-kastell": {
      "command": "npx",
      "args": [
        "-y",
        "kastell"
      ]
    }
  }
}

Frequently asked questions

OFAC SDN Screening is categorized under Security and uses an install path we have not confirmed yet. Kastell belongs to Security and uses a local stdio subprocess. Pick OFAC SDN Screening for security work and Kastell for security.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. OFAC SDN Screening has no confirmed install command yet — follow its own setup instructions.

OFAC SDN Screening has no declared pricing — check the project's own site. Kastell is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ofac-sdn-screening and kastelldev-kastell as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, OFAC SDN Screening has a quality signal of 38/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Kastell has 61/100 (Good) with 5 views, 0 installs and 60 GitHub stars.

Popular comparisons with OFAC SDN Screening

Popular comparisons with Kastell