Celestia network intelligence for AI agents: daily analysis, anomaly signals and DA metrics.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Inspect callable tools, capabilities, and parameters exposed to AI agents by Orion Celestia Intel.
get_daily_briefWhat's happening on Celestia today? (set `include_narrative` for Orion's written prose)
get_signalsAny anomalies (info / notable / critical) today or on date X?
get_network_stateCurrent height, DA volume, validators, staking ratios, Nakamoto coefficient, TIA price
get_trendsWhat changed since yesterday / last week? (day- and week-over-week deltas)
get_metric_historyChart one metric (fees, blobs, price, staking ratioβ¦) over N days
list_reportsWhat daily reports exist in the archive?
Celestia network intelligence for AI agents. An MCP server over Orion's daily analysis: anomaly signals, network verdicts, staking & DA metrics, live namespace and validator drill-downs β each figure linked back to the source it came from.
https://orionlabsone.cc/mcp
Orion watches Celestia mainnet continuously and publishes a daily machine-written brief: what moved, what drifted from baseline, and why it matters. This kit exposes that analysis to AI agents over the Model Context Protocol.
Think of it as an analysis layer for the Celestia agent ecosystem. It sits alongside knowledge bases (which answer "what is CIP-21?") and raw-data or transaction kits (which list blobs or build a delegate tx). Orion answers a different question: what is happening on the network right now, is it normal, and how did we get here?
Every number the server returns carries a provenance link to the Celenium or Celestia LCD endpoint it was read from, so the agent can cite its sources β and so can you. The server is read-only: no wallets, keys, or transactions anywhere in it.
Today & anomalies
| Tool | Question it answers |
|---|---|
get_daily_brief | What's happening on Celestia today? (set include_narrative for Orion's written prose) |
get_signals | Any anomalies (info / notable / critical) today or on date X? |
get_network_state | Current height, DA volume, validators, staking ratios, Nakamoto coefficient, TIA price |
Trends & history
| Tool | Question it answers |
|---|---|
get_trends | What changed since yesterday / last week? (day- and week-over-week deltas) |
get_metric_history | Chart one metric (fees, blobs, price, staking ratioβ¦) over N days |
list_reports | What daily reports exist in the archive? |
get_report | Full report for a given date |
search_reports | When did the archive last mention "eclipse" or "block time"? |
Live drill-down (straight from Celenium)
| Tool | Question it answers |
|---|---|
get_top_namespaces | Which rollups post the most data to Celestia right now? |
get_namespace | Detail for one namespace: size, blob count, last activity |
get_top_validators | Largest validators by stake β moniker, commission, jailed status |
Beyond tools, the server exposes MCP resources an agent can read or subscribe to:
orion://latest β the most recent daily reportorion://reports β the archive indexorion://report/{date} β any archived report by dateβ¦and ready-made prompts to guide an agent:
daily_celestia_briefing β produce a grounded, source-cited daily briefingrollup_da_check β survey who dominates blobspace and the current DA cost contextOrion's detectors are event-driven, not state-driven β a persistently dominant namespace or a steady utilization day produces no signal, so what you see is what actually changed:
Each daily brief is written by an LLM narrator and passes an automated citation check β every number in the prose is verified against the structured data before publishing.
The MCP server runs at https://orionlabsone.cc/mcp.
Claude Code
Cursor β add to .cursor/mcp.json (already included if you cloned this repo):
VS Code β add to .vscode/mcp.json:
Claude Desktop / Codex / Windsurf / Cline / any stdio-only client β bridge with mcp-remote:
Per-client walkthroughs: Claude Code Β· Claude Desktop Β· Cursor Β· Codex Β· VS Code
Then just ask:
"Any anomalies on Celestia today?" Β· "What changed on Celestia since yesterday?" Β· "Which rollups post the most data right now?" Β· "How concentrated is the validator set?" Β· "When did the archive last flag block time?"
The bundled /brief and /signals commands wrap the two most common queries.
Environment: PORT (default 8791), HOST (default 127.0.0.1), ORION_API_BASE (default https://orionlabsone.cc), CELENIUM_BASE (default https://api-mainnet.celenium.io/v1, used by the drill-down tools).
The underlying API is plain JSON, usable directly or via function calling with the OpenAPI spec:
| Endpoint | Returns |
|---|---|
GET /api/latest | today's full report |
GET /api/reports | archive index |
GET /api/reports/{date} | full report for a date |
GET /api/rss | the brief as an RSS feed |
Apache-2.0, Copyright 2026 Orion Labs. Questions, ideas, or a tool you wish existed: open an issue.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/orion-celestia-intel)<a href="https://allmcps.com/mcp/orion-celestia-intel"><img src="https://allmcps.com/api/badge/orion-celestia-intel?style=directory" alt="Orion Celestia Intel on AllMCPs" /></a>