# Bifrost (remote · bifrost-mcp-842108046620.us-central1.run.app)

Query a company's Bifrost trust gateway: cited answers and approved actions with signed receipts.

- Trust score: 18/100 (low)
- Change this week: −50
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `bifrost-mcp-842108046620.us-central1.run.app`: 18/100 (this document), [markdown](https://verifymcp.io/servers/com-odingard-bifrost/public-mcp.md), [page](https://verifymcp.io/servers/com-odingard-bifrost/public-mcp)
- remote · `bifrost-mcp-842108046620.us-central1.run.app`: 0/100, [markdown](https://verifymcp.io/servers/com-odingard-bifrost/t-tenant-mcp.md), [page](https://verifymcp.io/servers/com-odingard-bifrost/t-tenant-mcp)

## Channel facts

- Endpoint: `https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.48`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-odingard-bifrost 'https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-odingard-bifrost": {
      "url": "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-odingard-bifrost": {
      "type": "http",
      "url": "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-odingard-bifrost]
url = "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-odingard-bifrost": {
      "type": "remote",
      "url": "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-odingard-bifrost --url 'https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-odingard-bifrost:
    url: "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-odingard-bifrost": {
      "Transport": "http",
      "Url": "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-odingard-bifrost -t streamable-http -u 'https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-odingard-bifrost": {
      "type": "http",
      "url": "https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 18, −51)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-31 (score 69, +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.

### 2026-10-29 (score 68, +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.

### 2026-10-28 (score 67, 0)

- [security] Tool “find_company” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 67)

First indexed and scored.

## MCP tools (4)

### `find_company` (~59 tokens)

Find a company

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.

Input parameters:

- `query` (string, required)

### `get_trust_profile` (~53 tokens)

Get trust profile

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.

Input parameters:

- `company` (string, required)

### `ask_company` (~59 tokens)

Ask a company

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.

Input parameters:

- `company` (string, required)
- `question` (string, required)

### `invite_company` (~55 tokens)

Request a company

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.

Input parameters:

- `company_name` (string)
- `domain` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-odingard-bifrost/public-mcp#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://bifrost-mcp-842108046620.us-central1.run.app/public/mcp
- Repository: https://github.com/Odingard/Bifrost
- Website: https://odingard.com/bifrost
- Changelog RSS feed: https://verifymcp.io/servers/com-odingard-bifrost/public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-odingard-bifrost/public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-odingard-bifrost/public-mcp