Is Fd Daas MCP Cust1 down?
Up
No, Fd Daas MCP Cust1 is up.
It passed its latest check 9 min ago in 2.5 s. It has passed every check since 7 Nov 2026, 16:11 UTC.
Latest check
- Last check
- 9 min ago (10 Nov 2026, 11:43 UTC)
- Response time
- 2.5 s (typical 1.2 s)
- Next check
- In about 11 h
- How often
- About every 12 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 12 hours over the last 7 days.
Outages in the last 30 days
1 outage, 3 days 16 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 4 Nov 2026, 00:14 UTC | 3 days 16 h | 4 | initialize returned HTTP 405 |
Times are when our checks ran, about every 12 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 11:43 UTC | Passed | 401 | 2.5 s |
| 10 Nov 2026, 00:48 UTC | Passed | 401 | 1.1 s |
| 9 Nov 2026, 12:45 UTC | Passed | 401 | 2.8 s |
| 9 Nov 2026, 02:33 UTC | Passed | 401 | 1.2 s |
| 8 Nov 2026, 15:14 UTC | Passed | 401 | 2.1 s |
| 8 Nov 2026, 03:26 UTC | Passed | 401 | 1.2 s |
| 7 Nov 2026, 16:11 UTC | Passed | 401 | 1.5 s |
| 6 Nov 2026, 11:34 UTC | initialize returned HTTP 405 | 405 | 2.5 s |
| 5 Nov 2026, 05:24 UTC | initialize returned HTTP 405 | 405 | 1.7 s |
| 4 Nov 2026, 15:00 UTC | initialize returned HTTP 405 | 405 | 2.4 s |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 12 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.