Orion Celestia Intel

What Orion Celestia Intel MCP server does

Orion Celestia Intel MCP server exposes Celestia mainnet intelligence to MCP-compatible AI agents. Its data covers daily network briefs, event-driven anomaly signals, current network state, historical changes, archived reports, rollup namespace activity, and validator rankings.

The service is read-only. It does not manage wallets, hold keys, submit transactions, or mutate network state. Returned figures include provenance links to the Celenium or Celestia LCD endpoint used to obtain the data, allowing an agent or developer to trace metrics back to their sources.

How it works

The server combines two data paths. Orion’s analysis API provides daily reports, narrative briefs, signals, trends, and historical report search. Celenium supplies live namespace and validator drill-down information. The available signal categories include changes in DA utilization and fees, blob-volume deviations, namespace leadership shifts, staking and concentration changes, jailings, TIA price movements, governance activity, and celestia-app releases.

Signals are event-driven rather than continuous state descriptions. A namespace that remains dominant or utilization that stays steady may not produce a new signal. Daily narrative is generated from structured data and passes an automated citation check before publication.

In addition to tools, Orion Celestia Intel MCP server provides resources for the latest report, the report archive, and reports by date. It also includes prompts for producing a cited daily briefing and reviewing rollup data availability and DA cost context.

Setup and configuration

The hosted endpoint is available at https://orionlabsone.cc/mcp. HTTP-capable clients can connect directly. Claude Code, Cursor, and VS Code each have documented configuration examples in the repository. Claude Desktop, Codex, Windsurf, Cline, and other stdio-only clients can use mcp-remote as a bridge.

For a local deployment, clone the repository, run npm install, and use npm run start for Streamable HTTP or npm run start:stdio for stdio transport. The default local HTTP address is 127.0.0.1:8791/mcp. npm run smoke checks the tools against the live API, while npm run typecheck checks the source types.

Supported configuration variables are PORT, HOST, ORION_API_BASE, and CELENIUM_BASE. Their defaults are port 8791, host 127.0.0.1, the Orion hosted API base, and Celenium’s Celestia mainnet API base respectively.

Tools and capabilities

The tools support these workflows:

• Retrieve today’s brief, with optional Orion narrative prose.
• Find information, notable, or critical signals for today or a selected date.
• Inspect height, DA volume, validator count, staking ratios, Nakamoto coefficient, and TIA price.
• Compare day-over-day and week-over-week changes.
• Retrieve multi-day histories for metrics such as fees, blobs, price, and staking ratio.
• List, fetch, and search archived reports.
• Rank namespaces by posted data and inspect namespace size, blob count, and latest activity.
• Rank validators by stake and view moniker, commission, and jailed status.

Limitations and notes

Orion Celestia Intel MCP server is designed for observation and analysis, not transaction execution. It depends on the hosted Orion API and, for live drill-down tools, the Celenium API. The archive and daily analysis represent available reports and detected changes; absence of a signal does not necessarily mean that no condition exists, only that the configured event-driven detectors did not identify a qualifying change.