Is Cue down?

MCP serverBy cue-mcp-production.up.railway.app. How to connect and its trust score are on the listing page.

Down

Yes, Cue is down.

It has failed every check since 5 Nov 2026, 16:18 UTC (2 days 22 h, 4 checks). Latest error: initialize returned HTTP 404. It last passed on 5 Nov 2026, 01:02 UTC.

Latest check

Last check
13 h ago (8 Nov 2026, 00:28 UTC)
Response time
Not measured (typical 303 ms)
Next check
In about 9 h
How often
About every 15 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days63.6%11 checks
Last 30 days89.5%38 checks
All checks passedSome failedAll failedNot checked

Uptime is the share of checks that passed. We checked it about every 15 hours over the last 7 days.

Outages in the last 30 days

1 outage, 2 days 22 h of failed checks in total.

StartedDurationFailed checksFirst error
5 Nov 2026, 16:18 UTCOngoing, 2 days 22 h so far4initialize returned HTTP 404

Times are when our checks ran, about every 15 hours for this listing, so start times and durations are accurate to about that.

Recent checks

WhenResultHTTPTime
8 Nov 2026, 00:28 UTCinitialize returned HTTP 404404367 ms
6 Nov 2026, 18:41 UTCinitialize returned HTTP 404404339 ms
6 Nov 2026, 07:23 UTCinitialize returned HTTP 404404338 ms
5 Nov 2026, 16:18 UTCinitialize returned HTTP 404404371 ms
5 Nov 2026, 01:02 UTCPassed200319 ms
4 Nov 2026, 10:12 UTCPassed200280 ms
3 Nov 2026, 19:02 UTCPassed200292 ms
3 Nov 2026, 04:33 UTCPassed200294 ms
2 Nov 2026, 14:50 UTCPassed200303 ms
2 Nov 2026, 02:04 UTCPassed200336 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 15 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.