io.changedetection/mcp
changedetection.io (official)
Is the changedetection.io (official) MCP server down? No. It is up and needs your URL, probed 2026-11-06.
Official changedetection.io MCP: web page change tracking, back-in-stock and price alerts.
needs your URL probed 2026-11-14 · unchanged since 2026-11-06
The URL has placeholders that each user fills in: {account}.- Endpoint
- https://lemonade.changedetection.io/{account}/mcp/v1 (streamable-http)
- Host
- lemonade.changedetection.io
- Repository
- https://github.com/dgtlmoon/changedetection.io
- Website
- https://changedetection.io/MCP
- Registry
- active, updated 2026-11-05 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention changedetection or tracking or alerts.
- ChangeDetection.io MCP Server io.github.rusty4444/changedetection-mcp · needs mcp<2
- AIS Agent Flight Recorder — dead-man alerts & resume for AI agents ai.aislabs/recorder · alive
- AnomalyArmor ai.anomalyarmor/armor-mcp · needs auth
- AssetLog ai.assetlog/assetlog · needs auth
- DoneThat ai.donethat/donethat · needs auth
- ai.klipy/klipy · needs auth
- KOLens ai.kolens/kolens-mcp · needs auth
- ai.ohmyfin/banking-intelligence · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-06 10:56 | needs your URL | ||||
| 2026-11-05 10:58 | needs your URL |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- Every URL of the registry entry has a placeholder that each user fills in, such as a tenant, a project or a host of their own. Without that value there is nothing to call, so the probe does not call the URL, and the entry is not counted as down. A client asks the user for the value.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.