io.github.Braynexservices/nigeria-nigsac-sanctions
NPM · @BRAYNEXSERVICES/NIGERIA-MCP-NIGSAC-SANCTIONS
Screen a name vs Nigeria's NIGSAC sanctions register. Best-effort signal, not compliance-grade.
Available components
Last scanned (15 hours ago)
Scores higher than 51% 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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 122 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency16
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 182 tokens (~182/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 −3
- Stability: pass → 0.83 functional
- 4 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 3 Nov 26 −1
- Security disclosure: pass → unverified ▼ functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Analysed npm/@braynexservices/nigeria-mcp-nigsac-sanctions@0.1.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Deprecated | 1 |
| Stale | 40 |
| 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 →
screen_sanctions Screen a name against Nigerian sanctions lists ~182
Screen a person or company name against the official NIGSAC (Nigeria Sanctions Committee) list of Nigerian designations — both individuals and entities. Returns CLEAR or POTENTIAL_MATCH with candidates and similarity scores. Best-effort FUZZY name matching (diacritic-folded, transliteration-tolerant); it over-flags on purpose and is a screening signal for human review, NOT a legal determination or your sole compliance control. Scope: the NIGERIAN list only — a CLEAR result does not mean the subject is unsanctioned elsewhere (the UN consolidated list is not screened here). Default data source is the LIVE NIGSAC register; set SANCTIONS_PROVIDER=mock for an offline synthetic stub. Example: { name: 'Ibrahim Test Doe' }.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Person or company name to screen |
| Name | Type | Req | Description |
|---|---|---|---|
| listVersion | string|null | yes | Version/date of the list snapshot screened against, where known |
| matches | array | yes | Candidate matches, highest similarity first; empty when CLEAR |
| query | string | yes | The name that was screened |
| retrievedAt | string | yes | ISO-8601 timestamp when the record was fetched |
| source | string | yes | Which provider/source served this record (e.g. 'mock', 'public', 'mono') |
| status | string | yes | CLEAR = no candidate matches; POTENTIAL_MATCH = review the matches |
No examples provided.
How do I install the io.github.Braynexservices/nigeria-nigsac-sanctions MCP server?
io.github.Braynexservices/nigeria-nigsac-sanctions runs locally as an npm package, launched with npx -y @braynexservices/nigeria-mcp-nigsac-sanctions. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @braynexservices/nigeria-mcp-nigsac-sanctions
claude mcp add braynexservices-nigeria-nigsac-sanctions -- npx -y @braynexservices/nigeria-mcp-nigsac-sanctions
What is the io.github.Braynexservices/nigeria-nigsac-sanctions MCP server?
io.github.Braynexservices/nigeria-nigsac-sanctions is an MCP server listed in the public MCP registry as io.github.Braynexservices/nigeria-nigsac-sanctions. Screen a name vs Nigeria's NIGSAC sanctions register. Best-effort signal, not compliance-grade. This page covers its npm package (@braynexservices/nigeria-mcp-nigsac-sanctions).
Is the io.github.Braynexservices/nigeria-nigsac-sanctions MCP server safe to use?
io.github.Braynexservices/nigeria-nigsac-sanctions scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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.Braynexservices/nigeria-nigsac-sanctions MCP server expose?
io.github.Braynexservices/nigeria-nigsac-sanctions exposes 1 tool: screen_sanctions. Their descriptions and schemas cost roughly 182 tokens of context every time the server is loaded.
Is the io.github.Braynexservices/nigeria-nigsac-sanctions MCP server still maintained?
io.github.Braynexservices/nigeria-nigsac-sanctions is still listed as active in the MCP registry. We last reached this channel on 21 November 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.Braynexservices/nigeria-nigsac-sanctions MCP server under?
io.github.Braynexservices/nigeria-nigsac-sanctions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.Braynexservices/nigeria-nigsac-sanctions MCP server?
VerifyMCP ran 16 checks on io.github.Braynexservices/nigeria-nigsac-sanctions, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.