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.

io.github.UnityNodes/blobpedia

REMOTE · BLOBPEDIA.ORG

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

Available components

0 this week 79 Trust /100

Last scanned (12 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security63
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 10874 tokens (~162/item across 67 items; 67 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 67 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 67 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 67 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 16 Nov 26 0
    • Tool “get_celestia_hardware_usage” rewrote its description, which is the text the model reads security
    • Tool “size_fibre_node” rewrote its description, which is the text the model reads security
    • “size_fibre_node” reworded the description of “throughput” cosmetic
  • 13 Nov 26 0
    • Tool “get_celestia_hardware_usage” rewrote its description, which is the text the model reads security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 79
    • New tool “get_celestia_validator_guide” functional
    • New tool “list_celestia_resources” 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 21 Nov 2026 · Probed https://blobpedia.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=blobpedia.org CN=WE1,O=Google Trust Services,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA256 bc30ec816f73945a0ee39836585afaff
SANs: blobpedia.org, *.blobpedia.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of blobpedia.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
blobpedia.org. No DS 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
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://blobpedia.org/mcp Verified 200
http (plaintext) http://blobpedia.org/mcp HTTPS enforced 308 https://blobpedia.org/mcp
MCP tools · 67 exposed · ~10,874 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
detect_cip_dependency_chain ~128

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.

NameTypeReqDescription
cip_idstringyesStarting CIP or PR id, e.g. "5", "CIP-0005", or "PR-203".

No output schema declared.

No examples provided.

detect_drift ~59

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.

NameTypeReqDescription
topicstringyesTopic to cross-check.

No output schema declared.

No examples provided.

diagnose_error ~144

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.

NameTypeReqDescription
error_textstringyesError message, stack trace, or status code. Longer/more distinctive text returns better matches.
limitinteger–Max matches per source (default 3).

No output schema declared.

No examples provided.

ecosystem_dependency_graph ~64

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?".

NameTypeReqDescription
topicstringyesTopic / category / project family.

No output schema declared.

No examples provided.

find_cip_for_feature ~76

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?".

NameTypeReqDescription
featurestringyesFeature description, e.g. "blob size limit", "namespace format", "light client sampling".

No output schema declared.

No examples provided.

find_code_examples ~101

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.

NameTypeReqDescription
limitinteger–Max rows (default 5).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
topicstringyesTopic keyword.

No output schema declared.

No examples provided.

find_collaboration_opportunities ~59

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

NameTypeReqDescription
projectstringyesProject name or slug to look around.

No output schema declared.

No examples provided.

find_expert ~68

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

NameTypeReqDescription
limitinteger–Max authors (default 5).
topicstringyesTopic / domain to find experts for.

No output schema declared.

No examples provided.

find_known_issues ~137

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.

NameTypeReqDescription
descriptionstringyesWhat you're seeing. Short prose, not a stack trace (for that use diagnose_error).
limitinteger–Max rows per source (default 5).

No output schema declared.

No examples provided.

find_maintainer_guidance ~77

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.

NameTypeReqDescription
topicstringyesTopic keyword, e.g. "namespace", "light node sync", "blob submission".

No output schema declared.

No examples provided.

find_security_patches ~57

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

NameTypeReqDescription
limitinteger–Max rows (default 10).

No output schema declared.

No examples provided.

find_similar_projects ~106

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.

NameTypeReqDescription
descriptionstringyesProject description / idea.
limitinteger–Max rows (default 10).
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

No output schema declared.

No examples provided.

get_breaking_changes ~178

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

NameTypeReqDescription
from_sdkstringyesOrigin version, e.g. "9.0.0" or "v9.0.0".
repostring–Optional repo hint: "app", "node", "core", "rollkit", "openrpc", or a full owner/name. Defaults to celestia-app.
to_sdkstringyesTarget version, e.g. "9.1.0" or "v9.1.0".

No output schema declared.

No examples provided.

get_celestia_decentralization ~135

How concentrated Celestia validation and data availability are, from Unity Nodes Pulse: the hosting providers and countries that carry the most validator voting power, how much voting power has no known host, and the public bridge nodes (status, version, uptime, host). Mainnet or the Mocha testnet (bridge nodes are mainnet only). Celestia only, a snapshot refreshed every 15 minutes. Host names come from a network crawl and can be wrong for validators that sit behind sentries. To choose where to run a node use list_datacenter_providers.

NameTypeReqDescription
networkstring––

No output schema declared.

No examples provided.

get_celestia_economics ~145

Celestia staking economics and what it costs to run a validator, from Unity Nodes Pulse: staking APR, inflation, the share of supply that is staked, annual provisions, Pulse's reference monthly server costs per hosting provider (minimum, recommended and archive tiers), the stake at which a validator on each provider breaks even at an assumed 20% commission, and the estimated monthly operator earnings of the largest validators. Mainnet only, a snapshot refreshed every 15 minutes. The reference hardware prices are curated by Unity Nodes and can lag the market: for live server prices use list_datacenter_offers. For the TIA price use get_network_state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_celestia_hardware_usage ~507

What the Celestia nodes that Unity Nodes runs actually use, measured on its own servers and shown beside Celestia's recommended hardware, from Unity Nodes Pulse: CPU cores (median, 95th percentile and maximum), RAM of the processes, network and disk I/O (median and 95th percentile; the disk I/O says how many hours of samples it rests on when that is less than the node has), the data size with its change per day and its growth carried forward (per day, in 90 days, when the disk would fill), an estimate of the network traffic per month, and for the Fibre service how full its shard store is against its budget and how many shards it uploaded and served in the window (successful and failed apart), for each node role that has a node (validator, consensus node, bridge, Fibre, light node, Fibre included on mainnet and on Mocha), each node named by its role and CPU, over 1, 7 or 30 days. Measured values, with clearly labelled estimates kept apart from them (the Celestia Foundation's Fibre calculator for Unity Nodes' voting power and, on mainnet, Celestia's own planning scenario for bridge data): the chain's own load in the same window (block data per second at the median, 95th percentile and maximum) beside the block limit read from the chain, the average block time and how much of that capacity the load fills, with a correlation r of each node's CPU, network and disk load with it (a link in how they moved, not a cause; only loads with a link are listed, and it is shown once four hours overlap), and the answer says how much of the window the samples fill (the fewest samples of any node times the step, with a gap or a late start in the data named), so early figures are provisional. For what Celestia's documentation requires, use search or get_doc ("Hardware requirements"); for servers that meet it, list_datacenter_offers; for an estimate of Fibre load, size_fibre_node. Celestia only.

NameTypeReqDescription
networkstring–mainnet or the Mocha testnet
rolestring–Only this node role; all roles when left out
windowstring–1d, 7d or 30d: the span the median, 95th percentile and maximum cover

No output schema declared.

No examples provided.

get_celestia_network_health ~162

Operator view of how the Celestia network is doing right now, from Unity Nodes Pulse: latest block and the measured block time, throughput, staking, the validator set (active, inactive, jailed, online voting power), how full recent blocks are and which validators produced them, which rollups posted the most data, the DA light-node measurements Unity Nodes takes (network and local head, sampling lag, header arrival lag) and the official status page. Mainnet or the Mocha testnet (block fullness, rollups and the status page are mainnet only). Celestia only, a snapshot refreshed every 15 minutes. For live on-chain totals and the TIA price use get_network_state.

NameTypeReqDescription
networkstring––

No output schema declared.

No examples provided.

get_celestia_operator_toolkit ~154

What a Celestia node operator needs to bootstrap and keep a node healthy, from Unity Nodes Pulse: persistent peers and seeds, snapshot and address-book mirrors, state-sync servers with the current trust height and hash, the auto-upgrade script, the Unity Nodes pruned snapshot with its restore and verify procedure, and the health of public RPC, REST and gRPC endpoints (status, latency, app version). Mainnet or the Mocha testnet. Celestia only, curated lists plus a probe refreshed every 15 minutes. The restore procedure deletes the node data directory: read it before running anything. Endpoint status is what Pulse measured from its own server.

NameTypeReqDescription
networkstring––

No output schema declared.

No examples provided.

get_celestia_upgrade_status ~167

Where the next Celestia network upgrade stands, from Unity Nodes Pulse: the app version being signalled and the current one, how much voting power has signalled against the threshold, whether the threshold is reached and the block the upgrade activates at with the date estimate Pulse gives and the block time it rests on, the latest stable release Pulse recommends, the largest validators that have not signalled, governance proposals (active and recent, with vote tallies) and the history of hard forks. Mainnet or the Mocha testnet (hard-fork history is mainnet only). Celestia only, a snapshot refreshed every 15 minutes. For release notes and the version to install use get_latest_release and get_breaking_changes.

NameTypeReqDescription
networkstring––

No output schema declared.

No examples provided.

get_celestia_validator ~178

Everything Unity Nodes Pulse knows about one Celestia validator: status, voting power and stake, commission, missed block proposals over 24 hours, 7 and 30 days, signature participation over 7 days, voting-power change over 24 hours, 7 and 30 days, where it is hosted when Pulse could place it, and whether it has signalled for the pending network upgrade. Look it up by operator address (celestiavaloper...) or by name; a partial name that matches several validators returns the candidates. Mainnet or the Mocha testnet. Celestia only, from a snapshot refreshed every 15 minutes. Names are typed by the validators and marked untrusted.

NameTypeReqDescription
networkstring––
validatorstringyesOperator address (celestiavaloper...) or validator name

No output schema declared.

No examples provided.

get_celestia_validator_guide ~266

The Unity Nodes validator guide for Celestia (moved here from runcelestia.xyz): the path to an active validator in three phases, the ten setup steps, operator gotchas, and the FAQ and common errors with their fixes. Every item names the Celestia docs page it was checked against, says whether the docs or the chain confirm it (verified) or it is operator experience (partial), and records where the docs or the chain disagree with the guide: those win over the guide. For exact commands and requirements use the official docs (search or get_doc); for the live state of the network get_celestia_network_health and get_celestia_upgrade_status; for choosing a server list_datacenter_offers; for what Unity Nodes' own nodes measure get_celestia_hardware_usage.

NameTypeReqDescription
limitinteger––
querystring–Words or an error message from the logs, e.g. "app hash mismatch" or "how do I unjail". Most of the words must match.
sectionstring–journey: the path to an active validator; setup: the ten setup steps; gotcha: operator lessons; faq: questions and node errors with their fixes.

No output schema declared.

No examples provided.

get_cip ~89

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.

NameTypeReqDescription
idstringyesCIP ID: "0001", "CIP-0042", or "PR-0117"

No output schema declared.

No examples provided.

get_cip_attachments ~78

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.

NameTypeReqDescription
idstringyesCIP ID: "0001", "CIP-0042"

No output schema declared.

No examples provided.

get_cip_history ~83

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

NameTypeReqDescription
idstringyesCIP ID: "0001", "CIP-0042", or "PR-0117"

No output schema declared.

No examples provided.

get_cip_mentions ~108

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

NameTypeReqDescription
idstringyesCIP ID: "0001", "CIP-0042", or "PR-0117"

No output schema declared.

No examples provided.

get_datacenter_offer ~188

Full detail of one rentable server from the Pulse Celestia datacenter catalog, by the id that list_datacenter_offers prints: hardware, price and setup fee, upgrade options (storage, RAM, bandwidth tiers with prices), traffic terms, provider notes, the Pulse compatibility verdict with every reason for each node role in both the real and the docs envelope, the FDP hosting-rule verdict per role, how many Celestia validators already run on the same provider, and the provider status page incidents. Celestia node hosting only. A snapshot, not a quote: confirm price and stock on the provider order page. The id changes when a provider changes the configuration, so an id from an old answer may be gone.

NameTypeReqDescription
idstringyesOffer id from list_datacenter_offers, e.g. "ovh-23scaleamd01-v3-sgp-sg"

No output schema declared.

No examples provided.

get_discussion ~134

Read one Celestia community forum thread (forum.celestia.org) with its posts, by topic id. This is the CELESTIA FORUM channel — not GitHub Discussions (use get_github_discussion). The topic id is the number at the end of the thread link that search, get_recent_changes and the list tools print (https://blobpedia.org/discussions/2314 is topic 2314); that link is accepted as well.

NameTypeReqDescription
id–yesForum topic number, e.g. 2314, or the thread link https://blobpedia.org/discussions/2314

No output schema declared.

No examples provided.

get_doc ~113

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.

NameTypeReqDescription
id–yesDoc page ID (from search/semantic_search results)

No output schema declared.

No examples provided.

get_fibre_blob ~215

One Celestia Fibre blob settled on the Mocha testnet (mocha-5), live from Cumulo: when and at what height it settled, who paid and how much, namespace, size, how many validators signed and the share of stake, whether it reached 2/3 (exact integer check by Cumulo), how many validators signed, were not needed or were not eligible, the payment promise and the retention deadline, and Cumulo's availability check by sampling rows. Look it up by the id from list_fibre_blobs ("<txhash>:<message index>"), by transaction hash or by blob id. Namespace names are chosen by the publisher and marked untrusted.

NameTypeReqDescription
chainstring–Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
idstringyesBlob id as listed by list_fibre_blobs ("<txhash>:<message index>"), a transaction hash, or a blob id

No output schema declared.

No examples provided.

get_fibre_blob_market ~293

Who pays for Celestia Fibre blockspace and how much: blobs settled, bytes, fees in TIA, blob size distribution, the on-chain fee formula and Cumulo's check of every charge against it, the publishers (accounts that pay) with their share of bytes and fees, price per MiB, escrow balances and withdrawals, the namespaces posting data, and blob activity over time. From Cumulo's open Fibre Network Monitor on the Mocha testnet (mocha-5); testnet TIA, not a mainnet price. Choose the period: 24h, 7d, 30d or all. Give an account (celestia1...) to see one publisher live: its blobs, namespaces, escrow deposits and withdrawals. Namespace names are bytes chosen by the publisher and marked untrusted. For individual blobs use list_fibre_blobs; for validators use get_fibre_validator.

NameTypeReqDescription
accountstring–A publisher account (celestia1...); gives that publisher live from Cumulo
chainstring–Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
namespacesinteger–How many namespaces to list
periodstring–24h, 7d, 30d or all
publishersinteger–How many publishers to list

No output schema declared.

No examples provided.

get_fibre_network_status ~455

Is Celestia Fibre ready? Status of the Celestia Fibre network (CIP-51, validator-operated blob publishing) from Cumulo's open Fibre Network Monitor: whether enough stake has a ready Fibre host to reach the 2/3 threshold, how many validators registered a host and are ready, how fast each probe region reaches 2/3, how many validators, hosting providers or countries could fail before ready stake drops below 2/3, validators still missing a host, fee and escrow parameters, whether validators keep the data they signed, the network history, and Cumulo's weekly and monthly reports. Cumulo monitors the Mocha testnet (mocha-5) today. Figures are measured and computed by Cumulo from probes in several regions and relayed unchanged, with Cumulo credited. Pick a view: overview, quorum, liveness, concentration, missing, payments, retention, method, history or report. Validator names are typed by the validators and marked untrusted. For one validator use get_fibre_validator; for blobs and fees use get_fibre_blob_market. For the hardware a Fibre node needs use size_fibre_node.

NameTypeReqDescription
chainstring–Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
limitinteger–For view concentration: rows per list
periodstring–For view report: week, month, year, or a named period such as 2026-W40, 2026-09 or 2026
rangestring–For view history: 24h, 7d, 30d or all
viewstring–overview = readiness against 2/3 plus the headline numbers; quorum = time to reach 2/3 per region; liveness = how many failures break 2/3; concentration = share by hosting provider and country; missi…

No output schema declared.

No examples provided.

get_fibre_validator ~341

Everything Cumulo's Fibre Network Monitor measures for one Celestia validator on the Mocha testnet (mocha-5): whether its Fibre host is registered and ready, where it runs, round trip from each probe region, uptime, how often it signed blobs, whether it keeps the data it signed, certificate identity, flags and, when something is wrong, Cumulo's diagnosis. Look it up by name, operator address (celestiavaloper...) or consensus address (celestiavalcons...). Optionally add live sections from Cumulo: status (ready right now), history (hourly uptime and round trip), blobs (which blobs it signed, did not need to sign, or could not), checks (latest download checks). Not signing a blob is not a failure when the publisher already had 2/3; only "not ready" is. Names, hosts and certificate names are typed by the validators and marked untrusted. Use list_fibre_validators to find validators.

NameTypeReqDescription
chainstring–Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
daysinteger–For include history: how many days of hourly points
includearray–Live extras from Cumulo: status, history, blobs, checks
limitinteger–For include blobs: how many blobs
rolestring–For include blobs: only blobs where it signed, was not needed, or was not ready
validatorstringyesValidator name, operator address (celestiavaloper...) or consensus address (celestiavalcons...)

No output schema declared.

No examples provided.

get_foundation_info ~172

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.

NameTypeReqDescription
limitinteger––
topicstringyesFree-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board".

No output schema declared.

No examples provided.

get_github_discussion ~178

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.

NameTypeReqDescription
idstringyesGitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..."

No output schema declared.

No examples provided.

get_issue_status ~69

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

NameTypeReqDescription
numberintegeryesIssue or PR number.
repostringyesRepo, e.g. "celestiaorg/celestia-app" or shorthand "celestia-app".

No output schema declared.

No examples provided.

get_latest_release ~98

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.

NameTypeReqDescription
packagestringyesRepo or package name: "app", "node", "core", "rollkit", "openrpc", or a full owner/repo.

No output schema declared.

No examples provided.

get_network_state ~126

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 present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_stats ~91

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 present but exposes no named parameters.

No output schema declared.

No examples provided.

get_operator_upgrade_notes ~234

What a Celestia node operator has to know and do for each consensus app version, from the official release notes: required OS and glibc, binary and multiplexer changes, config changes, KMS and signer changes, pruning, Fibre setup. Official text relayed as published, not a summary; for a version the official page does not cover yet (the newest), the Upgrade Notice of the latest stable celestia-app release. Give from_version (the version you run now) and to_version to get every version in between, only to_version for one version, or nothing for the newest. Celestia only. Which version mainnet runs now and where the upgrade signal stands: get_celestia_upgrade_status.

NameTypeReqDescription
detailstring–full: the official text; outline: only the section headings of each version
from_version––The app version you run now, e.g. 7 or v7; notes cover every version after it
to_version––The app version you are moving to, e.g. 10; the newest held if left out

No output schema declared.

No examples provided.

get_radar ~191

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.

NameTypeReqDescription
levelstring–Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert.
limitinteger–How many alerts to return, most severe and most recent first. Default 25.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

No output schema declared.

No examples provided.

get_recent_changes ~103

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.

NameTypeReqDescription
daysinteger––
limitinteger––

No output schema declared.

No examples provided.

get_sdk_changelog ~112

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.

NameTypeReqDescription
repostring–Optional repo hint: app, node, core, rollkit, openrpc.
versionstringyesVersion tag, e.g. "9.0.6", "v9.0.6".

No output schema declared.

No examples provided.

get_started_guide ~181

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.

NameTypeReqDescription
backgroundstringyesDeveloper's primary goal. Ask the user to pick one before proceeding.

No output schema declared.

No examples provided.

get_trending ~119

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 present but exposes no named parameters.

No output schema declared.

No examples provided.

get_video ~133

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.

NameTypeReqDescription
idstringyesYouTube video id, e.g. "dQw4w9WgXcQ"
transcript_charsinteger–Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only.

No output schema declared.

No examples provided.

get_whitepaper ~76

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.

NameTypeReqDescription
slugstringyesWhitepaper slug, e.g. "celestia-whitepaper"

No output schema declared.

No examples provided.

learning_path ~90

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

NameTypeReqDescription
goalstringyesWhat the learner wants to do, e.g. "run a light node", "post a blob", "understand DAS".

No output schema declared.

No examples provided.

list_celestia_resources ~253

Resources curated by Unity Nodes validators (moved here from unityhub.dev/celestia): endpoints, explorers, monitoring, services, tools, faucets, articles, videos and learning material for node operators (page validator), builders (developers), the community and people learning about Celestia (education). Called with no arguments it lists every page and section with its size; pass page and section to read one, network to keep one network, query to find words in labels, titles, descriptions and URLs. What a linked page says about itself is third-party text and is fenced. For peers, seeds and snapshots of the live network use get_celestia_operator_toolkit.

NameTypeReqDescription
limitinteger––
networkstring–Only resources for this network (and those for both).
offsetinteger––
pagestring–validator: node operators; developers: building on Celestia; community; education: learning material.
querystring–Words to find in labels, groups, titles, descriptions and URLs.
sectionstring–A section slug from the overview, e.g. endpoints, explorers, monitoring, services, articles, videos.

No output schema declared.

No examples provided.

list_celestia_validators ~274

List Celestia validators with their current numbers from Unity Nodes Pulse: status (active set, inactive, jailed), voting power, stake, commission, missed block proposals over 24 hours, 7 and 30 days, and the 30-day change of voting power. Mainnet or the Mocha testnet. Filter by status or name; sort by voting power, commission, missed proposals or voting-power change. Celestia validators only, from a snapshot refreshed every 15 minutes. Missed proposals are the health signal Pulse uses; Celestia commits blocks at two thirds of voting power, so a validator missing a signature is not necessarily down. Monikers are typed by the validators and marked untrusted. Use get_celestia_validator for one validator.

NameTypeReqDescription
limitinteger––
networkstring–mainnet or the Mocha testnet
offsetinteger––
querystring–Part of the validator name
sortstring–voting_power largest first; commission lowest first; missed_proposals_* most first; vp_change_30d largest gain first; name A-Z
statusstring–active = the bonded set that votes; inactive = not in the set; jailed = removed for downtime or double signing

No output schema declared.

No examples provided.

list_cips ~133

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.

NameTypeReqDescription
limitinteger––
statusstring––
typestring–Type filter, e.g. "Standards Track"

No output schema declared.

No examples provided.

Install

How do I install the io.github.UnityNodes/blobpedia MCP server?

io.github.UnityNodes/blobpedia is a hosted endpoint at https://blobpedia.org/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 · blobpedia.org

# add to Claude Code
claude mcp add --transport http unitynodes-blobpedia 'https://blobpedia.org/mcp'
Common questions

What is the io.github.UnityNodes/blobpedia MCP server?

io.github.UnityNodes/blobpedia is an MCP server listed in the public MCP registry as io.github.UnityNodes/blobpedia. Celestia knowledge base: CIPs, docs, forum, videos, GitHub, plus live on-chain state. This page covers its hosted endpoint (https://blobpedia.org/mcp).

Is the io.github.UnityNodes/blobpedia MCP server safe to use?

io.github.UnityNodes/blobpedia scores 79 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 io.github.UnityNodes/blobpedia MCP server expose?

io.github.UnityNodes/blobpedia exposes 67 tools: search, get_cip, list_cips, get_discussion, get_whitepaper, and 62 more. Their descriptions and schemas cost roughly 10,874 tokens of context every time the server is loaded.

Does the io.github.UnityNodes/blobpedia MCP server require authentication?

No. We connected to io.github.UnityNodes/blobpedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.UnityNodes/blobpedia MCP server still maintained?

io.github.UnityNodes/blobpedia is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.UnityNodes/blobpedia MCP server?

VerifyMCP ran 12 checks on io.github.UnityNodes/blobpedia, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.UnityNodes/blobpedia: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.