Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

[mcp_servers.blobpedia]
url = "https://blobpedia.org/mcp"

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

{
  "mcpServers": {
    "blobpedia": {
      "type": "http",
      "url": "https://blobpedia.org/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=blobpedia&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYmxvYnBlZGlhLm9yZy9tY3AifQ%3D%3D"
}

{
  "servers": {
    "blobpedia": {
      "type": "http",
      "url": "https://blobpedia.org/mcp"
    }
  }
}

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

extensions:
  "blobpedia":
    enabled: true
    name: "blobpedia"
    type: streamable_http
    uri: "https://blobpedia.org/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene71 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_github_discussions (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_similar_projects (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); learning_path (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 6,833 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

44 tools, about 6,833 tokens to load them all · tool set 781328f5e45f · checked 2026-10-09 23:53 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 94 / 100

provenance90

liveness99

freshness85

hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-99% ~updated-82d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://blobpedia.org/mcp` streamable-http	none	yes	99%	501 ms	2025-11-25	2026-10-09

Tools (44)

`detect_cip_dependency_chain`	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.
`detect_drift`	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.
`diagnose_error`	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.
`ecosystem_dependency_graph`	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?".
`find_cip_for_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?".
`find_code_examples`	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.
`find_collaboration_opportunities`	Given one Celestia ecosystem project, find others with complementary tags/category that could plug in. Celestia-specific. Lightweight heuristic: overlap of tags + adjacent categories.
`find_expert`	Rank likely Celestia experts on a topic across blobpedia: forum activity matching the topic, plus overall forum volume of that author. Celestia-specific.
`find_known_issues`	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.
`find_maintainer_guidance`	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.
`find_security_patches`	Surface release notes likely to contain security or CVE fixes. Celestia-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.
`find_similar_projects`	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.
`get_breaking_changes`	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").
`get_cip`	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.
`get_cip_attachments`	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.
`get_cip_history`	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).
`get_cip_mentions`	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).
`get_discussion`	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.
`get_doc`	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.
`get_foundation_info`	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.
`get_github_discussion`	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.
`get_issue_status`	Look up one GitHub issue or PR by repo + number. Celestia repos only.
`get_latest_release`	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.
`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.
`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.
`get_radar`	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.
`get_recent_changes`	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.
`get_sdk_changelog`	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.
`get_started_guide`	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.
`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.
`get_video`	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.
`get_whitepaper`	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.
`learning_path`	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).
`list_cips`	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.
`list_ecosystem_projects`	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.
`list_github_discussions`	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).
`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.
`list_videos`	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.
`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.
`search`	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.
`search_github_issues`	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".
`search_release_notes`	Search across release-notes bodies of all indexed Celestia repos for a feature/keyword. Celestia-specific. Use to find which release first mentioned X.
`search_talks`	Search blobpedia's indexed Celestia talks/videos (YouTube transcripts). Celestia-specific. Returns matches across title + transcript with a short snippet around the hit.
`semantic_search`	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.

Schemas: list_tools.

Official server.json

{
  "name": "io.github.UnityNodes/blobpedia",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://blobpedia.org/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/UnityNodes/blobpedia",
    "source": "github"
  },
  "websiteUrl": "https://blobpedia.org/for-ai",
  "description": "Celestia knowledge base: CIPs, docs, forum, videos, GitHub, plus live on-chain state"
}