Bifrost
REMOTE · BIFROST-MCP-842108046620.US-CENTRAL1.RUN.APP · 2 COMPONENTS
Query a company's Bifrost trust gateway: cited answers and approved actions with signed receipts.
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Tool “find_company” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bifrost-mcp-842108046620.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp | HTTP error | 404 | |
| http (plaintext) | http://bifrost-mcp-842108046620.us-central1.run.app/public/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_company Ask a company ~59
Ask a listed company a question. The answer comes only from its public-tier evidence with exact source citations and a signed receipt, or a refusal when public evidence does not support an answer.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
find_company Find a company ~59
Find a company's public trust center by name or domain. A match whose domain is domain-verified is proven to belong to the company; a name match without a verified domain is self-asserted by the workspace owner.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
get_trust_profile Get trust profile ~53
Read the public-tier trust profile a listed company publishes: its summary, framework and control statuses, subprocessors and the titles of its public documents. Never returns private or restricted material.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
No output schema declared.
No examples provided.
invite_company Request a company ~55
Record interest in a company that isn't listed yet and get a link to share so it can publish its own trust center. No message is sent to the company.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | – |
| domain | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Bifrost MCP server?
Bifrost is a hosted endpoint at https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bifrost-mcp-842108046620.us-central1.run.app
claude mcp add --transport http com-odingard-bifrost 'https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp'
What is the Bifrost MCP server?
Bifrost is an MCP server listed in the public MCP registry as com.odingard/bifrost. Query a company's Bifrost trust gateway: cited answers and approved actions with signed receipts. This page covers its hosted endpoint (https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp).
Is the Bifrost MCP server safe to use?
Bifrost scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Bifrost MCP server expose?
Bifrost exposes 4 tools: find_company, get_trust_profile, ask_company, invite_company. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.
Does the Bifrost MCP server require authentication?
Its publisher declares no required credentials for Bifrost. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Bifrost MCP server still maintained?
Bifrost is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.