Spark Pack
REMOTE · SPARK-PACK.NEROLABS.WORKERS.DEV
Cable sizing, Part P, certificate checks and G98/G99 for UK electricians' AI assistants
Available components
Last scanned (15 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category IoT and Hardware
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 21 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 61
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 21 Nov 2026 · Probed https://spark-pack.nerolabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nerolabs.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6de4049323d6abaa327886d7b5c76757b3a |
| SANs: *.nerolabs.workers.dev, nerolabs.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spark-pack.nerolabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spark-pack.nerolabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://spark-pack.nerolabs.workers.dev/mcp | Inconclusive | 405 |
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 →
check_certificate Check a filled certificate ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate | string | yes | – |
| data | object | yes | 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. |
No output schema declared.
No examples provided.
check_grid_connection G98, G99 or EV and heat pump notification? ~611
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}]}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
check_part_p Is this job notifiable under Part P? ~311
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"]}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The kind of work. Pick the most significant if the job has several parts (a new circuit outranks everything). |
No output schema declared.
No examples provided.
get_certificate_schema Certificate fields as a JSON schema ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate | string | yes | 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. |
No output schema declared.
No examples provided.
list_capabilities What Spark Pack can do ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
size_cable Cable size, voltage drop and earth fault loop check ~1,156
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
trade_profile Check the electrician's business details ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| trade | object | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · spark-pack.nerolabs.workers.dev
claude mcp add --transport http nero-engine-spark-pack 'https://spark-pack.nerolabs.workers.dev/mcp'
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.