Skip to content

MCP servers › io.github.descipar › wled-mcp

MCP server · registry snapshot 2026-11-13 · last checked 2026-11-13

wled-mcp MCP server

Registry name io.github.descipar/wled-mcp

WLED MCP (unofficial) — the publisher's title

by descipar · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗Website ↗

Unofficial MCP server for WLED LED controllers; not affiliated with the WLED project — the publisher's description

7 of 7 record checks metversion 0.4.0PythonApache-2.0standard input/output

Summary

io.github.descipar/wled-mcp is a local MCP server listed in the official MCP registry at version 0.4.0, under the namespace of the GitHub account descipar. Its linked repository, github.com/descipar/wled-mcp, belongs to the same GitHub account.

Record checks

7 of 7 record checks met · 1 does not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not checked: No known critical or high advisory in the package or its dependencies
  • #9,264 of 20,610 packages by monthly downloads, tied with 10 others
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
PyPI · listed version current
License
Apache-2.0
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.4.0, published 2026-11-13 (registry, as of the 2026-11-13 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-09 to 2026-11-13; 3 in the 90 days before the 2026-11-13 snapshot.
Most recent 3 versions
  • 0.4.0 · 2026-11-13
  • 0.3.0 · 2026-11-11
  • 0.2.0 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-13
Package and repository
checked 2026-11-13

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.3.0 (published 2026-11-11) → 0.4.0 (published 2026-11-13), between the registry lists of 2026-11-12 and 2026-11-13.

The publisher’s GitHub release note for v0.4.0, published 2026-11-13.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
The minor release that carries all work merged since 0.3.0: milestones M3 (layout preview), M4
(temporary signals), M5 (validation with locked controllers) and M6 (public distribution
and the bounded security review), plus the backlog and tooling changes listed below. M3, M4 and
M5 close without a release of their own
([DEC-032](docs/DECISIONS.md#dec-032--m3-closes-without-its-own-release),
[DEC-034](docs/DECISIONS.md#dec-034--m4-closes-without-its-own-release),
[DEC-036](docs/DECISIONS.md#dec-036--m5-closes-without-its-own-release)). A minor release under the
`0.x` policy ([versioning](docs/contract/versioning.md), DEC-020). The served tool list grows from
33 to 37 tools; the tool changes are additive and no tool or field was removed or renamed.
Four behaviors changed and carry migration notes below: the snapshot directory, the HTTP
protocol error bodies, the HTTP startup line and the definition-directory scan cap.

### Migration

- **Snapshot directory (#181).** A symlinked `<data_dir>/backups` is no longer followed; see the
  symlink entry under "Changed" below.
- **HTTP error bodies (#181).** Transport-level HTTP errors (status 400 and above, such as a
  malformed request) now carry a fixed message and no SDK text that could quote the request. The
  status, the JSON-RPC code and request ID and the server's own fixed messages are unchanged; a
  client that parsed the SDK's validation text of such an error sees "HTTP request rejected."
  instead. Successful responses are unchanged.
- **HTTP startup line (#181).** The stderr notice at startup is `listening on configured address
  path /mcp` and no longer names the host and port; a bind failure prints a fixed message with the
  OS error number. A script that waited for or parsed `listening on <host>:<port>` must match
  the new line.
- **Definition directories (#181).** A group, scene or zone directory with more files than the scan
  cap now refuses to store a new definition instead of using an incomplete count.

### Added

- Temporary light signals ([#28](https://github.com/descipar/wled-mcp/issues/28),
  [contract](docs/contract/signals.md)): `wled_start_signal` shows an RGB colour on chosen
  existing segments of one controller for 1 to 300 seconds and `wled_cancel_signal` ends it
  early; `wled_get_signal_status` reads the state. The server restores only the fields it changed
  (slot-0 colour, the Solid effect, and segment or master power it turned on), and only if they
  still hold the signal value; otherwise the result is `skipped_conflict` and nothing is
  overwritten. One signal per device, no queue, no scheduler, no preset touched. Timing is best
  effort and nothing is persisted: a crash or kill can leave a signal applied, an orderly
  shutdown makes one bounded restore attempt, and a write whose outcome is unknown is never
  replayed.
- Static layout preview ([#29](https://github.com/descipar/wled-mcp/issues/29),
  [contract](docs/contract/layout-preview.md)): the read-only `wled_preview_layout` returns a
  bounded, script-free SVG string (`data.svg`) of one device's observed 1D segment layout or of a
  proposed complete layout validated by the existing layout planner, with ranges (exclusive
  stops), a scale, gaps, overlaps and approximate colours, optional zone bands and optional live
  colour samples. It sends no write, never simulates effects, and refuses matrix devices.

- Claude Desktop MCPB bundle ([#151](https://github.com/descipar/wled-mcp/issues/151),
  [contract](docs/contract/mcpb-bundle.md)): the release workflow builds
  `wled-mcp-<version>.mcpb` in its own job and, after the PyPI upload succeeded, a separate job
  attaches it with a SHA-256 file to the GitHub release; a failure of either job does not affect the
  PyPI upload. The bundle only makes Claude Desktop start the released package through `uvx`
  (it needs uv on the PATH of Claude Desktop). It is built along with each release, not tested
  by the project and comes without warranty. The jobs h

The release on GitHub

Source: the official MCP Registry list on 2026-11-12 and on 2026-11-13; release notes from the GitHub Releases API, checked 2026-11-13.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.4.0
Latest stable
0.4.0
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-13. About the version the registry lists; a manual install may resolve to a different one.

Integrity, provenance, license

Integrity
sha256-4c9e3c30c0f744bf9…
License
Apache-2.0

Source: the package registry · 2026-11-13.

Usage

Downloads
449 in the last month

Source: pypistats.org · 2026-11-13.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-13.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.4.0 on PyPIExists and can be installedmatchesPyPI · 2026-11-13
Repository github.com/descipar/wled-mcpOpens publiclymatchesapi.github.com · 2026-11-13

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.descipar
GitHub owner
a personal account (descipar)
Repository
github.com/descipar/wled-mcp
Stars
1
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-13; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 7 record checks met · 1 does not apply · 1 not checked

  • #9,264 of 20,610 packages by monthly downloads, tied with 10 others
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierApache-2.0
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Not checkedNo known critical or high advisory in the package or its dependenciesWe could not resolve its dependencies.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-13 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.descipar/wled-mcp

Answered from the data above

Who publishes io.github.descipar/wled-mcp?

The registry ties the namespace io.github.descipar to the GitHub account descipar; only its owner can publish under it. Its linked repository, github.com/descipar/wled-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.descipar/wled-mcp safe to install?

We do not rate servers as safe or unsafe. 7 of its 7 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.descipar/wled-mcp been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.descipar/wled-mcp publish a security policy?

Yes: its repository has a public security policy (github.com/descipar/wled-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.4.0, the latest stable release on PyPI.

Where is the source code of io.github.descipar/wled-mcp?

In github.com/descipar/wled-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-13; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-13
Hosting type
registry · 2026-11-13
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-13
Required credentials
none declared
registry · 2026-11-13 · no declaration is not a guarantee
Package registry
registry · 2026-11-13
Freshness
0–30 days
registry updatedAt · 2026-11-13
Lifecycle status
registry · 2026-11-13
License class
package registry · 2026-11-13
Integrity hash
declared (sha256)
package registry · 2026-11-13
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
not known (our limit)
not resolvable for our pinned target Python 3.12 - our limitation
Popularity
449 downloads a month
package registry · 2026-11-13
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-13
Maintenance
api.github.com · 2026-11-13
Environment
your machine
where it runs, from the hosting type · 2026-11-13

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.descipar/wled-mcp: MCP server record.” Data checked 2026-11-13. https://protocolprobe.com/mcp/servers/io.github.descipar/wled-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 7 of 7 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.descipar/wled-mcp)](https://protocolprobe.com/mcp/servers/io.github.descipar/wled-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology