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.

repairinfo

REMOTE · WWW.REPAIRINFO.APP

Repairability and durability data for EU devices from the official EPREL register

69 Trust /100

Last scanned (14 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 559 tokens (~139/item across 4 items; 4 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 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.

  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 67

    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 · Probed https://www.repairinfo.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.repairinfo.app CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 6b49d735651ba6100e1146e556632b23
SANs: www.repairinfo.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.repairinfo.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
repairinfo.app. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.repairinfo.app/mcp Verified 200
http (plaintext) http://www.repairinfo.app/mcp HTTPS enforced 301 https://www.repairinfo.app/mcp
MCP tools · 4 exposed · ~391 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
get_device ~118

All data for one device: score and what it is based on, repairability class and index, guaranteed software update years and the year updates last until at least, user-replaceable battery, battery life, charge cycles, spare-part years, energy class, EPREL registration number, official recalls or safety warnings (EU Safety Gate, RappelConso) if any, and the link to the device page.

NameTypeReqDescription
idstringyesDevice id from search_devices or top_devices, e.g. smartphones/gigaset-gs6-pro

No output schema declared.

No examples provided.

lookup_barcode ~69

Find a device by its EAN/GTIN barcode (8 to 14 digits), as printed on the box or shelf label. Returns the same data as get_device.

NameTypeReqDescription
eanstringyesEAN-8, UPC-A, EAN-13 or GTIN-14

No output schema declared.

No examples provided.

search_devices ~101

Search smartphones, tablets, laptops, TVs, washing machines, dishwashers and vacuum cleaners by brand, sales name or model number. Returns repairability and durability score, EU repairability class, guaranteed update years and the link to the device page.

NameTypeReqDescription
categorystring––
limitinteger––
querystringyesBrand, sales name or model number, e.g. "Galaxy S26" or "SM-S942B"

No output schema declared.

No examples provided.

top_devices ~103

The most repairable and durable devices of a category, sorted by score. Optional filters: minimum guaranteed update years, user-replaceable battery, brand. Use this for questions like "which phone gets updates the longest" or "which tablets have a replaceable battery".

NameTypeReqDescription
brandstring––
categorystringyes–
limitinteger––
min_update_yearsinteger––
replaceable_batteryboolean––

No output schema declared.

No examples provided.

Install

How do I install the repairinfo MCP server?

repairinfo is a hosted endpoint at https://www.repairinfo.app/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 · www.repairinfo.app

# add to Claude Code
claude mcp add --transport http app-repairinfo-repairinfo 'https://www.repairinfo.app/mcp'
Common questions

What is the repairinfo MCP server?

repairinfo is an MCP server listed in the public MCP registry as app.repairinfo/repairinfo. Repairability and durability data for EU devices from the official EPREL register. This page covers its hosted endpoint (https://www.repairinfo.app/mcp).

Is the repairinfo MCP server safe to use?

repairinfo scores 69 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 repairinfo MCP server expose?

repairinfo exposes 4 tools: search_devices, get_device, top_devices, lookup_barcode. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.

Does the repairinfo MCP server require authentication?

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

Is the repairinfo MCP server still maintained?

repairinfo 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 repairinfo MCP server?

VerifyMCP ran 13 checks on repairinfo, 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.