# ScreenSeal (remote · screenseal-mcp.agent-tollbooth.workers.dev)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `screenseal-mcp.agent-tollbooth.workers.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/wthall05-screenseal-mcp/screenseal-mcp.md), [page](https://verifymcp.io/servers/wthall05-screenseal-mcp/screenseal-mcp)

## Channel facts

- Endpoint: `https://screenseal-mcp.agent-tollbooth.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 227 tokens (~227/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ScreenSeal MCP server?

ScreenSeal is a hosted endpoint at https://screenseal-mcp.agent-tollbooth.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http wthall05-screenseal-mcp 'https://screenseal-mcp.agent-tollbooth.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "wthall05-screenseal-mcp": {
      "url": "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wthall05-screenseal-mcp": {
      "type": "http",
      "url": "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.wthall05-screenseal-mcp]
url = "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wthall05-screenseal-mcp": {
      "type": "remote",
      "url": "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wthall05-screenseal-mcp --url 'https://screenseal-mcp.agent-tollbooth.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wthall05-screenseal-mcp:
    url: "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "wthall05-screenseal-mcp": {
      "Transport": "http",
      "Url": "https://screenseal-mcp.agent-tollbooth.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add wthall05-screenseal-mcp -t streamable-http -u 'https://screenseal-mcp.agent-tollbooth.workers.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 61, −1)

- [security] Tool “screenseal_screen” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail

### 2026-10-03 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-30 (score 60)

First indexed and scored.

## MCP tools (1)

### `screenseal_screen` (~227 tokens)

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).

Input parameters:

- `dob` (string): Date of birth as YYYY-MM-DD (optional; must be a real past date).
- `name` (string, required): Full name of the person or organization to screen (2-200 characters).
- `nationality` (string): ISO 3166-1 alpha-2 country code, e.g. "DE" (optional).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wthall05-screenseal-mcp/screenseal-mcp#diagnostics

## Score history

- 2026-10-04: 61
- 2026-10-03: 62
- 2026-10-02: 61
- 2026-10-01: 61
- 2026-09-30: 60

## Common questions

### What is the ScreenSeal MCP server?

ScreenSeal is an MCP server listed in the public MCP registry as io.github.wthall05/screenseal-mcp. Sanctions screening for AI agents: check a name against OFAC and EU lists. Free during launch. This page covers its hosted endpoint (https://screenseal-mcp.agent-tollbooth.workers.dev/mcp).

### Is the ScreenSeal MCP server safe to use?

ScreenSeal scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ScreenSeal MCP server expose?

ScreenSeal exposes 1 tool: screenseal_screen. Their descriptions and schemas cost roughly 227 tokens of context every time the server is loaded.

### Does the ScreenSeal MCP server require authentication?

No. We connected to ScreenSeal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ScreenSeal MCP server still maintained?

ScreenSeal is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://screenseal-mcp.agent-tollbooth.workers.dev/mcp
- Repository: https://github.com/wthall05/screenseal-mcp
- Website: https://apify.com/wthall05/screenseal-screen
- Changelog RSS feed: https://verifymcp.io/servers/wthall05-screenseal-mcp/screenseal-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wthall05-screenseal-mcp/screenseal-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wthall05-screenseal-mcp/screenseal-mcp