Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PlanElec Calculators

REMOTE · PLANELEC.BE

Free AREI cable sizing, Synergrid C10/26 inverter check, LED strip calculator. No account.

Available components

+3 this week 78 Trust /100

Last scanned (15 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

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 Security80
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2211 tokens (~276/item across 8 items; 8 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 Management53
  • Stability observed for 16 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 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.

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1

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

  • 6 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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://planelec.be/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=planelec.be CN=YR2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 RSA 4096 SHA256-RSA 5626cf202d6c65360ecf2207f0aee903dd4
SANs: planelec.be
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of planelec.be. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
be. DS published 45588 13 Verified
planelec.be. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'wasm-unsafe-eval' https://io.planelec.be; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' blob: https://*.supabase.co https://io.planelec.be; media-src 'self' blob:; worker-src 'self' blob:; frame-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=(self "https://sketch.planelec.be"), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://planelec.be/mcp/public Verified 200
http (plaintext) http://planelec.be/mcp/public HTTPS enforced 302 https://planelec.be/mcp/public
MCP tools · 8 exposed · ~2,107 tokens

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 →

Tool Tokens
calculate_led_strip ~492

Calculates power, current (total and per channel), required feed points, power-supply size and the extra-low-voltage feed cable for an analogue LED strip (5/12/24/48 V DC; single colour, CCT, RGB, RGBW, RGB+CCT). Provide the strip length in metres and either a preset or the datasheet values (voltage, colour channels, watts per metre at full load). Optional: cut unit, maximum length per feed, number of feeds, power-supply reserve, feed-cable length, material and cross-section, and voltage-drop limit. Planning values from datasheet data, not a manufacturer guarantee; current-carrying capacity, heat and AREI/RGIE rules for SELV, bathrooms and outdoor areas are not checked. The response includes a shareable link that opens the calculation on planelec.be.

NameTypeReqDescription
colorModestring–Colour channels: mono, cct, rgb, rgbw or rgbcct. Default: mono.
cutUnitMmnumber–Cut unit in mm; the length is rounded down to it.
feedCrossSectionMm2number–Planned feed-cable cross-section in mm²; omit for a recommendation only.
feedLengthMnumber–One-way feed-cable length from power supply to strip in m. Default: 5.
feedMaterialstring–Feed-cable conductor material. Default: CU.
feedsinteger–Planned number of feed points; defaults to the minimum.
lengthMnumberyesStrip length in metres.
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
maxFeedDropPercentnumber–Feed-cable voltage-drop limit in percent (planning assumption). Default: 3.
maxRunMnumber–Manufacturer's maximum strip length per feed in m. Default: 5.
powerPerMeterWnumber–Power per metre in W with all channels at full brightness. Default: 14.4.
presetstring–Typical strip class as starting values; explicit fields override it.
psuReservePercentnumber–Power-supply reserve in percent. Default: 20.
voltagenumber–Strip nominal voltage in V DC. Default: 24.
NameTypeReqDescription
channelsnumberyes–
currentAnumberyes–
feedComparisonarrayyes–
feedsnumberyes–
inputobjectyes–
nextStepsarrayyes–
overallStatusstringyes–
powerWnumberyes–
psuRequiredWnumberyes–
requiredFeedsnumberyes–
sourceobjectyes–
warningsarrayyes–

No examples provided.

check_inverter_c10_26 ~245

Checks whether a PV inverter, battery inverter or other power-generating unit (PGU) is on the Synergrid C10/26 list of devices homologated for connection to the Belgian grid. Returns the outcome (found, found_with_limitations, expired, not_found, brand), matching devices with homologation dates, limitations and firmware versions, and homologated alternatives when nothing matches. Where available, each match also carries a separate "datasheet" object with manufacturer datasheet values (DC voltage, MPPT data, links, source URLs, status, last verified date); these are NOT checked by Synergrid and are not part of the approval. Search by brand and model, for example "Huawei SUN2000-10KTL".

NameTypeReqDescription
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
phasesnumber–Optional: 1 or 3 phases, improves alternative suggestions.
querystringyesBrand and/or model, 2–80 characters.
smaxVanumber–Optional: apparent power in VA, improves alternative suggestions.
NameTypeReqDescription
alternativesarrayyes–
dataDatestring|nullyes–
matchesarrayyes–
nextStepsarrayyes–
officialSourceobjectyes–
outcomestringyes–
sourceobjectyes–

No examples provided.

get_inverter_datasheet ~247

Returns manufacturer datasheet data for an inverter from the Synergrid C10/26 list: maximum DC voltage, MPPT count and range, current limits per MPPT, start voltage, maximum PV power, battery capability, optimizer architecture, links to the datasheet and installation manual, the product photo URL, source URL and page per value, status (verified = stated in the datasheet, secondary = unconfirmed) and the date last verified. These are manufacturer statements and are NOT part of the Synergrid approval; use check_inverter_c10_26 for the approval status. Look up by Synergrid reference (GLV…) or by brand and model.

NameTypeReqDescription
brandstring–Brand, e.g. Huawei. Use together with model.
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
modelstring–Model designation, e.g. SUN2000-5KTL-M1. Use together with brand.
referencestring–Synergrid reference, e.g. GLV073-06-0020. Alternative to brand and model.
NameTypeReqDescription
datasheetobjectyes–
notestringyes–
sourceobjectyes–

No examples provided.

get_regelwerk_article ~240

Returns the text of one article of Book 1 of the Belgian AREI/RGIE by its number (for example 4.2.4.3 or "AREI 7.1.4.3"), in the language of the text (Dutch, French or German; English uses the German text), with the edition, change notices of amending decrees, the titles of its sub-articles and a link to the article in the PlanElec reader. Cite the article number and edition when you pass the content on. Use search_regelwerk to find the number.

NameTypeReqDescription
articlestringyesArticle number such as 4.2.4.3; a prefix such as "AREI" or "RGIE" is accepted.
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
versionstring–Optional edition, e.g. v06 or v07. Default: the edition in force today (v06 until 31/10/2026, v07 from 01/11/2026).
NameTypeReqDescription
articlestring––
changesarray––
editionobject––
sourceobjectyes–
subArticlesarray––
textstring––
titlestring––
truncatedboolean––

No examples provided.

search_help_guides ~120

Searches the PlanElec guides about getting started, automatic planning, document exports, AREI self-check coverage, floor plan import, symbols and circuits in the visitor’s current language. Returns up to five guides with title, summary, category and a link to the full article; the article text itself is not returned.

NameTypeReqDescription
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
querystring–Keywords matched against title, summary and tags. Empty lists all guides.
NameTypeReqDescription
resultsarrayyes–
sourceobjectyes–

No examples provided.

search_regelwerk ~258

Searches Book 1 of the Belgian AREI/RGIE (Royal Decree on electrical installations) in the language of the text: Dutch, French or German; English uses the German text. Returns up to ten articles with number, title, an excerpt, the edition in force today and a link to the article in the PlanElec reader; the full article text is not returned, use get_regelwerk_article for it. Search by keywords or by article number such as 4.2.4.3. Results are planning aids, not an official inspection.

NameTypeReqDescription
limitinteger–Maximum number of articles, 1–10. Default: 5.
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
querystringyesKeywords or an article number such as 5.2.2.1 or 4.2.4.3, 2–120 characters.
versionstring–Optional edition, e.g. v06 or v07. Default: the edition in force today (v06 until 31/10/2026, v07 from 01/11/2026).
NameTypeReqDescription
editionobject––
resultsarrayyes–
sourceobjectyes–

No examples provided.

size_cable_arei ~389

Calculates the required copper or aluminium cable cross-section for a residential circuit under the Belgian AREI/RGIE: design current, voltage drop per cross-section, protection check against the breaker rating and the recommended cross-section. Provide the load (A, W, kW or kVA), one-way cable length in metres, the network (1x230V, 3x230V, 3x400V) and the breaker rating; other fields use the defaults for a typical socket circuit. The response includes a shareable link that opens the same calculation on planelec.be.

NameTypeReqDescription
breakerAmpsnumber–Circuit-breaker rating in A. Default: 16.
circuitKindstring–‘lighting’ applies the 3% voltage-drop limit, ‘other’ 5%.
circuitPhasesstring–Circuit type; three-phase requires a 3x network.
cosPhinumber–Power factor 0–1. Default: 0.95.
lengthMnumber–One-way cable length in metres. Default: 30.
loadUnitstring–Unit of loadValue. Default: A.
loadValuenumber–Load magnitude in loadUnit. Default: 16.
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
materialstring–Conductor material. Default: CU.
modestring–‘plan’ recommends a cross-section; ‘check’ evaluates selectedCrossSectionMm2.
networkstring–Supply network. Default: 1x230V.
nominalVoltagenumber–Optional override of the nominal voltage (≤ 1000 V).
selectedCrossSectionMm2number–Cross-section to evaluate in ‘check’ mode.
NameTypeReqDescription
activePowerWnumberyes–
comparisonarrayyes–
currentAmpsnumberyes–
inputobjectyes–
maxVoltageDropPercentnumberyes–
nextStepsarrayyes–
nominalVoltagenumberyes–
overallStatusstringyes–
sourceobjectyes–

No examples provided.

suggest_inverter_c10_26 ~116

Typeahead for the Synergrid C10/26 list: given a partial brand or model name, returns matching brands with device counts or, once a brand is recognised, its homologated models. Use this to resolve an ambiguous device name before calling check_inverter_c10_26.

NameTypeReqDescription
localestring–Language of source titles and links (nl, fr, de, en). Defaults to the server setting.
querystringyesPartial brand or model name, 1–80 characters.
NameTypeReqDescription
brandsarrayyes–
matchedBrandstring|nullyes–
modelsarrayyes–
sourceobjectyes–

No examples provided.

Install

How do I install the PlanElec Calculators MCP server?

PlanElec Calculators is a hosted endpoint at https://planelec.be/mcp/public, 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 · planelec.be

# add to Claude Code
claude mcp add --transport http be-planelec-calculators 'https://planelec.be/mcp/public'
Common questions

What is the PlanElec Calculators MCP server?

PlanElec Calculators is an MCP server listed in the public MCP registry as be.planelec/calculators. Free AREI cable sizing, Synergrid C10/26 inverter check, LED strip calculator. No account. This page covers its hosted endpoint (https://planelec.be/mcp/public).

Is the PlanElec Calculators MCP server safe to use?

PlanElec Calculators scores 78 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 PlanElec Calculators MCP server expose?

PlanElec Calculators exposes 8 tools: check_inverter_c10_26, suggest_inverter_c10_26, get_inverter_datasheet, size_cable_arei, calculate_led_strip, and 3 more. Their descriptions and schemas cost roughly 2,107 tokens of context every time the server is loaded.

Does the PlanElec Calculators MCP server require authentication?

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

Is the PlanElec Calculators MCP server still maintained?

PlanElec Calculators 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 PlanElec Calculators MCP server?

VerifyMCP ran 13 checks on PlanElec Calculators, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.