Skip to content
Odingard Security logo

Odingard Security MCP server

Which MCP servers are Odingard Security's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Odingard Security

Whose server it is
  • Registry namecom.odingard/bifrostverified in the MCP registry

The registry name sits under odingard.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked it
  • Stateper-install address

The registry lists this address as a template, with parts each company fills in for its own install. There is no shared address to ask, so we did not check it.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "bifrost": {
      "type": "http",
      "url": "https://bifrost-mcp-842108046620.us-central1.run.app/t/{tenant}/mcp"
    }
  }
}

Replace the parts in curly braces with the values of your own Odingard Security install.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.