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.

Jithox EU Energy Label Preflight

REMOTE · ENERGY.MCP.JITHOX.COM

Read-only EU energy-label preflight: supplier-declared EPREL records. Evidence, not advice.

−35 this week 52 Trust /100

Last scanned (12 hours ago)

Scores higher than 42% of remote servers

Unreachable for 4 days in a row. Last reached 1 Nov 2026.

Category Health and Science

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 5 Nov 26 −18

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 4 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 2 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 30 Sept 26 0
    • Server version: 0.3.0 → 0.3.1 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://energy.mcp.jithox.com/mcp

TLS unreached
DNSSEC insecure

Validation of energy.mcp.jithox.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jithox.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://energy.mcp.jithox.com/mcp Unreachable
http (plaintext) http://energy.mcp.jithox.com/mcp HTTPS enforced
MCP tools · 5 exposed · ~844 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
compare_eprel_product_metrics ~159

Compare two or more COMPATIBLE records on their COMMON supplier-declared metrics — a value table only. Cross-product-group comparison fails safely as 'incompatible_comparison'; no 'best product', no ranking, no buying advice. Answers come from the queried source at the stated retrieval time: the official EPREL Public API in live mode, or a clearly-labelled synthetic fixture in dev/test — provenance.sourceAuthority names which. Supplier-declared data only; Jithox verifies nothing.

NameTypeReqDescription
metricKeysarray–Optional metric keys to restrict the comparison to.
publicRecordIdsarray–Public record identifiers to compare; a comparison needs at least 2 (fewer returns 'insufficient_identifiers'), up to 5.
NameTypeReqDescription
billingobjectyes–
capability–yes–
dataobjectyes–
decisionstringyes–
decisionCategorystringyes–
generatedAtstringyes–
limitationsarrayyes–
product–yes–
provenanceobjectyes–
receipt–yes–
receiptEnvelopeobject––
retryablebooleanyes–
schemaVersion–yes–

No examples provided.

get_eprel_energy_label_data ~127

Structure the supplier-DECLARED energy-label / product-sheet data for one public record. The result states supplierDeclared=true and independentlyVerifiedByJithox=false explicitly — nothing is independently verified. Answers come from the queried source at the stated retrieval time: the official EPREL Public API in live mode, or a clearly-labelled synthetic fixture in dev/test — provenance.sourceAuthority names which. Preflight evidence only — never a conformity, CE, GPSR, safety or market-access determination.

NameTypeReqDescription
publicRecordIdstring–The public record identifier whose declared label data to return.
NameTypeReqDescription
billingobjectyes–
capability–yes–
dataobjectyes–
decisionstringyes–
decisionCategorystringyes–
generatedAtstringyes–
limitationsarrayyes–
product–yes–
provenanceobjectyes–
receipt–yes–
receiptEnvelopeobject––
retryablebooleanyes–
schemaVersion–yes–

No examples provided.

get_eprel_product_record ~151

Structure ONE public record by its public record identifier: declared supplier/brand, product group, declared public fields, documents, missing fields, provenance and freshness. 'exact_public_record' / 'no_match_in_queried_source' / 'unavailable'. Answers come from the queried source at the stated retrieval time: the official EPREL Public API in live mode, or a clearly-labelled synthetic fixture in dev/test — provenance.sourceAuthority names which. Supplier-declared data only; Jithox verifies nothing. Preflight evidence only — never a conformity, CE, GPSR, safety or market-access determination.

NameTypeReqDescription
publicRecordIdstring–The public record identifier (from a prior search candidate).
NameTypeReqDescription
billingobjectyes–
capability–yes–
dataobjectyes–
decisionstringyes–
decisionCategorystringyes–
generatedAtstringyes–
limitationsarrayyes–
product–yes–
provenanceobjectyes–
receipt–yes–
receiptEnvelopeobject––
retryablebooleanyes–
schemaVersion–yes–

