Remote MCP · Endpoint

Bifrost MCP server

Yes, as of 4 days ago: the server returned an HTTP error.

DownLast checked 4 days ago

Server URL

https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.odingard/bifrost
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
45.5% from 11 checks
Described by its publisher as
Query a company's Bifrost trust gateway: cited answers and approved actions with signed receipts.
Listing
From the official MCP registry (active).
Recent checks of Bifrost
CheckedResultHandshake
4 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoHandshake completed58 ms
22 days agoHandshake completed73 ms
22 days agoHandshake completed194 ms
24 days agoHandshake completed68 ms
26 days agoHandshake completed54 ms

The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 11.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Bifrost and makes no claim about it beyond what these checks measured.