ai.datasnack/datasnack
DataSnack
Is the DataSnack MCP server down? It gave no valid answer in the probe of 2026-11-15: server error (HTTP 503). One failed probe is not an outage.
Seven-day forecasts of real-world numbers, linked and graded daily; sign-in adds Excel exports.
server error no valid answer since 2026-11-15 · probed 2026-11-15 · HTTP 503
Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>503 Service Temporarily Unavailable</title></head> <body> <center><h1>503 Service Tempo
- Endpoint
- https://datasnack.ai/mcp (streamable-http)
- Host
- datasnack.ai
- Website
- https://datasnack.ai/
- Registry
- active, updated 2026-11-14 · registry entry
- Changes
- 4 recorded, reachable in 3 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 forecasts or exports.
- RoboSystems ai.robosystems/robosystems · needs auth
- SnowSure — Snow & Ski ai.snowsure/snow · alive
- Timix.AI ai.timix/time-tracking · alive
- SnowData — Live Snow ai.snowdata/live-snow · not MCP
- ai.smithery/jenniferjiang0511-mit-ai-studio-hw3 · not found
- Nausika app.nausika/mcp · alive
- app.strikemission/surf-trip-planner · alive
- Agent SVG Registry app.vercel.agent-svg-registry/mcp · not found
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-15 10:58 | server error | ||||
| 2026-11-14 10:30 | alive | 322 ms | 23 | 3.2k | 1.9k |
| 2026-11-12 11:17 | alive | 640 ms | 21 | 2.9k | 1.7k |
| 2026-11-11 11:01 | alive | 851 ms | 20 | 2.7k | 1.6k |
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
- No valid answer since 2026-11-15. One failed probe is not an outage: the board calls a server down after two days without a valid answer. The next probe runs within a day.
- The server answers HTTP 503 on initialize. The error output, if any, is above.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.