Is uta-shield Remote (Barter-enabled) down?
Down
Yes, uta-shield Remote (Barter-enabled) is down.
It has not passed a check since we started checking it on 27 Oct 2026. Latest error: initialize returned HTTP 405.
Latest check
- Last check
- 13 h ago (10 Nov 2026, 14:50 UTC)
- Response time
- Not measured
- Next check
- In about 3 days
- How often
- About every 33 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 33 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, 14:50 UTC | initialize returned HTTP 405 | 405 | 200 ms |
| 7 Nov 2026, 11:22 UTC | initialize returned HTTP 405 | 405 | 210 ms |
| 6 Nov 2026, 02:49 UTC | initialize returned HTTP 405 | 405 | 178 ms |
| 4 Nov 2026, 17:38 UTC | initialize returned HTTP 405 | 405 | 223 ms |
| 3 Nov 2026, 07:28 UTC | initialize returned HTTP 405 | 405 | 171 ms |
| 1 Nov 2026, 22:21 UTC | initialize returned HTTP 405 | 405 | 176 ms |
| 31 Oct 2026, 19:48 UTC | initialize returned HTTP 405 | 405 | 207 ms |
| 30 Oct 2026, 09:37 UTC | initialize returned HTTP 405 | 405 | 204 ms |
| 29 Oct 2026, 00:26 UTC | initialize returned HTTP 405 | 405 | 180 ms |
| 28 Oct 2026, 11:42 UTC | initialize returned HTTP 405 | 405 | 219 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 33 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.