Orbit Sentinel

Orbit Sentinel MCP Server

MCP (Model Context Protocol) server for Orbit Sentinel — 419,000+ extracted space regulatory filings from FCC, ITU, UNOOSA, and FAA-AST, queryable from Claude Desktop, Claude Code, Cursor, or any MCP client.

An API key is required. Beta access: https://console.viventine.com.

The server is a thin, open-source (MIT) client of the public REST API — five Go files, easy to audit before you run it. Run it locally over stdio, or skip the install entirely and point your client at the hosted remote endpoint (below).

Install

Remote (no install)

The lowest-friction path — no binary, no updates. Point any HTTP-capable MCP client at:

https://orbit-sentinel.viventine.com/mcp

Transport is Streamable HTTP (stateless). Two ways to authenticate:

OAuth (recommended) — sign in with your Viventine account in the browser; no key to copy or store. In Claude Code:

claude mcp add --transport http orbit-sentinel https://orbit-sentinel.viventine.com/mcp

Then run /mcp -> orbit-sentinel -> authenticate. A browser opens for sign-in and consent; Claude Code stores the token and refreshes it automatically. The same works as a custom connector in claude.ai / Claude Desktop (Settings -> Connectors -> Add custom connector -> paste the URL -> sign in).

API key — if you'd rather use a static key (or your client can't do OAuth), pass your console key as a bearer token:

claude mcp add --transport http orbit-sentinel \
  https://orbit-sentinel.viventine.com/mcp \
  --header "Authorization: Bearer <your-key>"

Get a key / beta access at https://console.viventine.com.

Generic MCP clients — any Streamable HTTP client works via OAuth 2.1 (RFC 9728 protected-resource discovery) or an Authorization: Bearer <key> header. For a stdio-only client, bridge with npx mcp-remote https://orbit-sentinel.viventine.com/mcp.

Claude Desktop (one-click)

Download orbit-sentinel-mcp.mcpb and double-click it — Claude Desktop installs the extension and prompts for your API key. Bundles macOS (universal), Linux, and Windows binaries.

Homebrew (macOS — recommended)

brew install --cask viventine-space/tap/orbit-sentinel-mcp

Installs to $(brew --prefix)/bin/orbit-sentinel-mcp, handles the quarantine flag for you, and upgrades with brew upgrade.

Manual download

Download the archive for your platform from the latest release, then:

tar -xzf orbit-sentinel-mcp_*.tar.gz
mkdir -p ~/bin && mv orbit-sentinel-mcp ~/bin/

macOS only — the binary is not notarized yet, so clear the quarantine flag once:

xattr -d com.apple.quarantine ~/bin/orbit-sentinel-mcp

Windows: unzip and note the full path to orbit-sentinel-mcp.exe.

Build from source

go install github.com/viventine-space/orbit-sentinel-mcp@latest

Configure

The server reads two environment variables:

Variable	Purpose
MCP_API_URL	Orbit Sentinel API base URL (https://orbit-sentinel.viventine.com)
MCP_API_KEY	Your API key from the console

Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json (Windows: %APPDATA%\Claude\claude_desktop_config.json), using the absolute path to the binary (~ is not expanded):

{
  "mcpServers": {
    "orbit-sentinel": {
      "command": "/absolute/path/to/orbit-sentinel-mcp",
      "env": {
        "MCP_API_URL": "https://orbit-sentinel.viventine.com",
        "MCP_API_KEY": "<your-key>"
      }
    }
  }
}

Claude Code — one command:

claude mcp add orbit-sentinel \
  --env MCP_API_URL=https://orbit-sentinel.viventine.com \
  --env MCP_API_KEY=<your-key> \
  -- ~/bin/orbit-sentinel-mcp

Restart your client; the Orbit Sentinel tools (research, search_filings, get_entity_profile, …) appear in the tools menu.

Releasing (maintainers)

Tag and push — GitHub Actions builds and publishes all platforms:

git tag v0.x.y && git push origin v0.x.y

Asset names are version-stable (orbit-sentinel-mcp_<os>_<arch>.tar.gz), so releases/latest/download/... URLs always serve the newest build.

The Claude Desktop bundle (orbit-sentinel-mcp.mcpb) is packed and uploaded by the release workflow — the manifest template lives at mcpb/manifest.json (its version is stamped from the tag at pack time).

Then repeat the Glama release — it does not auto-update from GitHub, and it gates the quality score on the badge above. On the Dockerfile admin page, the saved build spec should carry over (build steps install Go and go build; placeholder parameters need a dummy MCP_API_KEY to satisfy the env schema) — click Build, then Make Release with the new version. Manual for now; consider Glama API integration next release cycle.