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.

AI LedParser

REMOTE · LEDPARSER.WIN

LED selection by package, CCT and current: flux, lm/W, price per lumen from datasheet curves.

Available components

72 Trust /100

Last scanned (18 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category IoT and Hardware

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 Security80
  • 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
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 901 tokens (~450/item across 2 items; 2 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
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 +3
    • HSTS header: fail → pass ▲ security
  • 18 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.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 68

    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://ledparser.win/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ledparser.win CN=YE2,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA384 67ad3f5833bb8ec5933c87272f5dd05cf77
SANs: ledparser.win
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ledparser.win. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
win. DS published 29737 8 Verified
ledparser.win. 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
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'self' https://webvisor.com https://*.webvisor.com https://metrika.yandex.ru https://*.metrika.yandex.ru https://metrika.yandex.by https://*.metrika.yandex.by https://metrika.yandex.com https://*.metrika.yandex.com https://metrika.yandex.com.tr https://*.metrika.yandex.com.tr https://metrica.yandex.ru https://*.metrica.yandex.ru https://metrica.yandex.by https://*.metrica.yandex.by https://metrica.yandex.com https://*.metrica.yandex.com https://metrica.yandex.com.tr https://*.metrica.yandex.com.tr
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ledparser.win/api/mcp Verified 200
http (plaintext) http://ledparser.win/api/mcp HTTPS enforced 308 https://ledparser.win/api/mcp
MCP tools · 2 exposed · ~680 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
led_catalog_search ~266

Price list without calculation: catalog search without current; package and CCT are required, plus part number, voltage, CRI, quantity, availability, and price. Without availability — stock and on order only; availability.source=all — all items without quantity filtering. The response has no flux or lm/W — use led_select with an operating current for those. Show the result as the table from the response `table` field — it is the same as on the site. Pass hidden_message to the user; do not promise an order.

NameTypeReqDescription
availabilityobject–availability { source, min_quantity }: stock — stock only, stock-and-order — stock and on order, all — all items without quantity filtering. Field omitted — stock and on order, minimum 1; when a part…
color_tempstringyesCCT
criinteger–color rendering index
markingstring–part number or model
min_quantityinteger–quantity specified by the user; 0 if not specified
package_sizestringyesLED package
priceobject–maximum price per unit
voltagenumber–voltage

No output schema declared.

No examples provided.

led_select ~414

Calculation-based LED selection by package, CCT, and operating current. If there is no current, call led_catalog_search (price list without calculation) or ask for the current. Default: 5 items, maximum 10 — if the user asks for more, call with limit 10. Without availability — stock and on order only; availability.source=all — all items. Without sort — lowest cost per lumen; with thresholds.target_flux the sort is always flux-distance-asc, and flux-distance-asc without it is rejected as sort-invalid. Show the result as the table from the response `table` field — it is the same as on the site. Pass hidden_message to the user; do not promise an order.

NameTypeReqDescription
availabilityobject–availability { source, min_quantity }: stock — stock only, stock-and-order — stock and on order, all — all items without quantity filtering. Field omitted — stock and on order, minimum 1; when a part…
catalogobjectyesprice list conditions: package, CCT, and optional refinements
currentnumberyesoperating current in mA
limitinteger–how many items to return
priceobject–maximum price per unit
sortstring–result sorting: price-per-lumen-usd-asc — lowest cost per lumen (USD/lm), price-usd-asc — lowest price per unit (USD), price-cny-asc — lowest price per unit (CNY), efficacy-desc — highest efficacy, f…
temperaturenumber|null–solder-point temperature in °C; degrees without qualification mean this temperature
thresholdsobject–flux and efficacy thresholds

No output schema declared.

No examples provided.

Install

How do I install the AI LedParser MCP server?

AI LedParser is a hosted endpoint at https://ledparser.win/api/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 · ledparser.win

# add to Claude Code
claude mcp add --transport http win-ledparser-ledparser 'https://ledparser.win/api/mcp'
Common questions

What is the AI LedParser MCP server?

AI LedParser is an MCP server listed in the public MCP registry as win.ledparser/ledparser. LED selection by package, CCT and current: flux, lm/W, price per lumen from datasheet curves. This page covers its hosted endpoint (https://ledparser.win/api/mcp).

Is the AI LedParser MCP server safe to use?

AI LedParser scores 72 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 AI LedParser MCP server expose?

AI LedParser exposes 2 tools: led_select, led_catalog_search. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.

Does the AI LedParser MCP server require authentication?

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

Is the AI LedParser MCP server still maintained?

AI LedParser 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 AI LedParser MCP server?

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