Nigeria NIGSAC Sanctions MCP by Wycord
NPM · @WYCORD/NIGERIA-MCP-NIGSAC-SANCTIONS
Screen a name vs Nigeria's NIGSAC sanctions register. Best-effort signal. A Wycord product.
Available components
Last scanned (19 hours ago)
Scores higher than 41% 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
- 39 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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
- 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 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
- 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
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.
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 57
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 22 Oct 2026 · Analysed npm/@wycord/nigeria-mcp-nigsac-sanctions@0.3.0
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 121 packages
| Packages resolved | 121 |
|---|---|
| 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.
How do I install the Nigeria NIGSAC Sanctions MCP by Wycord server?
Nigeria NIGSAC Sanctions MCP by Wycord runs locally as an npm package, launched with npx -y @wycord/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 · @wycord/nigeria-mcp-nigsac-sanctions
claude mcp add wycord-nigeria-nigsac-sanctions -- npx -y @wycord/nigeria-mcp-nigsac-sanctions
What is the Nigeria NIGSAC Sanctions MCP by Wycord server?
Nigeria NIGSAC Sanctions MCP by Wycord is listed in the public MCP registry as io.github.wycord/nigeria-nigsac-sanctions. Screen a name vs Nigeria's NIGSAC sanctions register. Best-effort signal. A Wycord product. This page covers its npm package (@wycord/nigeria-mcp-nigsac-sanctions).
Is the Nigeria NIGSAC Sanctions MCP by Wycord server safe to use?
Nigeria NIGSAC Sanctions MCP by Wycord scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Nigeria NIGSAC Sanctions MCP by Wycord server expose?
Nigeria NIGSAC Sanctions MCP by Wycord exposes 1 tool: screen_sanctions. Their descriptions and schemas cost roughly 182 tokens of context every time the server is loaded.
Is the Nigeria NIGSAC Sanctions MCP by Wycord server still maintained?
Nigeria NIGSAC Sanctions MCP by Wycord is still listed as active in the MCP registry. We last reached this channel on 22 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 Nigeria NIGSAC Sanctions MCP by Wycord server under?
Nigeria NIGSAC Sanctions MCP by Wycord declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.