Is Pin Payments MCP by usefulapi down?
Down
Yes, Pin Payments 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
- 25 h ago (10 Nov 2026, 03:31 UTC)
- Response time
- Not measured
- Next check
- In about 2 days
- How often
- About every 31 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 31 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 |
|---|---|---|---|
| 10 Nov 2026, 03:31 UTC | initialize returned HTTP 302 | 302 | 91 ms |
| 8 Nov 2026, 20:32 UTC | initialize returned HTTP 302 | 302 | 118 ms |
| 7 Nov 2026, 13:53 UTC | initialize returned HTTP 302 | 302 | 78 ms |
| 6 Nov 2026, 08:48 UTC | initialize returned HTTP 302 | 302 | 163 ms |
| 5 Nov 2026, 01:52 UTC | initialize returned HTTP 302 | 302 | 83 ms |
| 3 Nov 2026, 18:09 UTC | initialize returned HTTP 302 | 302 | 88 ms |
| 2 Nov 2026, 08:38 UTC | initialize returned HTTP 302 | 302 | 96 ms |
| 1 Nov 2026, 01:53 UTC | initialize returned HTTP 302 | 302 | 116 ms |
| 31 Oct 2026, 11:38 UTC | initialize returned HTTP 302 | 302 | 77 ms |
| 30 Oct 2026, 21:45 UTC | initialize returned HTTP 302 | 302 | 121 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 31 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.