MCP.Market

ScreenSeal MCP server

online · 100% uptime
by wthall05·io.github.wthall05/screenseal-mcp·v1.0.0
No reviews yet

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

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed ScreenSeal yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ScreenSeal tools (1)

write = sends, deletes, buys or posts
  • screenseal_screenFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 327ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ScreenSeal compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
54 ms
faster than 92% of 30,031 servers

What its tools let an agent do: 1 read

Install ScreenSeal in Claude Code, Cursor or VS Code

claude mcp add --transport http screenseal-mcp https://screenseal-mcp.agent-tollbooth.workers.dev/mcp
Add to Cursor

ScreenSeal: common questions

Is ScreenSeal MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the ScreenSeal safety report
How do I install ScreenSeal?
It runs remotely at screenseal-mcp.agent-tollbooth.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does ScreenSeal need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is ScreenSeal maintained?
The last commit was 35 days ago (2026-09-30). The latest release is v1.0.0.
Is ScreenSeal up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does ScreenSeal compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.