Is Famly MCP by usefulapi down?
Down
Yes, Famly MCP by usefulapi is down.
It has not passed a check since we started checking it on 30 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 46 h ago (9 Nov 2026, 06:14 UTC)
- Response time
- Not measured
- Next check
- In about 32 h
- How often
- About every 29 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 29 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 9 Nov 2026, 06:14 UTC | initialize returned HTTP 302 | 302 | 150 ms |
| 8 Nov 2026, 01:51 UTC | initialize returned HTTP 302 | 302 | 90 ms |
| 6 Nov 2026, 23:20 UTC | initialize returned HTTP 302 | 302 | 82 ms |
| 5 Nov 2026, 17:55 UTC | initialize returned HTTP 302 | 302 | 122 ms |
| 4 Nov 2026, 10:29 UTC | initialize returned HTTP 302 | 302 | 107 ms |
| 3 Nov 2026, 02:08 UTC | initialize returned HTTP 302 | 302 | 125 ms |
| 1 Nov 2026, 19:03 UTC | initialize returned HTTP 302 | 302 | 118 ms |
| 31 Oct 2026, 12:44 UTC | initialize returned HTTP 302 | 302 | 73 ms |
| 30 Oct 2026, 22:41 UTC | initialize returned HTTP 302 | 302 | 117 ms |
| 30 Oct 2026, 09:15 UTC | initialize returned HTTP 302 | 302 | 356 ms |
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 29 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.