Skip to content

MCP servers › nl.enfy › energievergelijker

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

energievergelijker MCP server

Registry name nl.enfy/energievergelijker

enfy.nl energievergelijker (Nederland) — the publisher's title

by enfy.nl · domain (the registry's namespace rule)repository owner on GitHub: kaprudy (personal account)Source ↗Website ↗

Compare all Dutch electricity and gas contracts, dynamic prices, grid costs and energy tax (Dutch). — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-19version 1.6.6streamable HTTP12 tools

Summary

nl.enfy/energievergelijker is a remote MCP server listed in the official MCP registry at version 1.6.6, under the namespace of the domain enfy.nl. Its linked repository is github.com/kaprudy/enfy-mcp; GitHub reports its owner as kaprudy, a personal account. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 12 tools, 1 resource and 1 prompt.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
12
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (enfy.nl), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.6.6).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.6.6, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-18 (earliest version still in the registry; older removed versions would be earlier)
Version history
7 versions listed, 2026-11-18 to 2026-11-19; 7 in the 90 days before the 2026-11-19 snapshot.
Most recent 7 versions
  • 1.6.6 · 2026-11-19
  • 1.6.4 · 2026-11-18
  • 1.6.3 · 2026-11-18
  • 1.6.2 · 2026-11-18
  • 1.6.1 · 2026-11-18
  • 1.6.0 · 2026-11-18
  • 1.5.0 · 2026-11-18
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-18, listed on 2026-11-19 with version 1.6.6 (published 2026-11-19).

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19.

What it is

What does this server offer?

Observed inventory
12tools
1resources
1prompts

