Orbit Sentinel MCP

What viventine-space/orbit-sentinel-mcp MCP server does

The viventine-space/orbit-sentinel-mcp MCP server exposes Orbit Sentinel’s space-regulatory data to MCP-compatible AI clients. Its source data comes from the FCC, ITU, UNOOSA, and FAA-AST, covering a large collection of filings that can be searched and investigated through an agent conversation.

Supported research tasks include semantic filing search, entity dossiers, spectrum-holding lookups, launch-license research, and filing alerts. The README identifies tools such as research, search_filings, and get_entity_profile; the available tool set is presented to the connected client after setup.

How it works

The project is a small Go client for Orbit Sentinel’s public REST API rather than a separate regulatory-data store. A local binary communicates with the API over MCP stdio, while the hosted service accepts MCP requests over stateless Streamable HTTP at https://orbit-sentinel.viventine.com/mcp.

Authentication is required for API use. Remote clients can sign in through OAuth 2.1, or send an Orbit Sentinel API key as a bearer token. Local deployments provide the key through environment variables. OAuth-capable clients can discover the protected-resource flow from the endpoint’s authentication response.

Setup and configuration

The viventine-space/orbit-sentinel-mcp MCP server can be installed with Homebrew on macOS, downloaded as a platform release archive, built with Go, or installed as a Claude Desktop .mcpb extension. The documented Homebrew command is:

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

For a local process, set MCP_API_URL to the Orbit Sentinel API base URL and MCP_API_KEY to a key from the Viventine console. Claude Desktop requires an absolute binary path in its MCP configuration. Claude Code can register the executable with claude mcp add and pass both variables.

The no-install option points an HTTP-capable client at the hosted endpoint. Claude Code can register it with the HTTP transport, and Claude Desktop or claude.ai can add it as a custom connector. A stdio-only client can use npx mcp-remote as a bridge.

Tools and capabilities

Available functions and data areas include:

• research for broader Orbit Sentinel investigations
• search_filings for finding relevant regulatory records
• get_entity_profile for retrieving an organization’s profile
• Semantic search across space regulatory filings
• Research into spectrum holdings and launch licenses
• Filing-alert workflows described by the service

The server is intended for clients such as Claude Desktop, Claude Code, Cursor, and other MCP clients. An API key or authenticated remote session is needed to use protected operations.

Limitations and notes

The repository describes the server as a thin API client, so the underlying Orbit Sentinel service determines the available data and response behavior. Beta access and API credentials are obtained through the Viventine console. The macOS release binaries are not notarized, which may require clearing the quarantine attribute after a manual download. Remote access avoids installing or updating a local binary, but requires an HTTP-capable MCP client or an MCP bridge.