Is SimplyRETS MCP by usefulapi down?
Down
Yes, SimplyRETS MCP by usefulapi is down.
It has not passed a check since we started checking it on 21 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 41 h ago (9 Nov 2026, 10:08 UTC)
- Response time
- Not measured
- Next check
- In about 31 h
- How often
- About every 3 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 3 days 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, 10:08 UTC | initialize returned HTTP 302 | 302 | 269 ms |
| 6 Nov 2026, 11:53 UTC | initialize returned HTTP 302 | 302 | 96 ms |
| 3 Nov 2026, 10:21 UTC | initialize returned HTTP 302 | 302 | 179 ms |
| 30 Oct 2026, 20:31 UTC | initialize returned HTTP 302 | 302 | 108 ms |
| 29 Oct 2026, 12:38 UTC | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
| 28 Oct 2026, 04:44 UTC | initialize returned HTTP 302 | 302 | 113 ms |
| 26 Oct 2026, 23:56 UTC | initialize returned HTTP 302 | 302 | 134 ms |
| 25 Oct 2026, 17:03 UTC | initialize returned HTTP 302 | 302 | 92 ms |
| 24 Oct 2026, 08:49 UTC | initialize returned HTTP 302 | 302 | 117 ms |
| 23 Oct 2026, 02:41 UTC | initialize returned HTTP 302 | 302 | 73 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 3 days 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.