No examples provided.

prepare_energy_label_preflight_receipt ~137

Bundle the preflight lookups into one idempotent Ed25519-signed receipt committing to the FINGERPRINTED inputs, record references, sources, freshness and decision states — provable evidence of WHAT was looked up and WHEN. Attests the lookups, never a registration, conformity or market-access outcome. Preflight evidence only — never a conformity, CE, GPSR, safety or market-access determination.

NameTypeReqDescription
bundleobjectyesThe preflight results to attest (fingerprinted inputs, sources, decision states — no raw query values).
createdAtstringyesISO timestamp the bundle was assembled.
NameTypeReqDescription
billingobjectyes–
capability–yes–
dataobjectyes–
decisionstringyes–
decisionCategorystringyes–
generatedAtstringyes–
limitationsarrayyes–
product–yes–
provenanceobjectyes–
receipt–yes–
receiptEnvelopeobject––
retryablebooleanyes–
schemaVersion–yes–

No examples provided.

search_eprel_products ~270

Search the queried source by model identifier, registration number, or supplier/brand + product group. Returns CANDIDATE public records with deterministic match kinds and visible ambiguity: 'exact_public_record' / 'possible_match' / 'multiple_matches' / 'no_match_in_queried_source' — a no-match is never 'not registered'. Outage → 'unavailable'; unverified schema → 'source_schema_unverified'; stale → 'stale'. Answers come from the queried source at the stated retrieval time: the official EPREL Public API in live mode, or a clearly-labelled synthetic fixture in dev/test — provenance.sourceAuthority names which. Supplier-declared data only; Jithox verifies nothing. Preflight evidence only — never a conformity, CE, GPSR, safety or market-access determination.

NameTypeReqDescription
modelIdentifierstring–The supplier's model identifier to search for.
productGroupstring–Product group to narrow the search (must be covered by the queried source). The official live source searches ONE group at a time: text searches (model/brand) REQUIRE it; registration-number lookups…
registrationNumberstring–A public registration number, when known.
supplierOrBrandstring–Supplier or trade brand to narrow the search.
NameTypeReqDescription
billingobjectyes–
capability–yes–
dataobjectyes–
decisionstringyes–
decisionCategorystringyes–
generatedAtstringyes–
limitationsarrayyes–
product–yes–
provenanceobjectyes–
receipt–yes–
receiptEnvelopeobject––
retryablebooleanyes–
schemaVersion–yes–

No examples provided.

Install

How do I install the Jithox EU Energy Label Preflight MCP server?

Jithox EU Energy Label Preflight is a hosted endpoint at https://energy.mcp.jithox.com/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 · energy.mcp.jithox.com

# add to Claude Code
claude mcp add --transport http com-jithox-eu-energy-label-preflight 'https://energy.mcp.jithox.com/mcp'
Common questions

What is the Jithox EU Energy Label Preflight MCP server?

Jithox EU Energy Label Preflight is an MCP server listed in the public MCP registry as com.jithox/eu-energy-label-preflight. Read-only EU energy-label preflight: supplier-declared EPREL records. Evidence, not advice. This page covers its hosted endpoint (https://energy.mcp.jithox.com/mcp).

Is the Jithox EU Energy Label Preflight MCP server safe to use?

Jithox EU Energy Label Preflight scores 52 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 Jithox EU Energy Label Preflight MCP server expose?

Jithox EU Energy Label Preflight exposes 5 tools: search_eprel_products, get_eprel_product_record, get_eprel_energy_label_data, compare_eprel_product_metrics, prepare_energy_label_preflight_receipt. Their descriptions and schemas cost roughly 844 tokens of context every time the server is loaded.

Does the Jithox EU Energy Label Preflight MCP server require authentication?

Its publisher declares that Jithox EU Energy Label Preflight requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the Jithox EU Energy Label Preflight MCP server still maintained?

Jithox EU Energy Label Preflight is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.