# AI LedParser (remote · ledparser.win)

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

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ledparser.win`: 72/100 (this document), [markdown](https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp.md), [page](https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp)

## Channel facts

- Endpoint: `https://ledparser.win/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http win-ledparser-ledparser 'https://ledparser.win/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "win-ledparser-ledparser": {
      "url": "https://ledparser.win/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "win-ledparser-ledparser": {
      "type": "http",
      "url": "https://ledparser.win/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.win-ledparser-ledparser]
url = "https://ledparser.win/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "win-ledparser-ledparser": {
      "type": "remote",
      "url": "https://ledparser.win/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add win-ledparser-ledparser --url 'https://ledparser.win/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  win-ledparser-ledparser:
    url: "https://ledparser.win/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "win-ledparser-ledparser": {
      "Transport": "http",
      "Url": "https://ledparser.win/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add win-ledparser-ledparser -t streamable-http -u 'https://ledparser.win/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "win-ledparser-ledparser": {
      "type": "http",
      "url": "https://ledparser.win/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 72, +3)

- [security improvement] HSTS header: fail → pass

### 2026-11-18 (score 69, +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.

### 2026-11-17 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 68)

First indexed and scored.

## MCP tools (2)

### `led_select` (~414 tokens)

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.

Input parameters:

- `availability` (object): 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…
- `catalog` (object, required): price list conditions: package, CCT, and optional refinements
- `current` (number, required): operating current in mA
- `limit` (integer): how many items to return
- `price` (object): maximum price per unit
- `sort` (string): 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…
- `temperature` (number|null): solder-point temperature in °C; degrees without qualification mean this temperature
- `thresholds` (object): flux and efficacy thresholds

### `led_catalog_search` (~266 tokens)

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.

Input parameters:

- `availability` (object): 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_temp` (string, required): CCT
- `cri` (integer): color rendering index
- `marking` (string): part number or model
- `min_quantity` (integer): quantity specified by the user; 0 if not specified
- `package_size` (string, required): LED package
- `price` (object): maximum price per unit
- `voltage` (number): voltage

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68

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

## Links

- Remote endpoint: https://ledparser.win/api/mcp
- Website: https://ledparser.win/ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/win-ledparser-ledparser/api-mcp
