io.github.Braynexservices/nigeria-electricity
NPM · @BRAYNEXSERVICES/NIGERIA-MCP-ELECTRICITY
Read-only Nigerian electricity meter validation + DisCo list via VTpass (free keys). No payments.
Available components
Last scanned (17 hours ago)
Scores higher than 49% of npm servers
Category Finance and Payments
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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 158 tokens (~79/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
- Source repository: unverified → fail ▼ security
- 9 Nov 26 0
- Provenance: fail → unverified ▼ security
- 8 Nov 26 −2
- Stability: pass → 0.87 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 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-electricity@0.2.6
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 →
list_discos List Nigerian electricity DisCos ~34
List supported Nigerian electricity distribution companies (DisCos) with their codes. Use a returned code as the disco for validate_meter.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| discos | array | yes | – |
No examples provided.
validate_meter Validate Nigerian electricity meter ~124
Validate an electricity meter (read-only) and return the registered customer name/address and DisCo. Provide the meter number, DisCo code (see list_discos) and meter type. Does NOT buy power or pay bills. Example: { meter_number: '45010101010', disco: 'EKEDC', meter_type: 'prepaid' }.
| Name | Type | Req | Description |
|---|---|---|---|
| disco | string | yes | Distribution company code, e.g. EKEDC (see list_discos) |
| meter_number | string | yes | Electricity meter number |
| meter_type | string | yes | Meter type |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string|null | – | Service address (PII — pass-through) |
| customerName | string|null | – | Registered customer name (PII — pass-through) |
| disco | string | yes | Distribution company code, e.g. EKEDC / IKEDC / AEDC / PHED |
| meterNumber | string | yes | Electricity meter number |
| meterType | string | yes | prepaid | postpaid |
| 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') |
No examples provided.
How do I install the io.github.Braynexservices/nigeria-electricity MCP server?
io.github.Braynexservices/nigeria-electricity runs locally as an npm package, launched with npx -y @braynexservices/nigeria-mcp-electricity. 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-electricity
claude mcp add braynexservices-nigeria-electricity -- npx -y @braynexservices/nigeria-mcp-electricity
What is the io.github.Braynexservices/nigeria-electricity MCP server?
io.github.Braynexservices/nigeria-electricity is an MCP server listed in the public MCP registry as io.github.Braynexservices/nigeria-electricity. Read-only Nigerian electricity meter validation + DisCo list via VTpass (free keys). No payments. This page covers its npm package (@braynexservices/nigeria-mcp-electricity).
Is the io.github.Braynexservices/nigeria-electricity MCP server safe to use?
io.github.Braynexservices/nigeria-electricity scores 74 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-electricity MCP server expose?
io.github.Braynexservices/nigeria-electricity exposes 2 tools: validate_meter, list_discos. Their descriptions and schemas cost roughly 158 tokens of context every time the server is loaded.
Is the io.github.Braynexservices/nigeria-electricity MCP server still maintained?
io.github.Braynexservices/nigeria-electricity 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-electricity MCP server under?
io.github.Braynexservices/nigeria-electricity 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-electricity MCP server?
VerifyMCP ran 16 checks on io.github.Braynexservices/nigeria-electricity, 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.