None of its 12 tools are described as changing anything. For 12 the reading was uncertain, so no mark is shown.

  • vergelijk_energie

    “Berekent de goedkoopste stroom- en gascontracten van alle Nederlandse leveranciers voor een huishouden: maandbedrag en kosten eerste jaar (incl.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    26 inputs
    • kwhinteger“Stroomverbruik per jaar in kWh (enkeltarief of totaal).”
    • kwh_normaalinteger“Verbruik normaaltarief per jaar in kWh (samen met kwh_dal; staat op de jaarnota).”
    • kwh_dalinteger“Verbruik daltarief per jaar in kWh.”
    • m3integer“Gasverbruik per jaar in m³.”
    • geen_gasboolean“true als het huis geen gasaansluiting heeft.”
    • terugleveringinteger“Teruglevering aan het net per jaar in kWh (zonnepanelen), van de jaarnota.”
    • zonnepanelen_wpinteger“Alleen als de teruglevering niet bekend is: vermogen van alle zonnepanelen samen in wattpiek (Wp), bijv.”
    • aantal_paneleninteger“Of: aantal zonnepanelen (samen met wp_per_paneel), in plaats van zonnepanelen_wp.”
    • wp_per_paneelinteger“Vermogen per paneel in Wp (staat op de factuur of het typeplaatje); zonder: het paneel waarmee Milieu Centraal rekent.”
    • aansluitingstring“Aansluitwaarde van de stroomaansluiting (staat op de jaarnota of de hoofdschakelaar).”
    • netbeheerderstring“Netbeheerder voor stroom (en voor gas als netbeheerder_gas ontbreekt).”
    • netbeheerder_gasstring“Netbeheerder voor gas als die anders is dan voor stroom (bijv.”
    • postcodestring“Alleen de 4 cijfers van de postcode, bijv.”
    • ingangstring“Ingangsdatum van het nieuwe contract (jjjj-mm-dd, vandaag tot over 12 maanden).”
    • autoboolean“true als er thuis een elektrische auto laadt.”
    • auto_kminteger“Kilometers per jaar met de elektrische auto (standaard 15000).”
    • auto_verbruiknumber“Verbruik van de auto in kWh per 100 km (standaard 18).”
    • auto_kwhinteger“Of direct: laadstroom van de auto per jaar in kWh (gaat voor auto_km × auto_verbruik).”
    • slim_ladenboolean“true als de auto slim laadt: automatisch in de goedkoopste uren (dynamisch: elke nacht tussen 21:00 en 07:00; dubbele meter: 95% dal in plaats van 80%).”
    • auto_1faseboolean“true bij een laadpaal op 1 fase (3,7 kW in plaats van 11 kW); telt bij slim laden met een dynamisch contract.”
    • contractstring“Alleen deze contractvorm.”
    • looptijdinteger“Alleen vaste contracten met deze looptijd in jaren.”
    • groenboolean“Alleen groene stroom (Nederland, Europa of land niet vermeld; "herkomst onbekend" telt niet als groen).”
    • groen_nlboolean“Alleen groene stroom uit Nederland (Garanties van Oorsprong uit Nederland, volgens de leverancier).”
    • aantalinteger“Aantal aanbiedingen per groep (standaard 3).”

    and 1 more not listed here.

  • eigen_contract_vergelijken

    “Rekent uit wat je huidige energiecontract per jaar kost met de tarieven van je jaarnota of contract en zet dat naast de goedkoopste aanbiedingen voor hetzelfde verbruik: wat je met overstappen per ja…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    39 inputs
    • kwhinteger“Stroomverbruik per jaar in kWh (enkeltarief of totaal).”
    • kwh_normaalinteger“Verbruik normaaltarief per jaar in kWh (samen met kwh_dal; staat op de jaarnota).”
    • kwh_dalinteger“Verbruik daltarief per jaar in kWh.”
    • m3integer“Gasverbruik per jaar in m³.”
    • geen_gasboolean“true als het huis geen gasaansluiting heeft.”
    • terugleveringinteger“Teruglevering aan het net per jaar in kWh (zonnepanelen), van de jaarnota.”
    • zonnepanelen_wpinteger“Alleen als de teruglevering niet bekend is: vermogen van alle zonnepanelen samen in wattpiek (Wp), bijv.”
    • aantal_paneleninteger“Of: aantal zonnepanelen (samen met wp_per_paneel), in plaats van zonnepanelen_wp.”
    • wp_per_paneelinteger“Vermogen per paneel in Wp (staat op de factuur of het typeplaatje); zonder: het paneel waarmee Milieu Centraal rekent.”
    • aansluitingstring“Aansluitwaarde van de stroomaansluiting (staat op de jaarnota of de hoofdschakelaar).”
    • netbeheerderstring“Netbeheerder voor stroom (en voor gas als netbeheerder_gas ontbreekt).”
    • netbeheerder_gasstring“Netbeheerder voor gas als die anders is dan voor stroom (bijv.”
    • postcodestring“Alleen de 4 cijfers van de postcode, bijv.”
    • ingangstring“Ingangsdatum van het nieuwe contract (jjjj-mm-dd, vandaag tot over 12 maanden).”
    • autoboolean“true als er thuis een elektrische auto laadt.”
    • auto_kminteger“Kilometers per jaar met de elektrische auto (standaard 15000).”
    • auto_verbruiknumber“Verbruik van de auto in kWh per 100 km (standaard 18).”
    • auto_kwhinteger“Of direct: laadstroom van de auto per jaar in kWh (gaat voor auto_km × auto_verbruik).”
    • slim_ladenboolean“true als de auto slim laadt: automatisch in de goedkoopste uren (dynamisch: elke nacht tussen 21:00 en 07:00; dubbele meter: 95% dal in plaats van 80%).”
    • auto_1faseboolean“true bij een laadpaal op 1 fase (3,7 kW in plaats van 11 kW); telt bij slim laden met een dynamisch contract.”
    • stroomprijsnumber“Verplicht (of stroomprijs_normaal + stroomprijs_dal, of bij dynamisch inkoopvergoeding_stroom): leveringsprijs stroom per kWh in euro (enkeltarief), bijv.”
    • stroomprijs_normaalnumber“Leveringsprijs stroom normaaltarief per kWh in euro; samen met stroomprijs_dal, in plaats van stroomprijs.”
    • stroomprijs_dalnumber“Leveringsprijs stroom daltarief per kWh in euro; samen met stroomprijs_normaal.”
    • gasprijsnumber“Verplicht als er gas is (tenzij geen_gas of bij dynamisch gas inkoopvergoeding_gas): leveringsprijs gas per m³ in euro, bijv.”
    • vaste_kosten_stroomnumber“Verplicht (of vaste_kosten): vaste leveringskosten (vastrecht) van de leverancier voor stroom, euro per maand.”

    and 14 more not listed here.

  • dynamisch_of_vast

    “Zet voor een huishouden het goedkoopste vaste 1-jaarscontract, het goedkoopste variabele en het goedkoopste dynamische contract naast elkaar (dynamisch als schatting met bandbreedte), en rekent hetze…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    20 inputs
    • kwhinteger“Stroomverbruik per jaar in kWh (enkeltarief of totaal).”
    • kwh_normaalinteger“Verbruik normaaltarief per jaar in kWh (samen met kwh_dal; staat op de jaarnota).”
    • kwh_dalinteger“Verbruik daltarief per jaar in kWh.”
    • m3integer“Gasverbruik per jaar in m³.”
    • geen_gasboolean“true als het huis geen gasaansluiting heeft.”
    • terugleveringinteger“Teruglevering aan het net per jaar in kWh (zonnepanelen), van de jaarnota.”
    • zonnepanelen_wpinteger“Alleen als de teruglevering niet bekend is: vermogen van alle zonnepanelen samen in wattpiek (Wp), bijv.”
    • aantal_paneleninteger“Of: aantal zonnepanelen (samen met wp_per_paneel), in plaats van zonnepanelen_wp.”
    • wp_per_paneelinteger“Vermogen per paneel in Wp (staat op de factuur of het typeplaatje); zonder: het paneel waarmee Milieu Centraal rekent.”
    • aansluitingstring“Aansluitwaarde van de stroomaansluiting (staat op de jaarnota of de hoofdschakelaar).”
    • netbeheerderstring“Netbeheerder voor stroom (en voor gas als netbeheerder_gas ontbreekt).”
    • netbeheerder_gasstring“Netbeheerder voor gas als die anders is dan voor stroom (bijv.”
    • postcodestring“Alleen de 4 cijfers van de postcode, bijv.”
    • ingangstring“Ingangsdatum van het nieuwe contract (jjjj-mm-dd, vandaag tot over 12 maanden).”
    • autoboolean“true als er thuis een elektrische auto laadt.”
    • auto_kminteger“Kilometers per jaar met de elektrische auto (standaard 15000).”
    • auto_verbruiknumber“Verbruik van de auto in kWh per 100 km (standaard 18).”
    • auto_kwhinteger“Of direct: laadstroom van de auto per jaar in kWh (gaat voor auto_km × auto_verbruik).”
    • slim_ladenboolean“true als de auto slim laadt: automatisch in de goedkoopste uren (dynamisch: elke nacht tussen 21:00 en 07:00; dubbele meter: 95% dal in plaats van 80%).”
    • auto_1faseboolean“true bij een laadpaal op 1 fase (3,7 kW in plaats van 11 kW); telt bij slim laden met een dynamisch contract.”
  • thuisbatterij_berekenen

    “Rekent uit of een thuisbatterij loont voor een huishouden, per uur over de afgelopen 12 maanden (weer van het KNMI, beursprijzen bij dynamisch) met de regels van 2027 (geen salderen): ons advies (Int…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    11 inputs
    • contractstring“Energiecontract: vast, variabel of dynamisch (beursprijs per uur; dan laadt een slimme batterij ook in goedkope uren).”
    • zonnepanelen_wpinteger“Vermogen van alle zonnepanelen samen in wattpiek (Wp), bijv.”
    • aantal_paneleninteger“Of: aantal zonnepanelen (samen met wp_per_paneel), in plaats van zonnepanelen_wp.”
    • wp_per_paneelinteger“Vermogen per paneel in Wp (factuur of typeplaatje); zonder: het paneel waarmee Milieu Centraal rekent.”
    • kwh_per_dagnumber“Totaal eigen stroomverbruik per dag in kWh, inclusief de zonnestroom die je direct zelf gebruikt (jaarverbruik ÷ 365).”
    • kwh_per_jaarinteger“Of: totaal eigen stroomverbruik per jaar in kWh (wordt omgerekend naar kWh per dag).”
    • batterij_kwhnumber“Bruikbare opslag van de batterij die je wilt bekijken, in kWh (bijv.”
    • huidige_batterij_kwhnumber“Heb je al een thuisbatterij: de bruikbare opslag in kWh.”
    • installatiestring“Wat voor batterij: advies (standaard; ook als je niets opgeeft: we rekenen een vaste thuisbatterij, een stekkerbatterij en losse componenten door en adviseren …”
    • zelf_aansluitenboolean“Oud: true = installatie stekker (stekkerbatterij).”
    • slim_aansturenarray“Apparaten die je al op een zonnig (vast/variabel) of goedkoop (dynamisch) moment aanzet, bijv.”
  • netbeheerder

    “Zoekt bij de 4 cijfers van een postcode de netbeheerder voor stroom en gas (Liander, Stedin, Enexis, Westland Infra, Coteq of RENDO) en geeft de netbeheerkosten per jaar en per maand, dit jaar en vol…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    6 inputs
    • postcodestring“De 4 cijfers van de postcode, bijv.”
    • netbeheerderstring“In plaats van postcode: de netbeheerder (voor stroom, en voor gas als netbeheerder_gas ontbreekt).”
    • netbeheerder_gasstring“Netbeheerder voor gas als die anders is dan voor stroom.”
    • aansluitingstring“Aansluitwaarde van de stroomaansluiting.”
    • m3integer“Gasverbruik per jaar in m³; bepaalt de gascategorie (t/m 500, 500–4.000, meer dan 4.000).”
    • geen_gasboolean“true als het huis geen gasaansluiting heeft.”
  • stroomprijs_vandaag

    “Dynamische stroomprijs (day-ahead, Nederland) per uur voor vandaag, morgen (na ±13:00) of een datum: kaal (beursprijs excl.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs
    • datumstring“"vandaag" (standaard), "morgen", "gisteren" of JJJJ-MM-DD.”
    • leverancierstring“Slug van een dynamische leverancier (bijv.”
  • gasprijs_vandaag

    “Dynamische gasprijs in Nederland per gasdag (06:00 tot 06:00): kaal (marktprijs excl.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input
    • gasdagstring“JJJJ-MM-DD (de gasdag begint om 06:00), "gisteren", of leeg voor de meest recente gasdag.”
  • leverancier_tarieven

    “Actuele, gecontroleerde tarieven van één Nederlandse energieleverancier per contract (stroom, gas, vaste kosten, teruglevering 2026 en vanaf 2027, welkomstbonus), met de kosten voor een gemiddeld hui…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input, 1 required
    • leverancierstringrequired“Naam of slug van de leverancier, bijv.”
  • prijswijzigingen

    “Gecontroleerde tariefwijzigingen en nieuwe contracten van Nederlandse energieleveranciers, nieuwste ingangsdatum eerst: oud en nieuw tarief (incl.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • leverancierstring“Naam of slug van één leverancier, bijv.”
    • alleen_komendboolean“true: alleen wijzigingen met een ingangsdatum vandaag of later.”
    • aantalinteger“Aantal wijzigingen (standaard 10).”
  • prijshistorie

    “Hoe energieprijzen in Nederland zich ontwikkelden, per jaar en de laatste 13 maanden, met bronnen (CBS, Eurostat, wetgeving, ENTSO-E): onderwerp stroom (leveringsprijs per kWh, incl.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs, 1 required
    • onderwerpstringrequired“stroom, gas, energiebelasting of day-ahead.”
    • vanaf_jaarinteger“Alleen jaren vanaf dit jaar (de laatste 13 maanden blijven).”
  • energiebelasting

    “Energiebelasting op stroom (per kWh) en gas (per m³) in Nederland voor een jaar, per schijf excl.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input
    • jaarinteger“Jaar, standaard het huidige jaar.”
  • methode_en_dekking

    “Hoe de vergelijking werkt en hoe volledig en actueel de gegevens zijn: volgorde alleen op kosten (geen betaalde volgorde), hoe de welkomstbonus telt, wat wel en niet in de bedragen zit, privacy; hoev…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input
    • leverancierstring“Optioneel: naam of slug van een leverancier (bijv.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 113
Tools with a description
100% of 12
Typical description length
748 characters

The tool set

Counted from the listing

Tools
12
Size of the list
about 38,927 tokens for an agent to load (characters ÷ 4)
Naming
8 of 12 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 12 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-19 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://enfy.nl/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "energievergelijker": {
      "url": "https://enfy.nl/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "energievergelijker": {
      "type": "http",
      "url": "https://enfy.nl/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"energievergelijker","type":"http","url":"https://enfy.nl/mcp"}'
Claude Code
claude mcp add --transport http energievergelijker https://enfy.nl/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "energievergelijker": {
      "type": "streamableHttp",
      "url": "https://enfy.nl/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "energievergelijker": {
      "httpUrl": "https://enfy.nl/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.energievergelijker]
url = "https://enfy.nl/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "energievergelijker": {
      "url": "https://enfy.nl/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://enfy.nl/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint enfy.nl/mcpSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19
Repository github.com/kaprudy/enfy-mcpOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
nl.enfy
GitHub owner
a personal account (kaprudy)
Repository
github.com/kaprudy/enfy-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-19.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-19). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about nl.enfy/energievergelijker

Answered from the data above

Who publishes nl.enfy/energievergelijker?

The registry ties the namespace nl.enfy to the domain enfy.nl; only its owner can publish under it. Its linked repository is github.com/kaprudy/enfy-mcp; GitHub reports its owner as kaprudy, a personal account. These are facts from the registry and GitHub, not a rating.

Is nl.enfy/energievergelijker safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does nl.enfy/energievergelijker need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.

Has nl.enfy/energievergelijker been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does nl.enfy/energievergelijker publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of nl.enfy/energievergelijker?

In github.com/kaprudy/enfy-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,304 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 12 tools, 1 resource, 1 prompt.
  4. 6,349 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-11-19
MCP capability
prompts, resources, tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “nl.enfy/energievergelijker: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/nl.enfy/energievergelijker

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/nl.enfy/energievergelijker)](https://protocolprobe.com/mcp/servers/nl.enfy/energievergelijker)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology