Is ScrapeOwl MCP by usefulapi down?
Down
Yes, ScrapeOwl MCP by usefulapi is down.
It has not passed a check since we started checking it on 29 Oct 2026. Latest error: initialize returned HTTP 302.
Latest check
- Last check
- 2 days ago (8 Nov 2026, 21:05 UTC)
- Response time
- Not measured
- Next check
- In about 20 h
- How often
- About every 30 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 30 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 |
|---|---|---|---|
| 8 Nov 2026, 21:05 UTC | initialize returned HTTP 302 | 302 | 159 ms |
| 7 Nov 2026, 15:00 UTC | initialize returned HTTP 302 | 302 | 88 ms |
| 6 Nov 2026, 09:17 UTC | initialize returned HTTP 302 | 302 | 92 ms |
| 5 Nov 2026, 03:53 UTC | initialize returned HTTP 302 | 302 | 85 ms |
| 3 Nov 2026, 20:07 UTC | initialize returned HTTP 302 | 302 | 164 ms |
| 2 Nov 2026, 10:17 UTC | initialize returned HTTP 302 | 302 | 142 ms |
| 1 Nov 2026, 07:12 UTC | initialize returned HTTP 302 | 302 | 147 ms |
| 31 Oct 2026, 00:05 UTC | initialize returned HTTP 302 | 302 | 119 ms |
| 30 Oct 2026, 10:33 UTC | initialize returned HTTP 302 | 302 | 75 ms |
| 29 Oct 2026, 20:50 UTC | initialize returned HTTP 302 | 302 | 90 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 30 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.