Is Bifrost down?

MCP serverBy bifrost-mcp-842108046620.us-central1.run.app. How to connect and its trust score are on the listing page.

Down

Yes, Bifrost is down.

It has failed every check since 2 Nov 2026, 00:50 UTC (3 days 2 h, 4 checks). Latest error: initialize returned HTTP 404. It last passed on 1 Nov 2026, 15:24 UTC.

Latest check

Last check
14 h ago (4 Nov 2026, 13:08 UTC)
Response time
Not measured (typical 218 ms)
Next check
In about 8 h
How often
About every 14 hours over the last 7 days

Uptime

Last 24 hours0.0%1 check
Last 7 days63.6%11 checks
Last 30 days73.3%15 checks
All checks passedSome failedAll failedNot checked

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

Outages in the last 30 days

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

StartedDurationFailed checksFirst error
2 Nov 2026, 00:50 UTCOngoing, 3 days 2 h so far4initialize returned HTTP 404

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

Recent checks

WhenResultHTTPTime
4 Nov 2026, 13:08 UTCinitialize returned HTTP 404404264 ms
3 Nov 2026, 04:03 UTCinitialize returned HTTP 404404198 ms
2 Nov 2026, 13:20 UTCinitialize returned HTTP 404404276 ms
2 Nov 2026, 00:50 UTCinitialize returned HTTP 404404209 ms
1 Nov 2026, 15:24 UTCPassed200246 ms
1 Nov 2026, 04:04 UTCPassed200209 ms
31 Oct 2026, 13:56 UTCPassed200218 ms
31 Oct 2026, 00:18 UTCPassed200222 ms
30 Oct 2026, 11:22 UTCPassed200215 ms
29 Oct 2026, 21:23 UTCPassed200240 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 14 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.