Jithox EU Energy Label Preflight
com.jithox/eu-energy-label-preflight · 0.3.1
Read-only EU energy-label preflight: supplier-declared EPREL records. Evidence, not advice.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://energy.mcp.jithox.com/mcpstreamable-httpAuthorizationrequired, secret: OAuth 2.1 bearer. Discover the authorization server via /.well-known/oauth-protected-resource; PKCE S256 is mandatory; tokens are audience-bound to https://energy.mcp.jithox.com/mcp with least-privile
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- com.jithox/eu-energy-label-preflight 0.3.1
- Handshake time
- 372 ms
- HTTP status
- 200
The tools it lists (5, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_eprel_productsSearch 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.sourceAuthor
get_eprel_product_recordStructure 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
get_eprel_energy_label_dataStructure 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.
compare_eprel_product_metricsCompare 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.jithox/eu-energy-label-preflight, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 14 days ago. The registry entry · energy.mcp.jithox.com