io.github.Alex-Dev-Web-C-DE/scopeguard
NPM · @ALEX-DEV-WEB-C-DE/SCOPEGUARD-MCP
Sanctions scope monitoring. Track entities for changes in OFAC/UK/EU/UN lists.
Available components
Last scanned (19 hours ago)
Scores higher than 38% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 163 tokens (~40/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_scope" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed npm/@alex-dev-web-c-de/scopeguard-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_sanctions ~52
Screen a name against OFAC SDN, UK OFSI, EU Consolidated, and UN Consolidated sanctions lists.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Name to screen (person, company, vessel, aircraft) |
No output schema declared.
No examples provided.
delete_scope ~31
Delete a scope by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Scope ID to delete (from list_scopes) |
No output schema declared.
No examples provided.
list_scopes ~16
List all registered sanctions monitoring scopes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_scope ~64
Register a sanctions monitoring scope. You will get a webhook when matches change.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Entity name, country, or industry to monitor (e.g. Rosneft) |
| webhook_url | string | yes | HTTP(S) URL where we POST JSON on change |
No output schema declared.
No examples provided.
How do I install the io.github.Alex-Dev-Web-C-DE/scopeguard MCP server?
io.github.Alex-Dev-Web-C-DE/scopeguard runs locally as an npm package, launched with npx -y @alex-dev-web-c-de/scopeguard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @alex-dev-web-c-de/scopeguard-mcp
claude mcp add alex-dev-web-c-de-scopeguard -- npx -y @alex-dev-web-c-de/scopeguard-mcp
What is the io.github.Alex-Dev-Web-C-DE/scopeguard MCP server?
io.github.Alex-Dev-Web-C-DE/scopeguard is an MCP server listed in the public MCP registry as io.github.Alex-Dev-Web-C-DE/scopeguard. Sanctions scope monitoring. Track entities for changes in OFAC/UK/EU/UN lists. This page covers its npm package (@alex-dev-web-c-de/scopeguard-mcp).
Is the io.github.Alex-Dev-Web-C-DE/scopeguard MCP server safe to use?
io.github.Alex-Dev-Web-C-DE/scopeguard scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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 io.github.Alex-Dev-Web-C-DE/scopeguard MCP server expose?
io.github.Alex-Dev-Web-C-DE/scopeguard exposes 4 tools: register_scope, list_scopes, check_sanctions, delete_scope. Their descriptions and schemas cost roughly 163 tokens of context every time the server is loaded.
Is the io.github.Alex-Dev-Web-C-DE/scopeguard MCP server still maintained?
io.github.Alex-Dev-Web-C-DE/scopeguard is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Alex-Dev-Web-C-DE/scopeguard MCP server under?
io.github.Alex-Dev-Web-C-DE/scopeguard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.