# Spark Pack (remote · spark-pack.nerolabs.workers.dev)

Cable sizing, Part P, certificate checks and G98/G99 for UK electricians' AI assistants

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `spark-pack.nerolabs.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack.md), [page](https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack)

## Channel facts

- Endpoint: `https://spark-pack.nerolabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2849 tokens (~407/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Spark Pack MCP server?

Spark Pack is a hosted endpoint at https://spark-pack.nerolabs.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http nero-engine-spark-pack 'https://spark-pack.nerolabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nero-engine-spark-pack": {
      "url": "https://spark-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nero-engine-spark-pack": {
      "type": "http",
      "url": "https://spark-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nero-engine-spark-pack]
url = "https://spark-pack.nerolabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-spark-pack": {
      "type": "remote",
      "url": "https://spark-pack.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nero-engine-spark-pack --url 'https://spark-pack.nerolabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nero-engine-spark-pack:
    url: "https://spark-pack.nerolabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nero-engine-spark-pack": {
      "Transport": "http",
      "Url": "https://spark-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nero-engine-spark-pack -t streamable-http -u 'https://spark-pack.nerolabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nero-engine-spark-pack": {
      "type": "http",
      "url": "https://spark-pack.nerolabs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 61)

First indexed and scored.

## MCP tools (7)

### `list_capabilities` (~51 tokens)

What Spark Pack can do

Lists Spark Pack's tools, the regulations edition it targets, what it covers (nations, circuit types, cable types, installation methods) and what it deliberately does not do. Free, needs no input.

### `size_cable` (~1156 tokens)

Cable size, voltage drop and earth fault loop check

Sizes a UK final circuit or sub-main and shows the working: design current (with cooker diversity), protective device rating, the smallest cable size that passes current-carrying capacity, voltage drop (3% lighting, 5% other) and earth fault loop impedance (Zs against the maximum for B, C or D breakers), plus a cpc adiabatic check. Returns `recommended` (size and every check with status pass, fail, indicative_pass, needs_input), `sizes_considered` (one line per size), `must_check_against_regs` (points the electrician confirms in BS 7671) and sources. Current-carrying capacity comes from a cautious heat-flow model, not BS 7671 tables, so it is marked indicative; give `cable_size_mm2` plus `tabulated_capacity_a` from the regs for a firm check. Voltage drop and Zs are calculated from physics and are firm for the inputs given. Typical call: a 9.5 kW shower on an 18 m run clipped direct: {"circuit_type":"shower","load_kw":9.5,"run_length_m":18,"installation_method":"clipped_direct"}.

Input parameters:

- `ambient_c` (number): Ambient temperature, C. Defaults to 30 in air, 20 in the ground.
- `apply_cooker_diversity` (boolean): Cooker only: apply the usual domestic cooker diversity (default true).
- `armour_resistance_mohm_per_m` (number): SWA armour resistance from the cable datasheet, milliohms per metre, when the armour is the cpc.
- `cable_size_mm2` (number): Check this specific size as well as finding the smallest that passes.
- `cable_type` (string): Defaults to twin_and_earth, or swa_xlpe for buried runs and sub-mains.
- `circuit_type` (string, required): What the circuit feeds. ring_final and radial_sockets can be sized without a load (the device rating is used).
- `cooker_has_socket` (boolean): Cooker only: the cooker control unit has a socket outlet.
- `cores` (number): SWA only: number of cores. Defaults to 3 single phase (spare core as cpc) or 4 three phase. With 2 the armour is the cpc: give armour_resistance_mohm_per_m.
- `cpc_size_mm2` (number): Override the circuit protective conductor size (twin and earth sizes are known).
- `design_current_a` (number): Design current Ib in amps, if already known. Overrides load_kw.
- `earthing` (string): Supply earthing. Defaults to tn_c_s (PME).
- `grouped_circuits` (number): Number of circuits bunched together along the run, including this one. Defaults to 1.
- `grouping_factor` (number): Grouping factor Cg from the regs for the arrangement, if known. Without it Spark Pack uses a cautious estimate.
- `installation_method` (string, required): How the cable is run. clipped_direct: Clipped direct to a wall or surface, in free air; in_conduit_or_trunking_on_wall: In conduit or trunking fixed on a wall; in_conduit_in_insulated_wall: In condui…
- `load_kw` (number): Load in kW (for example 9.5 for a shower, 7.4 for a 32 A EV charger). Give this or design_current_a.
- `phases` (number): Defaults to 1.
- `power_factor` (number): Defaults to 1 (resistive loads, EV chargers). Use about 0.95 for heat pumps or mixed sub-main loads.
- `protective_device` (object): The breaker or fuse. Leave rating_a out to let Spark Pack choose the smallest standard rating at or above the design current.
- `run_length_m` (number, required): Cable length from the board to the furthest point, metres. For a ring, the total ring length.
- `soil_thermal_resistivity` (number): Buried runs: soil thermal resistivity K.m/W, defaults to 2.5 (cautious).
- `tabulated_capacity_a` (number): Tabulated current-carrying capacity It for cable_size_mm2 and this method, read from BS 7671 Appendix 4 by the electrician. Makes the capacity check firm.
- `trade` (object): Optional. The electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.
- `upstream_voltage_drop_percent` (number): Voltage drop already used upstream (for a circuit fed from a sub-board), percent.
- `ze_ohms` (number): Measured external earth fault loop impedance Ze, ohms. Without it the typical network maximum is used (0.35 TN-C-S, 0.8 TN-S).

### `check_part_p` (~311 tokens)

Is this job notifiable under Part P?

Answers whether domestic electrical work in England or Wales must be notified to building control under Part P of the Building Regulations, with the reason and what to do next (self-certify through a competent person scheme within 30 days, or tell building control before starting). England and Wales differ: in Wales kitchens and outdoor areas are still special locations. Returns `notifiable` (true or false), `answer`, `reason`, `what_to_do`, `must_check` and sources. Scotland and Northern Ireland return not_covered. Example: adding a socket in a kitchen in England: {"nation":"england","work":"add_to_or_alter_existing_circuit","locations":["kitchen"]}.

Input parameters:

- `building` (string): Defaults to dwelling.
- `locations` (array): Where the work is. bath_or_shower_zone means within the zoned space around a bath or shower. Defaults to ["elsewhere"].
- `nation` (string, required): Where the property is.
- `registered_with_competent_person_scheme` (boolean): Whether the electrician is registered with a scheme such as NICEIC or NAPIT. Changes the next steps.
- `trade` (object): Optional. The electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.
- `work` (string, required): The kind of work. Pick the most significant if the job has several parts (a new circuit outranks everything).

### `get_certificate_schema` (~214 tokens)

Certificate fields as a JSON schema

Returns the fields an Electrical Installation Certificate (eic), Minor Electrical Installation Works Certificate (minor_works) or Electrical Installation Condition Report (eicr) needs, as a JSON Schema the assistant fills from the job notes and test readings (spark-pack-certs-1.0 (for BS 7671:2018+A4:2026 certificates)). Includes which certificate to use when, and the contractor block prefilled from `trade` if given. check_certificate checks the filled object. Field names are Spark Pack's own; the electrician transfers the values to the official form in their scheme portal or software.

Input parameters:

- `certificate` (string, required): eic for new circuits, consumer units and new installations; minor_works for additions or alterations to one existing circuit; eicr for periodic inspection reports.
- `trade` (object): Optional. The electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.

### `check_certificate` (~207 tokens)

Check a filled certificate

Checks a filled EIC, Minor Works certificate or EICR (shape from get_certificate_schema) and returns `ready_to_transfer`, every missing required field by path, errors (readings that fail: insulation resistance under 1 megohm at 500 V, measured Zs above the maximum for the breaker, RCD trip times too slow, wrong polarity, an EICR marked satisfactory with a C1 or C2) and warnings (Zs above 80% of maximum, mismatched ring readings, low insulation resistance). Contractor fields left blank are filled from `trade`. Returns the (prefilled) data back.

Input parameters:

- `certificate` (string, required)
- `data` (object, required): The certificate object, shaped like the JSON Schema from get_certificate_schema.
- `trade` (object): Optional. The electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.

### `check_grid_connection` (~611 tokens)

G98, G99 or EV and heat pump notification?

For solar PV, batteries, V2G chargers, EV chargers and heat pumps in Great Britain: says which network operator process applies and when. Generation: G98 (fully type tested, 16 A / 3.68 kW per phase or less: install, then notify within 28 days) or G99 (apply and wait for acceptance before installing), counting existing generation and battery inverters. Demand: the ENA EV charge point and heat pump form (connect and notify within 28 days if every criterion is met, otherwise apply first), with each criterion marked true, false or null (not yet known). Returns `generation`, `demand`, `facts_to_put_on_the_form` (prefilled from inputs and `trade`), `missing_facts` and sources. Example: 5 kW solar plus a 5 kW battery inverter on single phase: {"supply_phases":1,"new_equipment":[{"type":"solar_pv","rating_kw":5,"type_tested":true},{"type":"battery","rating_kw":5,"type_tested":true}]}.

Input parameters:

- `battery_storage_kwh` (number)
- `commissioning_date` (string): YYYY-MM-DD.
- `ct_metered` (boolean)
- `cut_out_rating_a` (number): Network cut-out fuse rating, amps. Do not open the cut-out to find it.
- `earthing` (string): Supply earthing, for example TN-C-S.
- `existing_equipment` (array): Generation, storage or chargers already at the premises, same shape as new_equipment.
- `export_limit_kw` (number): Export limit if an export limiting scheme (G100) is fitted.
- `heat_pump_single_controller` (boolean)
- `load_limiting_device` (boolean): A load limiting or curtailment device keeps demand below the cut-out rating.
- `looped_service` (boolean): The supply is looped with a neighbour.
- `max_demand_after_a` (number): Premises maximum demand after the installation, amps per phase (from a load survey).
- `metered` (boolean): The supply is metered (defaults to unknown).
- `mpan` (string): Meter point administration number (the supply number on the bill).
- `multiple_premises` (boolean): Part of several installations in a close area (housing development, street-wide scheme).
- `nation` (string): Defaults to great_britain.
- `new_equipment` (array, required): Equipment being installed.
- `service_equipment_ok` (boolean): No safety or adequacy concerns with the cut-out and service cable.
- `site_postcode` (string)
- `supply_phases` (number): Defaults to 1.
- `trade` (object): Optional. The electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.

### `trade_profile` (~156 tokens)

Check the electrician's business details

Checks the electrician's own business details (Nero Trade Profile v1: trading name, Companies House number, competent person scheme and number, postcode, contact) and returns them cleaned, with a stable `nero_trade_ref` computed from the scheme registration or company number. The same object, given as `trade` to the other tools, prefills certificates and grid forms. Spark Pack stores nothing. The same profile and reference can later be used to sign the business into Nero Work, the agent job exchange for trades.

Input parameters:

- `trade` (object, required): Optional. The electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 61

## Common questions

### What is the Spark Pack MCP server?

Spark Pack is an MCP server listed in the public MCP registry as io.github.Nero-Engine/spark-pack. Cable sizing, Part P, certificate checks and G98/G99 for UK electricians' AI assistants. This page covers its hosted endpoint (https://spark-pack.nerolabs.workers.dev/mcp).

### Is the Spark Pack MCP server safe to use?

Spark Pack scores 65 out of 100 on VerifyMCP. 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 Spark Pack MCP server expose?

Spark Pack exposes 7 tools: list_capabilities, size_cable, check_part_p, get_certificate_schema, check_certificate, and 2 more. Their descriptions and schemas cost roughly 2,706 tokens of context every time the server is loaded.

### Does the Spark Pack MCP server require authentication?

No. We connected to Spark Pack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Spark Pack MCP server still maintained?

Spark Pack 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 did VerifyMCP test on the Spark Pack MCP server?

VerifyMCP ran 12 checks on Spark Pack, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Spark Pack: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://spark-pack.nerolabs.workers.dev/mcp
- Repository: https://github.com/Nero-Engine/spark-pack-mcp
- Website: https://spark-pack.nerolabs.workers.dev/docs
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-spark-pack/spark-pack
