io.github.Braynexservices/nigeria-nigsac-sanctions
NPM · @BRAYNEXSERVICES/NIGERIA-MCP-NIGSAC-SANCTIONS · SCANNED SEP 24
Screen a name vs Nigeria's NIGSAC sanctions register. Best-effort signal, not compliance-grade.
Available components
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
- 39 of 124 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- 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
- Actively maintained (last published 66 days ago).Pass
- 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
{
"mcpServers": {
"braynexservices-nigeria-nigsac-sanctions": {
"command": "npx",
"args": [
"-y",
"@braynexservices/nigeria-mcp-nigsac-sanctions"
]
}
}
} {
"servers": {
"braynexservices-nigeria-nigsac-sanctions": {
"command": "npx",
"args": [
"-y",
"@braynexservices/nigeria-mcp-nigsac-sanctions"
]
}
}
} codex mcp add braynexservices-nigeria-nigsac-sanctions -- npx -y @braynexservices/nigeria-mcp-nigsac-sanctions
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"braynexservices-nigeria-nigsac-sanctions": {
"type": "local",
"command": [
"npx",
"-y",
"@braynexservices/nigeria-mcp-nigsac-sanctions"
],
"enabled": true
}
}
} openclaw mcp add braynexservices-nigeria-nigsac-sanctions --command npx --arg -y --arg @braynexservices/nigeria-mcp-nigsac-sanctions
mcp_servers:
braynexservices-nigeria-nigsac-sanctions:
command: "npx"
args: ["-y", "@braynexservices/nigeria-mcp-nigsac-sanctions"] {
"McpServers": {
"braynexservices-nigeria-nigsac-sanctions": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@braynexservices/nigeria-mcp-nigsac-sanctions"
]
}
}
} assistant mcp add braynexservices-nigeria-nigsac-sanctions -t stdio -c npx -a -y @braynexservices/nigeria-mcp-nigsac-sanctions
{
"mcpServers": {
"braynexservices-nigeria-nigsac-sanctions": {
"command": "npx",
"args": [
"-y",
"@braynexservices/nigeria-mcp-nigsac-sanctions"
]
}
}
} 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.
- 24 Sept 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.
- 22 Sept 26 −2
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 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.
- 18 Sept 26 −5
- Source repository: pass → fail ▼ security
- 17 Sept 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.
- 15 Sept 26 −1
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 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 →
Dependencies 124 packages
| Packages resolved | 124 |
|---|---|
| Stale | 39 |
| 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.
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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 24 September 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.