ScreenSeal

io.github.wthall05Published by GitHub account wthall05v1.0.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Screen a person or organization name against OFAC and EU financial sanctions lists, returning fuzzy matches with confidence scores and provenance.

What you can do
  • Screen a person or organization name against the current OFAC SDN, OFAC Consolidated Non-SDN and EU financial sanctions datasets.
  • Review potential fuzzy matches with confidence scores.
  • Inspect per-list provenance, including list versions, source URLs and SHA-256 digests.
  • Obtain a cryptographic EIP-712 attestation seal for the screening result.
When to use it
Useful when an assistant needs a quick sanctions check on a name during onboarding, vendor review, payment or compliance research, and when the result should carry provenance and an attestation.
Requirements
A remote MCP endpoint over streamable HTTP; no package, environment variables or headers are declared. The registry lists no authentication.
Before you install
Screening results are fuzzy matches with confidence scores, not a compliance determination, so verify hits before acting. The service is described as free during launch, which may change. Screening names sends them to a third-party remote service.

Installation

In SourceWeft

  1. Open ScreenSeal in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wthall05%2Fscreenseal-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "screenseal": {
      "type": "http",
      "url": "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

1

screenseal_screen

Screen a person or organization name against the current OFAC SDN, OFAC Consolidated Non-SDN, and EU financial sanctions datasets. Returns potential fuzzy matches with confidence scores, per-list provenance (list versions, source URLs, SHA-256 digests), and a cryptographic EIP-712 attestation sealing the exact response issued. Informational screening signal only — not a legal determination, sanctions certification, compliance clearance, or legal advice. Free during launch. For production volume, the same screening core is available as a paid x402 API: POST https://api-1-screening.agent-tollbooth.workers.dev/screen ($0.02 USDC/call on Base, no account or API key needed).

Parametersdobnamerequirednationality

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.