How do I install Orion Celestia Intel?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Orion Celestia Intel need an API key?

No required environment variable is listed on this record.

What transport does Orion Celestia Intel use?

Orion Celestia Intel is reached over HTTP.

When was Orion Celestia Intel last checked?

Last checked 2026-11-07. Celestia network intelligence for AI agents: daily analysis, anomaly signals and DA metrics.

Orion Celestia Intel MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://orionlabsone.cc/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http cc.orionlabsone-orion-agent-kit https://orionlabsone.cc/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "cc.orionlabsone-orion-agent-kit": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://orionlabsone.cc/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Orion Agent Kit

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

What this is

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.

Tools

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

Resources & prompts

Beyond tools, the server exposes MCP resources an agent can read or subscribe to:

orion://latest — the most recent daily report
orion://reports — the archive index
orion://report/{date} — any archived report by date

…and ready-made prompts to guide an agent:

daily_celestia_briefing — produce a grounded, source-cited daily briefing
rollup_da_check — survey who dominates blobspace and the current DA cost context

What counts as a signal

Orion'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:

DA utilization & fees — per-block volume and fees over the last day vs the recent daily baseline
Blob-volume z-score — statistical spikes/drops in data posted
Namespace shift — only when the DA leader changes or its share moves materially
Staking & concentration — bonded-ratio moves, Nakamoto-coefficient changes, new jailings
Market & protocol — notable TIA price moves, active governance proposals, new celestia-app releases

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.

Quick start — hosted endpoint (no install)

The MCP server runs at https://orionlabsone.cc/mcp.

Claude Code

claude mcp add --transport http orion https://orionlabsone.cc/mcp

Cursor — add to .cursor/mcp.json (already included if you cloned this repo):

{ "mcpServers": { "orion": { "url": "https://orionlabsone.cc/mcp" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "orion": { "type": "http", "url": "https://orionlabsone.cc/mcp" } } }

Claude Desktop / Codex / Windsurf / Cline / any stdio-only client — bridge with mcp-remote:

{
  "mcpServers": {
    "orion": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://orionlabsone.cc/mcp"]
    }
  }
}

Per-client walkthroughs: Claude Code · Claude Desktop · Cursor · Codex · VS Code

Quick start — clone & chat

git clone https://github.com/orioninfra/orion-agent-kit
cd orion-agent-kit
npm install
claude   # Claude Code picks up .mcp.json automatically

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.

Run the server yourself

npm install
npm run start          # Streamable HTTP on 127.0.0.1:8791/mcp
npm run start:stdio    # stdio transport (for local MCP clients)
npm run smoke          # end-to-end check of the tools against the live API
npm run typecheck      # type-check the sources

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).

REST, without MCP

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

How it fits together

AI agent (Claude / GPT / any MCP client)
   │  MCP — read-only analysis tools, resources & prompts
   ▼
orion-agent-kit  ──►  Orion daily analysis (orionlabsone.cc/api)
        │                 │  every figure linked to its source
        │                 ▼
        │             Celestia LCD · market data
        └──────────►  Celenium API   (live namespace & validator drill-down)

Orion Celestia Intel

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Orion Celestia Intel?

Does Orion Celestia Intel need an API key?

What transport does Orion Celestia Intel use?

When was Orion Celestia Intel last checked?

Documentation

Orion Agent Kit

What this is

Tools

Resources & prompts

What counts as a signal

Quick start — hosted endpoint (no install)

Quick start — clone & chat

Run the server yourself

REST, without MCP

How it fits together

License