
Scopeguard
io.github.Alex-Dev-Web-C-DEPublished by GitHub account Alex-Dev-Web-C-DEv1.0.1Updated Nov 6, 2026
Sanctions scope monitoring. Track entities for changes in OFAC/UK/EU/UN lists.
Overview
Local MCP server for ScopeGuard that screens names against OFAC, UK, EU and UN sanctions lists and manages webhook watch scopes.
- What you can do
- Screen a name against OFAC, UK, EU and UN sanctions lists
- Register a watch scope pairing an entity with a webhook URL
- List all registered scopes
- Delete a scope by its ID
- When to use it
- Useful when an assistant needs to check whether a person, company, country or industry appears on major sanctions lists, or to set up and maintain a watch list that notifies a webhook when new sanctions matches appear.
- Requirements
- Runs as a local stdio process installed from the npm package scopeguard-mcp (Node.js). No authentication, environment variables or headers are declared. Webhook URLs are supplied when registering a scope.
Installation
In SourceWeft
- Open Scopeguard in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
# ScopeGuard MCP
MCP server for **ScopeGuard** — sanctions scope monitoring with webhook alerts.
Register entities, countries, or industries and get webhook notifications when new sanctions hit your watch list.
## Tools
- register\_scope — Register a new scope (entity + webhook URL)
- list\_scopes — List all registered scopes
- check\_sanctions — Screen a name against OFAC + UK + EU + UN sanctions lists
- delete\_scope — Remove a scope by ID
## Install
Source: README.md at commit b091b19
Tools
0Version history
1- v1.0.1LatestOct 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.