# ScreenSeal [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/wthall05/screenseal-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/screenseal

## Description
Sanctions screening for AI agents: check a name against OFAC and EU lists. Free during launch.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What ScreenSeal does

The ScreenSeal MCP server provides sanctions screening for AI agents. Its documented purpose is narrow: check a name against sanctions lists maintained by the United States Office of Foreign Assets Control (OFAC) and the European Union.

This makes it relevant to agent workflows that need an initial sanctions-list check while handling names supplied in a conversation or process. The available description does not explain whether screening covers people, organizations, aliases, or other entity types, so those details should be confirmed before integrating it into a production review process.

ScreenSeal is listed in the 🔒 Security category. It should be treated as a screening aid, not as a complete compliance decision system, unless additional documentation establishes otherwise.

## Tools and capabilities

The documented capability is name screening against two sources:

- OFAC sanctions lists
- EU sanctions lists

The supplied material does not provide formal tool names, input schemas, output fields, match thresholds, or confidence indicators. It also does not say whether one request checks both sources automatically or exposes them as separate operations. Developers should avoid depending on a particular response format until the repository documentation or implementation confirms it.

The description identifies AI agents as the intended consumers, indicating that the capability is exposed through the Model Context Protocol rather than only as a standalone manual lookup. No other tools, list sources, search modes, or record-management features are documented.

## Limitations and notes

The repository README is unavailable in the supplied material. As a result, installation commands, supported MCP transports, authentication requirements, environment variables, client compatibility, and deployment instructions cannot be verified here.

The description says the service is free during launch. It does not define the launch period, establish a long-term price, or describe usage limits. Pricing and availability should therefore be checked before building a dependency on the service.

A sanctions-list result may require additional review in a real compliance workflow. The available information does not document how ScreenSeal handles spelling variations, transliteration, aliases, duplicate names, false positives, list freshness, audit records, or jurisdiction-specific decisions. Those omissions do not establish that the features are absent; they mean they are not confirmed by the supplied material.

For an evaluation, start with the basic name-screening use case and verify the returned data, source coverage, update timing, error behavior, and operational requirements. Keep any downstream approval or escalation logic outside the agent unless those controls are explicitly implemented and documented.

_Full upstream README: https://allmcps.com/mcp/screenseal/readme_