# io.github.UnityNodes/blobpedia (remote · blobpedia.org)

Celestia knowledge base: CIPs, docs, forum, videos, GitHub, plus live on-chain state

- Trust score: 69/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `blobpedia.org`: 69/100 (this document), [markdown](https://verifymcp.io/servers/unitynodes-blobpedia/blobpedia.md), [page](https://verifymcp.io/servers/unitynodes-blobpedia/blobpedia)

## Channel facts

- Endpoint: `https://blobpedia.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 23 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2729 tokens (~118/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http unitynodes-blobpedia https://blobpedia.org/mcp
```

### Codex

```toml
[mcp_servers.unitynodes-blobpedia]
url = "https://blobpedia.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "unitynodes-blobpedia": {
      "type": "remote",
      "url": "https://blobpedia.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add unitynodes-blobpedia --url https://blobpedia.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  unitynodes-blobpedia:
    url: "https://blobpedia.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "unitynodes-blobpedia": {
      "type": "http",
      "url": "https://blobpedia.org/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

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

### 2026-08-02 (score 68, +1)

- [functional regression] Schema quality: excellent → unverified

### 2026-08-01 (score 67, +1)

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

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 64, +1)

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

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (23)

### `search` (~163 tokens)

Keyword/full-text search over the Celestia knowledge base (CIPs, Celestia/rollup/node docs, forum, whitepapers, blog, YouTube transcripts, celestiaorg GitHub issues/PRs, releases and Discussions). Celestia-specific — do NOT use for other blockchains (use the Ethereum or other-chain docs tool), the general web (use the web-search tool), other knowledge bases (use the dedicated RAG tool), or local files. Use this for exact-term or name lookups; use semantic_search for conceptual how-does-X-work questions, and get_doc to read a full page once you have its id.

Input parameters:

- `limit` (integer)
- `query` (string, required): Search query
- `type` (string)

### `get_cip` (~89 tokens)

Read the full text of one Celestia Improvement Proposal (CIP) by its id. Celestia governance docs only — not GitHub issues or arbitrary proposals (use a GitHub tool for those). Get the id from search or list_cips first.

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042", or "PR-0117"

### `list_cips` (~133 tokens)

Browse or filter Celestia Improvement Proposals (CIPs) by status (Draft, Review, Final) or type. Celestia governance proposals only — do NOT use this to list GitHub issues, pull requests, or proposals from other chains (use the GitHub MCP or that chains tool for those). Use get_cip to read one in full, get_cip_history for its status timeline, and get_cip_mentions for where it is discussed.

Input parameters:

- `limit` (integer)
- `status` (string)
- `type` (string): Type filter, e.g. "Standards Track"

### `get_discussion` (~78 tokens)

Read one Celestia community forum thread (forum.celestia.org) with its posts, by numeric topic id. This is the CELESTIA FORUM channel — not GitHub Discussions (use get_github_discussion). Get the id from search or get_cip_mentions.

Input parameters:

- `id` (integer, required): Forum topic ID

### `get_whitepaper` (~76 tokens)

Read the full text of one Celestia whitepaper or research PDF by slug. Celestia papers only — not arbitrary web PDFs (use a web-search tool for those). Call list_whitepapers first to get a valid slug.

Input parameters:

- `slug` (string, required): Whitepaper slug, e.g. "celestia-whitepaper"

### `list_whitepapers` (~54 tokens)

List the Celestia whitepapers and research PDFs indexed here (slug plus title). Celestia-specific — not arbitrary web PDFs (use a web-search tool for those). Use get_whitepaper to read one by slug.

### `get_trending` (~119 tokens)

Show which CELESTIA content is trending on blobpedia this week (most-viewed CIPs, forum threads, docs, etc.). This is a Celestia content-engagement signal only. It is NOT token price or market trends (for trending coins, gainers, or TIA price movement defer to the price/market MCP such as CoinGecko) and NOT general web or crypto-wide trends (defer to a web-search MCP). Only fire when the user is asking what is popular within Celestia content. Zero arguments.

### `get_doc` (~115 tokens)

Read the FULL text of one indexed Celestia documentation page by id (Celestia node and developer docs plus partner docs) — exact commands, flags, and whole sections a search snippet truncates. Best for Celestia operational/how-to questions. Celestia docs only — not docs of other projects (use that projects docs tool) and not the web (use a web-search tool). Get the id from search or semantic_search first.

Input parameters:

- `id` (integer, required): Doc page ID (from search/semantic_search results)

### `get_cip_history` (~83 tokens)

Show the status-change timeline of one Celestia Improvement Proposal (CIP) — when it moved Draft to Review to Final, etc. Celestia governance only. Needs a CIP id (from search or list_cips).

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042", or "PR-0117"

### `get_cip_attachments` (~78 tokens)

List file/PDF attachments of one Celestia Improvement Proposal (CIP) — e.g. signed vote records, supporting docs — by CIP id. Celestia governance only. Get the id from search or list_cips.

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042"

### `get_cip_mentions` (~108 tokens)

Find where a given Celestia Improvement Proposal (CIP) is referenced across blobpedia: forum threads, blog posts, celestiaorg GitHub issues and pull requests, and sibling CIPs. Celestia-specific cross-reference — use to see who is discussing a CIP and where. Needs a CIP id (from search or list_cips).

Input parameters:

- `id` (string, required): CIP ID: "0001", "CIP-0042", or "PR-0117"

### `get_recent_changes` (~102 tokens)

Timeline of what changed on Celestia recently across blobpedia (CIP status changes, new proposals, forum threads, blog posts, GitHub releases), newest first. Celestia activity only — not a GitHub commit feed (use a GitHub tool) and not general crypto news (use a web-search tool). Use get_trending for what is popular rather than what is new.

Input parameters:

- `days` (integer)
- `limit` (integer)

### `get_network_stats` (~91 tokens)

Counts of CELESTIA CONTENT indexed by blobpedia (how many CIPs, forum threads, docs, videos, etc.). This is INDEX/catalog coverage of what blobpedia has cataloged, NOT live chain state. For LIVE on-chain metrics (block height, TIA supply, validators, cumulative blob data) or TIA price/market, use get_network_state on THIS server instead. Zero arguments.

### `get_network_state` (~126 tokens)

Live Celestia ON-CHAIN state + TIA market, fetched in real time (source: Celenium indexer + CoinGecko): mainnet block height, total TIA supply, validator count, cumulative blob data posted, total txs/accounts/namespaces, plus TIA price, market cap and 24h change. Celestia mainnet only — this is the LIVE on-chain/price layer, distinct from get_network_stats (which counts indexed CONTENT, not chain state). Use this for current/live chain questions or TIA price right now. Zero arguments.

### `list_ecosystem_projects` (~115 tokens)

Browse the Celestia ecosystem catalog (rollups, DeFi, wallets, infrastructure, etc.), optionally filtered by category or keyword. Celestia ecosystem only — not a general crypto-project directory (use a web-search tool for that). Returns catalog entries, not live project data.

Input parameters:

- `category` (string): Filter by category (e.g. "DeFi", "Wallets", "NaaS")
- `limit` (integer)
- `query` (string): Search in title/description/tags

### `list_repos` (~65 tokens)

List the GitHub repositories that blobpedia has INDEXED for Celestia, with item counts. Read-only view of the Celestia index on this server — does NOT browse your GitHub account or arbitrary repos (use a dedicated GitHub tool for that). Zero arguments.

### `list_github_discussions` (~149 tokens)

List GitHub Discussions from Celestia repos (e.g. celestiaorg/docs) cached on this server, ranked by upvotes then recency. Celestia repos only, from the local cache — not arbitrary GitHub Discussions (use a dedicated GitHub tool for those). Use get_github_discussion for the full body plus comments of one thread; this is GitHub Discussions, not the community forum (use get_discussion).

Input parameters:

- `category` (string): Filter by Discussions category, e.g. "Q&A", "Ideas"
- `limit` (integer)
- `repo` (string): Filter by repo, e.g. "celestiaorg/docs"

### `get_github_discussion` (~178 tokens)

Read one Celestia GitHub Discussion (celestiaorg/docs and other Celestia repos) cached on THIS server — full body plus comments — by an id you got from list_github_discussions on this server. Celestia cache only: if the id was not returned by this servers list_github_discussions, or the request is just a raw GitHub node id (e.g. D_kw...) with no Celestia context, this is NOT the tool — use a dedicated GitHub tool for arbitrary GitHub Discussions. This is GitHub Discussions, not the community forum (use get_discussion). Pair it with list_github_discussions, which supplies the valid ids.

Input parameters:

- `id` (string, required): GitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..."

### `get_video` (~95 tokens)

Get one Celestia-related YouTube video cached on this server (metadata plus transcript), by video id. Celestia-only cache — does NOT fetch arbitrary YouTube videos or search YouTube at large (use a dedicated YouTube tool for that). Find ids via list_videos or search.

Input parameters:

- `id` (string, required): YouTube video id, e.g. "dQw4w9WgXcQ"

### `list_videos` (~179 tokens)

Browse Celestia-related YouTube videos cached on this server, filtered by channel/date/transcript availability. Celestia-only cache — does NOT search YouTube at large (use a dedicated YouTube tool for that). Metadata only; use get_video for the transcript of one video by id.

Input parameters:

- `channel` (string): Channel name filter, e.g. "Celestia", "Celestia Foundation", "Modular". Case-insensitive substring.
- `has_transcript` (boolean): If true, only return videos with a stored transcript. If false, only those still missing one. Omit for both.
- `limit` (integer)
- `offset` (integer)
- `since` (string): Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound.

### `get_foundation_info` (~172 tokens)

Who runs Celestia: leadership and team members of the Celestia Foundation and Celestia Labs — names, roles and background — plus the headline figures from the official celestia.org About page. Use for "who is the CEO/CTO", "who works on Celestia", or team-background questions. People and org facts only — this is NOT Celestia documentation (use search or get_doc), NOT CIPs or their discussion (use list_cips/get_cip and get_cip_mentions), and it holds no grant-programme, board-seat or membership records.

Input parameters:

- `limit` (integer)
- `topic` (string, required): Free-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board".

### `semantic_search` (~180 tokens)

Semantic (meaning-based) search over the Celestia knowledge base (CIPs, Celestia/rollup/node docs, forum, whitepapers, blog, releases, ecosystem, YouTube transcripts, celestiaorg GitHub issues/PRs). Celestia-specific — do NOT use for other blockchains (use the Ethereum or other-chain docs tool), the general web (use the web-search tool), other knowledge bases (use the dedicated RAG tool), or local files. Use this for conceptual how-does-X-work questions; use search for exact-term or name lookups, and get_doc to read a full page once you have its id.

Input parameters:

- `limit` (integer)
- `query` (string, required): Free-form question or phrase.
- `source_types` (array): Restrict to these source types. Omit for all.

### `get_started_guide` (~181 tokens)

Personalized onboarding for building ON CELESTIA — running a node, posting a blob, or deploying a rollup that uses Celestia for data availability. ALWAYS use this when a developer asks how to get started or build ON CELESTIA (prefer it over the Celestia search tool for those questions). ASK the user about their background FIRST (rollup_dev, node_operator, app_dev, researcher, new_to_celestia), then return a path with docs.celestia.org links. Celestia-only — NOT for getting started with non-Celestia frameworks, languages, or dev tools (React, Node.js, generic blockchain onboarding, etc.); for those defer to a general docs or web-search tool.

Input parameters:

- `background` (string, required): Developer's primary goal. Ask the user to pick one before proceeding.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/unitynodes-blobpedia/blobpedia#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://blobpedia.org/mcp
- Repository: https://github.com/UnityNodes/blobpedia
- Website: https://blobpedia.org/for-ai
- Changelog RSS feed: https://verifymcp.io/servers/unitynodes-blobpedia/blobpedia/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/unitynodes-blobpedia/blobpedia/changelog.json
- HTML version of this page: https://verifymcp.io/servers/unitynodes-blobpedia/blobpedia