Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Orion Celestia Intel

REMOTE · ORIONLABSONE.CC · SCANNED SEP 20

Celestia network intelligence for AI agents: daily analysis, anomaly signals and DA metrics.

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 758 tokens (~58/item across 13 items; 11 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Orion Celestia Intel MCP server?

Orion Celestia Intel is a hosted endpoint at https://orionlabsone.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · orionlabsone.cc

# add to Claude Code
claude mcp add --transport http cc-orionlabsone-orion-agent-kit 'https://orionlabsone.cc/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cc-orionlabsone-orion-agent-kit": {
      "url": "https://orionlabsone.cc/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cc-orionlabsone-orion-agent-kit": {
      "type": "http",
      "url": "https://orionlabsone.cc/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cc-orionlabsone-orion-agent-kit]
url = "https://orionlabsone.cc/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cc-orionlabsone-orion-agent-kit": {
      "type": "remote",
      "url": "https://orionlabsone.cc/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cc-orionlabsone-orion-agent-kit --url 'https://orionlabsone.cc/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cc-orionlabsone-orion-agent-kit:
    url: "https://orionlabsone.cc/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cc-orionlabsone-orion-agent-kit": {
      "Transport": "http",
      "Url": "https://orionlabsone.cc/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cc-orionlabsone-orion-agent-kit -t streamable-http -u 'https://orionlabsone.cc/mcp'
// mcp.json
{
  "mcpServers": {
    "cc-orionlabsone-orion-agent-kit": {
      "type": "http",
      "url": "https://orionlabsone.cc/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 12 Sept 26 +1
    • Stability: 0.97 → pass security
  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Aug 26 −7
    • HSTS header: unverified → fail security
    • Injection markers: unverified → pass security
    • TLS certificate: unverified → pass security
    • Transport: fail → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: unreachable → reachable functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.53 functional
    • Schema quality: unverified → 100 functional
    • MCP protocol: unverified → pass functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://orionlabsone.cc/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=orionlabsone.cc CN=YE1,O=Let's Encrypt,C=US 12 Aug 2026 10 Nov 2026 ECDSA 256 ECDSA-SHA384 6757da6e0a2fd274e92135f4e5356fd7f3d
SANs: orionlabsone.cc, www.orionlabsone.cc
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of orionlabsone.cc. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cc. present 12593 13 Verified
orionlabsone.cc. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://orionlabsone.cc/mcp Verified 200
http (plaintext) http://orionlabsone.cc/mcp HTTPS enforced 301 https://orionlabsone.cc/mcp
MCP tools · 11 exposed · ~720 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_daily_brief ~91

Orion's latest daily analysis of the Celestia mainnet: headline, anomaly signals with severity, key network metrics, and provenance links for every figure. Start here for 'what is happening on Celestia today?'. Set include_narrative for Orion's written prose summary.

NameTypeReqDescription
include_narrativebooleanAlso return Orion's written prose narrative (markdown, with a citation check)

No output schema declared.

No examples provided.

get_metric_history ~95

Time series of one snapshot metric across Orion's daily reports, oldest to newest. Metrics: height, total_fee_tia, total_blobs_tb, total_tx, total_validators, active_validators, tia_price, bonded_ratio, bonded_ratio_supply, nakamoto_halting, jail_count.

NameTypeReqDescription
daysintegerHow many recent days (default 30)
metricstringyesWhich snapshot metric to chart

No output schema declared.

No examples provided.

get_namespace ~60

Detail for a single Celestia namespace by its namespace_id (hex — get one from get_top_namespaces): size, blob count, last activity.

NameTypeReqDescription
namespace_idstringyesNamespace id (hex), e.g. from get_top_namespaces

No output schema declared.

No examples provided.

get_network_state ~55

Current Celestia mainnet metrics from Orion's latest snapshot: height, DA volume (TB), fees, validators (active vs registered), staking ratios, Nakamoto coefficient, jail count, TIA price — with provenance links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_report ~49

Full Orion report for a specific date (YYYY-MM-DD): snapshot metrics, all signals, summary, provenance.

NameTypeReqDescription
datestringyesReport date YYYY-MM-DD (see list_reports for available dates)

No output schema declared.

No examples provided.

get_signals ~91

Anomaly/health signals detected by Orion for a given day (default: latest). Each signal has type, severity (info|notable|critical), observed value vs rolling baseline, and its data source. Filter with min_severity.

NameTypeReqDescription
datestringReport date YYYY-MM-DD; omit for the latest report
min_severitystringOnly signals at or above this severity

No output schema declared.

No examples provided.

get_top_namespaces ~56

Largest namespaces (rollups) on Celestia by total blob size, live from Celenium. Shows who is posting the most data to the DA layer.

NameTypeReqDescription
limitintegerHow many namespaces (default 10)

No output schema declared.

No examples provided.

get_top_validators ~49

Largest Celestia validators by stake, live from Celenium: moniker, stake (TIA), commission, jailed status.

NameTypeReqDescription
limitintegerHow many validators (default 20)

No output schema declared.

No examples provided.

get_trends ~42

Day-over-day and week-over-week change for key Celestia metrics, computed from Orion's daily snapshots. Answers 'what changed since yesterday / last week?'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_reports ~41

Index of Orion's daily Celestia reports (date + signal counts), newest first.

NameTypeReqDescription
limitintegerMax entries to return (default 30)

No output schema declared.

No examples provided.

search_reports ~91

Keyword search across recent daily reports (signal titles, details, types, metrics). Returns matching signals grouped by date. Plain keyword scan — no LLM in the loop, results are verbatim from the archive.

NameTypeReqDescription
limitintegerHow many recent reports to scan (default 14)
querystringyesKeyword or phrase, e.g. 'eclipse', 'block time', 'namespace'

No output schema declared.

No examples provided.

Common questions

What is the Orion Celestia Intel MCP server?

Orion Celestia Intel is an MCP server listed in the public MCP registry as cc.orionlabsone/orion-agent-kit. Celestia network intelligence for AI agents: daily analysis, anomaly signals and DA metrics. This page covers its hosted endpoint (https://orionlabsone.cc/mcp).

Is the Orion Celestia Intel MCP server safe to use?

Orion Celestia Intel scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Orion Celestia Intel MCP server expose?

Orion Celestia Intel exposes 11 tools: get_daily_brief, get_signals, get_network_state, list_reports, get_report, and 6 more. Their descriptions and schemas cost roughly 720 tokens of context every time the server is loaded.

Does the Orion Celestia Intel MCP server require authentication?

No. We connected to Orion Celestia Intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Orion Celestia Intel MCP server still maintained?

Orion Celestia Intel is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.