com.nodle/iot-dashboard
Nodle IoT Dashboard
Is the Nodle IoT Dashboard MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-06.
Fleets, devices, detections and webhooks on the Nodle Bluetooth Low Energy network.
needs auth probed 2026-11-15 · unchanged since 2026-11-06 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Authorization required"}- Endpoint
- https://dashboard.nodle.com/api/mcp (streamable-http)
- Host
- dashboard.nodle.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://dashboard.nodle.com/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server dashboard.nodle.com, PKCE S256, grants authorization_code, refresh_token.
Scopes read write provision.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://dashboard.nodle.com/docs/mcp
- Registry
- active, updated 2026-11-04 · registry entry
- Changes
- 2 recorded, reachable in 2 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 dashboard.
- Buron ai.buron/buron · paid (402)
- Dryos Workspace ai.dryos/dryos-workspace · needs auth
- Quillm ai.quillm/quillm · needs auth
- Elasticflow app.elasticflow/mcp · needs auth
- Framezone app.framezone/framezone · alive
- Race Calendar F1 app.racecalendar/f1 · alive
- MCP Scan — weekly registry health scans app.rowb.mcp-scan/weekly · alive
- NinoxNet ar.com.ninox/ninoxnet · needs auth
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 11:10 | needs auth | ||||
| 2026-11-05 11:12 | needs auth |
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
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.