blobpedia

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

Should I use this

Quality & Safety

A
Description quality
95%
Schema completeness
89%
Naming quality
97%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (5)

  • LOWTool 'find_security_patches' description lacks action verbin find_security_patches
  • LOWTool 'find_maintainer_guidance' description lacks action verbin find_maintainer_guidance
  • LOWTool 'get_issue_status' description lacks action verbin get_issue_status
  • LOWTool 'find_expert' description lacks action verbin find_expert
  • LOWTool 'find_collaboration_opportunities' name length outside 3-30 rangein find_collaboration_opportunities

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~7,145Tokens (tool definitions)
~899 BTypical response size
Significant attention impact (5.58% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "blobpedia": {
      "url": "https://blobpedia.org/mcp"
    }
  }
}

Remote endpoints

https://blobpedia.org/mcpstreamable-http

What it can do

Tool inventory

Tools (44)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search(query, type, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query"
    },
    "type": {
      "default": "all",
      "type": "string",
      "enum": [
        "all",
        "cip",
        "doc",
        "discussion",
        "whitepaper",
        "blog",
        "youtube",
        "github"
      ]
    },
    "limit": {
      "default": 10,
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_cip(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "CIP ID: \"0001\", \"CIP-0042\", or \"PR-0117\""
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_cips(status, type, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "status": {
      "default": "all",
      "type": "string",
      "enum": [
        "Approved",
        "Final",
        "Active",
        "Living",
        "In Review",
        "Review",
        "Proposed",
        "Last Call",
        "Draft",
        "Stagnant",
        "Withdrawn",
        "Rejected",
        "Replaced",
        "Obsolete",
        "Superseded",
        "Implemented",
        "all"
      ]
    },
    "type": {
      "description": "Type filter, e.g. \"Standards Track\"",
      "type": "string"
    },
    "limit": {
      "default": 20,
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_discussion(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991,
      "description": "Forum topic ID"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_whitepaper(slug)

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 Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Whitepaper slug, e.g. \"celestia-whitepaper\""
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_whitepapers

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_trending

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_doc(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991,
      "description": "Doc page ID (from search/semantic_search results)"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡get_cip_history(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "CIP ID: \"0001\", \"CIP-0042\", or \"PR-0117\""
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_cip_attachments(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "CIP ID: \"0001\", \"CIP-0042\""
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_cip_mentions(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "CIP ID: \"0001\", \"CIP-0042\", or \"PR-0117\""
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_recent_changes(days, limit)

Timeline of what changed on Celestia recently across blobpedia (new/changed CIPs, forum threads, blog posts, GitHub releases, radar alerts), 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 Schema

{
  "type": "object",
  "properties": {
    "days": {
      "default": 7,
      "type": "integer",
      "minimum": 1,
      "maximum": 90
    },
    "limit": {
      "default": 50,
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_network_stats

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_network_state

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_ecosystem_projects(category, query, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "category": {
      "description": "Filter by category (e.g. \"DeFi\", \"Wallets\", \"NaaS\")",
      "type": "string"
    },
    "query": {
      "description": "Search in title/description/tags",
      "type": "string"
    },
    "limit": {
      "default": 30,
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_repos

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_github_discussions(repo, category, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "repo": {
      "description": "Filter by repo, e.g. \"celestiaorg/docs\"",
      "type": "string"
    },
    "category": {
      "description": "Filter by Discussions category, e.g. \"Q&A\", \"Ideas\"",
      "type": "string"
    },
    "limit": {
      "default": 15,
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_github_discussion(id)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "GitHub GraphQL node ID, e.g. \"D_kwDOMNgu5s4AY...\""
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_video(id, transcript_chars)

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 Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "YouTube video id, e.g. \"dQw4w9WgXcQ\""
    },
    "transcript_chars": {
      "default": 12000,
      "description": "Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only.",
      "type": "integer",
      "minimum": 0,
      "maximum": 200000
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_videos(channel, since, has_transcript, limit, offset)

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 Schema

{
  "type": "object",
  "properties": {
    "channel": {
      "description": "Channel name filter, e.g. \"Celestia\", \"Celestia Foundation\", \"Modular\". Case-insensitive substring.",
      "type": "string"
    },
    "since": {
      "description": "Earliest published_at (ISO date, e.g. \"2026-01-01\"). Default: no lower bound.",
      "type": "string"
    },
    "has_transcript": {
      "description": "If true, only return videos with a stored transcript. If false, only those still missing one. Omit for both.",
      "type": "boolean"
    },
    "limit": {
      "default": 20,
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    },
    "offset": {
      "default": 0,
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_foundation_info(topic, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "Free-text topic, e.g. \"team\", \"executive director\", \"working groups\", \"membership\", \"grants\", \"board\"."
    },
    "limit": {
      "default": 3,
      "type": "integer",
      "minimum": 1,
      "maximum": 10
    }
  },
  "required": [
    "topic"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢semantic_search(query, source_types, limit)

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 Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "Free-form question or phrase."
    },
    "source_types": {
      "description": "Restrict to these source types. Omit for all.",
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "cip",
          "doc_page",
          "forum_topic",
          "github_item",
          "whitepaper",
          "blog_post",
          "github_release",
          "github_discussion",
          "ecosystem_project",
          "foundation_kb",
          "youtube_video",
          "radar_item"
        ]
      }
    },
    "limit": {
      "default": 6,
      "type": "integer",
      "minimum": 1,
      "maximum": 15
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_started_guide(background)

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 Schema

{
  "type": "object",
  "properties": {
    "background": {
      "type": "string",
      "enum": [
        "rollup_dev",
        "node_operator",
        "app_dev",
        "researcher",
        "new_to_celestia"
      ],
      "description": "Developer's primary goal. Ask the user to pick one before proceeding."
    }
  },
  "required": [
    "background"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢search_github_issues(query, state, limit, offset)

Full-text search across blobpedia's indexed GitHub issues across Celestia repos. Celestia ecosystem only. Use to find prior reports, open bugs, or requested features. For a broader cross-corpus search use the `search` tool with type="github".

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "Free-text query."
    },
    "state": {
      "description": "Issue state filter (default: all).",
      "type": "string",
      "enum": [
        "open",
        "closed",
        "all"
      ]
    },
    "limit": {
      "default": 10,
      "description": "Max rows (default 10).",
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    },
    "offset": {
      "default": 0,
      "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢search_talks(query, limit, offset)

Search blobpedia's indexed Celestia talks/videos (YouTube transcripts). Celestia-specific. Returns matches across title + transcript with a short snippet around the hit.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "Free-text query. Appears in title or transcript."
    },
    "limit": {
      "default": 5,
      "description": "Max rows (default 5).",
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    },
    "offset": {
      "default": 0,
      "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢search_release_notes(feature)

Search across release-notes bodies of all indexed Celestia repos for a feature/keyword. Celestia-specific. Use to find which release first mentioned X.

Input Schema

{
  "type": "object",
  "properties": {
    "feature": {
      "type": "string",
      "minLength": 2,
      "description": "Feature keyword, e.g. \"blob size limit\", \"namespace\", \"data availability sampling\"."
    }
  },
  "required": [
    "feature"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡find_security_patches(limit)

Surface release notes likely to contain security or CVE fixes. Celestia-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.

Input Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "default": 10,
      "description": "Max rows (default 10).",
      "type": "integer",
      "minimum": 1,
      "maximum": 30
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_maintainer_guidance(topic)

Surface forum posts authored by top-volume Celestia forum contributors (likely maintainers/core team) on a topic. Celestia-specific. Use when you want to weight expert voices over the general forum.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "minLength": 2,
      "description": "Topic keyword, e.g. \"namespace\", \"light node sync\", \"blob submission\"."
    }
  },
  "required": [
    "topic"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_issue_status(repo, number)

Look up one GitHub issue or PR by repo + number. Celestia repos only.

Input Schema

{
  "type": "object",
  "properties": {
    "repo": {
      "type": "string",
      "description": "Repo, e.g. \"celestiaorg/celestia-app\" or shorthand \"celestia-app\"."
    },
    "number": {
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991,
      "description": "Issue or PR number."
    }
  },
  "required": [
    "repo",
    "number"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_code_examples(topic, limit, offset)

Find Celestia code snippets in forum posts on a topic. Filters forum_posts where the rendered HTML contains `<pre>` or `<code>` blocks AND matches the topic keyword. Celestia-specific.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "minLength": 2,
      "description": "Topic keyword."
    },
    "limit": {
      "default": 5,
      "description": "Max rows (default 5).",
      "type": "integer",
      "minimum": 1,
      "maximum": 15
    },
    "offset": {
      "default": 0,
      "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "topic"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_expert(topic, limit)

Rank likely Celestia experts on a topic across blobpedia: forum activity matching the topic, plus overall forum volume of that author. Celestia-specific.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "minLength": 2,
      "description": "Topic / domain to find experts for."
    },
    "limit": {
      "default": 5,
      "description": "Max authors (default 5).",
      "type": "integer",
      "minimum": 1,
      "maximum": 15
    }
  },
  "required": [
    "topic"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪ecosystem_dependency_graph(topic)

Map ecosystem_projects matching a topic to the GitHub repos that mention them, building a quick "who references these projects" picture. Celestia-specific. Useful for "who else is building around X?".

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "minLength": 2,
      "description": "Topic / category / project family."
    }
  },
  "required": [
    "topic"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_collaboration_opportunities(project)

Given one Celestia ecosystem project, find others with complementary tags/category that could plug in. Celestia-specific. Lightweight heuristic: overlap of tags + adjacent categories.

Input Schema

{
  "type": "object",
  "properties": {
    "project": {
      "type": "string",
      "minLength": 2,
      "description": "Project name or slug to look around."
    }
  },
  "required": [
    "project"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢diagnose_error(error_text, limit)

Paste a Celestia ERROR MESSAGE, stack trace, or error code and get the most likely resolved fixes from blobpedia history: forum threads where the same error was discussed, and related GitHub issues (each with its own date). Needs a literal error string or code; do NOT use it for symptom descriptions with no error text (e.g. "my node won't sync"), use semantic_search for those. Celestia-specific. Returns top matches from forum and github.

Input Schema

{
  "type": "object",
  "properties": {
    "error_text": {
      "type": "string",
      "minLength": 8,
      "description": "Error message, stack trace, or status code. Longer/more distinctive text returns better matches."
    },
    "limit": {
      "default": 3,
      "description": "Max matches per source (default 3).",
      "type": "integer",
      "minimum": 1,
      "maximum": 10
    }
  },
  "required": [
    "error_text"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_breaking_changes(from_sdk, to_sdk, repo)

Compare two versions of one Celestia repo and return the release notes between them, plus any forum threads near the release window. Celestia-specific. Use when a developer is planning an upgrade and asks "what breaks moving from X to Y?". Pass version strings as they appear in github_releases tags (with or without the leading "v").

Input Schema

{
  "type": "object",
  "properties": {
    "from_sdk": {
      "type": "string",
      "description": "Origin version, e.g. \"9.0.0\" or \"v9.0.0\"."
    },
    "to_sdk": {
      "type": "string",
      "description": "Target version, e.g. \"9.1.0\" or \"v9.1.0\"."
    },
    "repo": {
      "description": "Optional repo hint: \"app\", \"node\", \"core\", \"rollkit\", \"openrpc\", or a full owner/name. Defaults to celestia-app.",
      "type": "string"
    }
  },
  "required": [
    "from_sdk",
    "to_sdk"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪detect_cip_dependency_chain(cip_id)

Walk the CIP `requires:` graph from a starting CIP or PR draft. Returns the full chain of prerequisites that must reach a settled status before the starting proposal becomes implementable, with each prerequisite's current status. Accepts both merged CIPs ("CIP-0005", "5") and open-PR drafts ("PR-203"). Celestia governance only. Use when planning around a CIP that hasn't shipped yet.

Input Schema

{
  "type": "object",
  "properties": {
    "cip_id": {
      "type": "string",
      "description": "Starting CIP or PR id, e.g. \"5\", \"CIP-0005\", or \"PR-203\"."
    }
  },
  "required": [
    "cip_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_sdk_changelog(version, repo)

Fetch the release-notes body for one version across celestia-app / celestia-node / celestia-core / rollkit / celestia-openrpc. Celestia-specific. Returns the rendered release body with a link to the GitHub release.

Input Schema

{
  "type": "object",
  "properties": {
    "version": {
      "type": "string",
      "description": "Version tag, e.g. \"9.0.6\", \"v9.0.6\"."
    },
    "repo": {
      "description": "Optional repo hint: app, node, core, rollkit, openrpc.",
      "type": "string"
    }
  },
  "required": [
    "version"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_known_issues(description, limit)

Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues. Answers "is anyone else hitting this?". Celestia-specific. Does NOT return fixes, solutions, config, or how-to steps, and returns nothing when no open issue matches; for "how do I fix / configure / why does X happen" use semantic_search (then get_doc) instead.

Input Schema

{
  "type": "object",
  "properties": {
    "description": {
      "type": "string",
      "minLength": 8,
      "description": "What you're seeing. Short prose, not a stack trace (for that use diagnose_error)."
    },
    "limit": {
      "default": 5,
      "description": "Max rows per source (default 5).",
      "type": "integer",
      "minimum": 1,
      "maximum": 15
    }
  },
  "required": [
    "description"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_cip_for_feature(feature)

Given a Celestia feature or capability description, find the matching CIP(s) by searching titles and bodies. Celestia-specific. Use to answer "is there a CIP for X?".

Input Schema

{
  "type": "object",
  "properties": {
    "feature": {
      "type": "string",
      "minLength": 2,
      "description": "Feature description, e.g. \"blob size limit\", \"namespace format\", \"light client sampling\"."
    }
  },
  "required": [
    "feature"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡get_latest_release(package)

Get the single latest release (version tag, publish date, and GitHub release-notes link) for ONE NAMED Celestia repo: app, node, core, rollkit, or openrpc. Celestia-specific. Requires a package name as input.

Input Schema

{
  "type": "object",
  "properties": {
    "package": {
      "type": "string",
      "description": "Repo or package name: \"app\", \"node\", \"core\", \"rollkit\", \"openrpc\", or a full owner/repo."
    }
  },
  "required": [
    "package"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_radar(level, limit, offset)

Get the Celestia Radar, blobpedia's curated feed of time-sensitive ecosystem alerts: breaking changes, upgrade deadlines, protocol changes and required node-operator/rollup actions, each with deadline, affected components and source link. Filter by level (critical/important/ecosystem/all). Celestia-only. Use when a user asks what's changing, what's about to break, or what deadlines are approaching on Celestia.

Input Schema

{
  "type": "object",
  "properties": {
    "level": {
      "default": "all",
      "description": "Severity floor. \"critical\" and \"important\" return only that level; \"ecosystem\" is the low-severity feed; \"all\" (default) returns every live alert.",
      "type": "string",
      "enum": [
        "all",
        "critical",
        "important",
        "ecosystem"
      ]
    },
    "limit": {
      "default": 25,
      "description": "How many alerts to return, most severe and most recent first. Default 25.",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    },
    "offset": {
      "default": 0,
      "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢find_similar_projects(description, limit, offset)

Find Celestia ecosystem projects most similar to a free-text description by matching across title + category + description + tags. Celestia-specific. Useful before proposing a project to check overlap with what already exists.

Input Schema

{
  "type": "object",
  "properties": {
    "description": {
      "type": "string",
      "minLength": 4,
      "description": "Project description / idea."
    },
    "limit": {
      "default": 10,
      "description": "Max rows (default 10).",
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    },
    "offset": {
      "default": 0,
      "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "description"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢detect_drift(topic)

Find contradictions between docs, forum and GitHub on a topic. Returns counts of how each surface talks about it plus the most recent doc-page and forum statement so the caller can spot mismatches.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "minLength": 2,
      "description": "Topic to cross-check."
    }
  },
  "required": [
    "topic"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢learning_path(goal)

Construct a structured Celestia onboarding sequence for a stated goal: whitepaper → relevant docs → CIPs to know → forum starter threads → talks. Celestia-specific. Topic-driven (distinct from get_started_guide, which is background-driven).

Input Schema

{
  "type": "object",
  "properties": {
    "goal": {
      "type": "string",
      "minLength": 2,
      "description": "What the learner wants to do, e.g. \"run a light node\", \"post a blob\", \"understand DAS\"."
    }
  },
  "required": [
    "goal"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded44 tools
verifiedversion not recorded44 tools