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.

io.github.CloudCorpRecords/labelproof

NPM · @RENETURCIOS/LABELPROOF · 2 COMPONENTS

Read-only EU energy-label preflight checks against supplier-declared EPREL records.

0 this week 69 Trust /100

Last scanned (20 hours ago)

Scores higher than 39% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 844 tokens (~168/item across 5 items; 5 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 54

    First indexed and scored.

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 · Analysed npm/@reneturcios/labelproof@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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.

No output schema declared.

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.

No output schema declared.

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).

No output schema declared.

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.

No output schema declared.

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.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/labelproof MCP server?

io.github.CloudCorpRecords/labelproof runs locally as an npm package, launched with npx -y @reneturcios/labelproof mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/labelproof

# add to Claude Code
claude mcp add cloudcorprecords-labelproof -- npx -y @reneturcios/labelproof mcp
Common questions

What is the io.github.CloudCorpRecords/labelproof MCP server?

io.github.CloudCorpRecords/labelproof is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/labelproof. Read-only EU energy-label preflight checks against supplier-declared EPREL records. This page covers its npm package (@reneturcios/labelproof).

Is the io.github.CloudCorpRecords/labelproof MCP server safe to use?

io.github.CloudCorpRecords/labelproof scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/labelproof MCP server expose?

io.github.CloudCorpRecords/labelproof 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.

Is the io.github.CloudCorpRecords/labelproof MCP server still maintained?

io.github.CloudCorpRecords/labelproof 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 licence is the io.github.CloudCorpRecords/labelproof MCP server under?

io.github.CloudCorpRecords/labelproof declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/labelproof MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/labelproof, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/labelproof: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.