io.github.UnityNodes/blobpedia

Est-ce que io.github.UnityNodes/blobpedia est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.UnityNodes/blobpedia » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 65 outils

• detect_cip_dependency_chain≈ 172 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • cip_id · string · requis
    Starting CIP or PR id, e.g. "5", "CIP-0005", or "PR-203".

  Exemple d'appel

  {"name": "detect_cip_dependency_chain", "arguments": {"cip_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• detect_drift≈ 113 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · requis
    Topic to cross-check.

  Exemple d'appel

  {"name": "detect_drift", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• diagnose_error≈ 228 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max matches per source (default 3).
  • error_text · string · requis
    Error message, stack trace, or status code. Longer/more distinctive text returns better matches.

  Exemple d'appel

  {"name": "diagnose_error", "arguments": {"error_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• ecosystem_dependency_graph≈ 122 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · requis
    Topic / category / project family.

  Exemple d'appel

  {"name": "ecosystem_dependency_graph", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_cip_for_feature≈ 128 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • feature · string · requis
    Feature description, e.g. "blob size limit", "namespace format", "light client sampling".

  Exemple d'appel

  {"name": "find_cip_for_feature", "arguments": {"feature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_code_examples≈ 195 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max rows (default 5).
  • topic · string · requis
    Topic keyword.
  • offset · integer · optionnel
    Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

  Exemple d'appel

  {"name": "find_code_examples", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_collaboration_opportunities≈ 120 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • project · string · requis
    Project name or slug to look around.

  Exemple d'appel

  {"name": "find_collaboration_opportunities", "arguments": {"project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_expert≈ 134 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max authors (default 5).
  • topic · string · requis
    Topic / domain to find experts for.

  Exemple d'appel

  {"name": "find_expert", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_known_issues≈ 216 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max rows per source (default 5).
  • description · string · requis
    What you're seeing. Short prose, not a stack trace (for that use diagnose_error).

  Exemple d'appel

  {"name": "find_known_issues", "arguments": {"description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_maintainer_guidance≈ 130 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • topic · string · requis
    Topic keyword, e.g. "namespace", "light node sync", "blob submission".

  Exemple d'appel

  {"name": "find_maintainer_guidance", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_security_patches≈ 112 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel
    Max rows (default 10).

  Exemple d'appel

  {"name": "find_security_patches", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_similar_projects≈ 213 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max rows (default 10).
  • offset · integer · optionnel
    Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
  • description · string · requis
    Project description / idea.

  Exemple d'appel

  {"name": "find_similar_projects", "arguments": {"description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_breaking_changes≈ 222 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • repo · string · optionnel
    Optional repo hint: "app", "node", "core", "rollkit", "openrpc", or a full owner/name. Defaults to celestia-app.
  • to_sdk · string · requis
    Target version, e.g. "9.1.0" or "v9.1.0".
  • from_sdk · string · requis
    Origin version, e.g. "9.0.0" or "v9.0.0".

  Exemple d'appel

  {"name": "get_breaking_changes", "arguments": {"to_sdk": "texte", "from_sdk": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_decentralization≈ 197 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • network · string · optionnel · mainnet | mocha

  Exemple d'appel

  {"name": "get_celestia_decentralization", "arguments": {"network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_economics≈ 204 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_celestia_economics", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_hardware_usage≈ 456 tokens

  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, RAM of the processes, page cache, data size and its change per day, free disk and network for each node role (validator, consensus node, bridge, Fibre, light node), as median, 95th percentile and maximum over 1, 7 or 30 days. Measured values, with two clearly labelled estimates kept apart from them (a straight-line projection of each node's data size and the Celestia Foundation's Fibre calculator for Unity Nodes' voting power): a role Unity Nodes does not run is said to have no measurements (there is no Fibre on mainnet yet), the chain's own load in the same window (block data per second) with a correlation r of each node's CPU, network and disk load with it (a link in how they moved, not a cause; shown once four hours overlap), and the answer says how much of the window the samples fill, 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • role · string · optionnel · validator | consensus | bridge | fibre | light
    Only this node role; all roles when left out
  • window · string · optionnel · 1d | 7d | 30d
    1d, 7d or 30d: the span the median, 95th percentile and maximum cover
  • network · string · optionnel · mainnet | mocha
    mainnet or the Mocha testnet

  Exemple d'appel

  {"name": "get_celestia_hardware_usage", "arguments": {"role": "validator", "window": "1d", "network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_network_health≈ 228 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • network · string · optionnel · mainnet | mocha

  Exemple d'appel

  {"name": "get_celestia_network_health", "arguments": {"network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_operator_toolkit≈ 224 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • network · string · optionnel · mainnet | mocha

  Exemple d'appel

  {"name": "get_celestia_operator_toolkit", "arguments": {"network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_upgrade_status≈ 241 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • network · string · optionnel · mainnet | mocha

  Exemple d'appel

  {"name": "get_celestia_upgrade_status", "arguments": {"network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_celestia_validator≈ 261 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • network · string · optionnel · mainnet | mocha
  • validator · string · requis
    Operator address (celestiavaloper...) or validator name

  Exemple d'appel

  {"name": "get_celestia_validator", "arguments": {"validator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_cip≈ 118 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    CIP ID: "0001", "CIP-0042", or "PR-0117"

  Exemple d'appel

  {"name": "get_cip", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_cip_attachments≈ 110 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    CIP ID: "0001", "CIP-0042"

  Exemple d'appel

  {"name": "get_cip_attachments", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_cip_history≈ 113 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    CIP ID: "0001", "CIP-0042", or "PR-0117"

  Exemple d'appel

  {"name": "get_cip_history", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_cip_mentions≈ 141 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    CIP ID: "0001", "CIP-0042", or "PR-0117"

  Exemple d'appel

  {"name": "get_cip_mentions", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_datacenter_offer≈ 258 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Offer id from list_datacenter_offers, e.g. "ovh-23scaleamd01-v3-sgp-sg"

  Exemple d'appel

  {"name": "get_datacenter_offer", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_discussion≈ 194 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · ? · requis
    Forum topic number, e.g. 2314, or the thread link https://blobpedia.org/discussions/2314

  Exemple d'appel

  {"name": "get_discussion", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_doc≈ 196 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · ? · requis
    Doc page ID (from search/semantic_search results)

  Exemple d'appel

  {"name": "get_doc", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_fibre_blob≈ 283 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    Blob id as listed by list_fibre_blobs ("<txhash>:<message index>"), a transaction hash, or a blob id
  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)

  Exemple d'appel

  {"name": "get_fibre_blob", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_fibre_blob_market≈ 408 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • period · string · optionnel · 24h | 7d | 30d | all
    24h, 7d, 30d or all
  • account · string · optionnel
    A publisher account (celestia1...); gives that publisher live from Cumulo
  • namespaces · integer · optionnel
    How many namespaces to list
  • publishers · integer · optionnel
    How many publishers to list

  Exemple d'appel

  {"name": "get_fibre_blob_market", "arguments": {"chain": "texte", "period": "24h", "account": "texte", "namespaces": 1, "publishers": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_fibre_network_status≈ 632 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • view · string · optionnel · overview | quorum | liveness | concentration | missing | payments | retention | method
    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; missing = validators without a ready host; payments = fee formula, parameters, escrow; retention = do hosts keep the data they signed; method = how Cumulo measures each figure; history = readiness over time; report = Cumulo's week or month report
  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • limit · integer · optionnel
    For view concentration: rows per list
  • range · string · optionnel · 24h | 7d | 30d | all
    For view history: 24h, 7d, 30d or all
  • period · string · optionnel
    For view report: week, month, year, or a named period such as 2026-W40, 2026-09 or 2026

  Exemple d'appel

  {"name": "get_fibre_network_status", "arguments": {"view": "overview", "chain": "texte", "limit": 1, "range": "24h", "period": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_fibre_validator≈ 515 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • days · integer · optionnel
    For include history: how many days of hourly points
  • role · string · optionnel · signed | not_collected | not_ready
    For include blobs: only blobs where it signed, was not needed, or was not ready
  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • limit · integer · optionnel
    For include blobs: how many blobs
  • include · array · optionnel
    Live extras from Cumulo: status, history, blobs, checks
  • validator · string · requis
    Validator name, operator address (celestiavaloper...) or consensus address (celestiavalcons...)

  Exemple d'appel

  {"name": "get_fibre_validator", "arguments": {"validator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_foundation_info≈ 231 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • topic · string · requis
    Free-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board".

  Exemple d'appel

  {"name": "get_foundation_info", "arguments": {"topic": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_github_discussion≈ 216 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    GitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..."

  Exemple d'appel

  {"name": "get_github_discussion", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_issue_status≈ 124 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • repo · string · requis
    Repo, e.g. "celestiaorg/celestia-app" or shorthand "celestia-app".
  • number · integer · requis
    Issue or PR number.

  Exemple d'appel

  {"name": "get_issue_status", "arguments": {"repo": "texte", "number": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_latest_release≈ 134 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • package · string · requis
    Repo or package name: "app", "node", "core", "rollkit", "openrpc", or a full owner/repo.

  Exemple d'appel

  {"name": "get_latest_release", "arguments": {"package": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_network_state≈ 161 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_network_state", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_network_stats≈ 128 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_network_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_operator_upgrade_notes≈ 347 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "get_operator_upgrade_notes", "arguments": {"detail": "full", "to_version": "texte", "from_version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_radar≈ 307 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "get_radar", "arguments": {"level": "all", "limit": 1, "offset": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_recent_changes≈ 160 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • days · integer · optionnel
  • limit · integer · optionnel

  Exemple d'appel

  {"name": "get_recent_changes", "arguments": {"days": 1, "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_sdk_changelog≈ 146 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • repo · string · optionnel
    Optional repo hint: app, node, core, rollkit, openrpc.
  • version · string · requis
    Version tag, e.g. "9.0.6", "v9.0.6".

  Exemple d'appel

  {"name": "get_sdk_changelog", "arguments": {"version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_started_guide≈ 259 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • background · string · requis · rollup_dev | node_operator | app_dev | researcher | new_to_celestia
    Developer's primary goal. Ask the user to pick one before proceeding.

  Exemple d'appel

  {"name": "get_started_guide", "arguments": {"background": "rollup_dev"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_trending≈ 153 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_trending", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_video≈ 186 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    YouTube video id, e.g. "dQw4w9WgXcQ"
  • transcript_chars · integer · optionnel
    Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only.

  Exemple d'appel

  {"name": "get_video", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_whitepaper≈ 116 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Whitepaper slug, e.g. "celestia-whitepaper"

  Exemple d'appel

  {"name": "get_whitepaper", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• learning_path≈ 142 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • goal · string · requis
    What the learner wants to do, e.g. "run a light node", "post a blob", "understand DAS".

  Exemple d'appel

  {"name": "learning_path", "arguments": {"goal": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_celestia_validators≈ 450 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • sort · string · optionnel · voting_power | commission | missed_proposals_30d | missed_proposals_7d | vp_change_30d | name
    voting_power largest first; commission lowest first; missed_proposals_* most first; vp_change_30d largest gain first; name A-Z
  • limit · integer · optionnel
  • query · string · optionnel
    Part of the validator name
  • offset · integer · optionnel
  • status · string · optionnel · active | inactive | jailed | any
    active = the bonded set that votes; inactive = not in the set; jailed = removed for downtime or double signing
  • network · string · optionnel · mainnet | mocha
    mainnet or the Mocha testnet

  Exemple d'appel

  {"name": "list_celestia_validators", "arguments": {"sort": "voting_power", "limit": 1, "query": "texte", "offset": 1, "status": "active", "network": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_cips≈ 237 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • type · string · optionnel
    Type filter, e.g. "Standards Track"
  • limit · integer · optionnel
  • status · string · optionnel · Approved | Final | Active | Living | In Review | Review | Proposed | Last Call

  Exemple d'appel

  {"name": "list_cips", "arguments": {"type": "texte", "limit": 1, "status": "Approved"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_datacenter_offers≈ 890 tokens

  Browse rentable bare-metal servers for Celestia nodes (validator, bridge or Fibre) from the Unity Nodes Pulse datacenter catalog: 23 hosting providers, price and stock, location, CPU, RAM, NVMe, uplink and traffic terms, and Pulse's own compatibility verdict per node role (Compatible, Needs benchmark, Check caveats, Not compatible) with the reason. Filter by role, verdict, region, country, provider, price and hardware; cheapest first. Celestia node hosting only, not a general server search and not a quote: prices, stock and verdicts are a snapshot refreshed every 15 minutes. Servers that miss a role hardware or price floor are not listed for it, as on the Pulse page. mode real = what Unity Nodes recommends from its own measurements, docs = the larger official Celestia envelope. Fibre verdicts assume the launch-minimum stake: use size_fibre_node for yours. FDP = Celestia Foundation Delegation Program hosting rules. Use get_datacenter_offer for one server and list_datacenter_providers for the provider overview.

  Paramètres, retour & exemple (16)

  Paramètres

  • mode · string · optionnel · real | docs
    real = Unity Nodes measured minimum, docs = official Celestia docs envelope
  • role · string · optionnel · validator | bridge | fibre
    Only servers Pulse lists for this node role, and show that role verdict. Omit to list servers listed for any role
  • sort · string · optionnel · price | ram | nvme | cores
    price = cheapest first; ram, nvme, cores = largest first
  • limit · integer · optionnel
  • offset · integer · optionnel
  • region · string · optionnel · eu | na | latam | apac | africa | me
    eu, na, latam, apac, africa or me (Middle East)
  • country · string · optionnel
    ISO 3166-1 alpha-2 country code, e.g. "SG"
  • traffic · string · optionnel · unmetered | egress | both | unknown
    How the provider bills bandwidth: unmetered, egress (only outbound counted), both (inbound counted too, risky for Fibre) or unknown
  • verdict · string · optionnel · compatible | needs_benchmark | check_caveats | not_compatible
    Only servers with this verdict for the role (any role when role is omitted)
  • provider · string · optionnel
    Provider name or key, e.g. "OVHcloud", "hetzner", "cherry"; see list_datacenter_providers
  • min_ram_gb · integer · optionnel
  • min_nvme_gb · integer · optionnel
    NVMe capacity in GB the server can reach, counting the provider's storage upgrade options
  • hide_auction · boolean · optionnel
    Hide auction/used units
  • max_price_usd · number · optionnel
    Monthly price ceiling in approximate USD (euro prices at Pulse's fixed 1.12)
  • hide_fdp_excluded · boolean · optionnel
    Hide servers the FDP rules exclude for the role (validator unless role is fibre)
  • include_out_of_stock · boolean · optionnel
    Also list servers that are currently out of stock

  Exemple d'appel

  {"name": "list_datacenter_offers", "arguments": {"mode": "real", "role": "validator", "sort": "price", "limit": 1, "offset": 1, "region": "eu"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_datacenter_providers≈ 293 tokens

  Overview of the hosting providers in the Pulse Celestia datacenter catalog: how many servers each lists, how many Pulse lists for each node role and how many of those are Compatible, regions, price range for validator servers, bandwidth billing, the FDP hosting rule, how many Celestia validators already run there and whether the provider status page shows open incidents. Use it to choose a provider before browsing servers with list_datacenter_offers. Celestia node hosting only. Provider data is a snapshot refreshed every 15 minutes from Pulse.

  Paramètres, retour & exemple (3)

  Paramètres

  • mode · string · optionnel · real | docs
    real = Unity Nodes measured minimum, docs = official Celestia docs envelope
  • region · string · optionnel · eu | na | latam | apac | africa | me
    Only providers that list servers in this region
  • provider · string · optionnel
    One provider by name or key, e.g. "Hetzner" or "cherry"

  Exemple d'appel

  {"name": "list_datacenter_providers", "arguments": {"mode": "real", "region": "eu", "provider": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_ecosystem_projects≈ 174 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
  • query · string · optionnel
    Search in title/description/tags
  • category · string · optionnel
    Filter by category (e.g. "DeFi", "Wallets", "NaaS")

  Exemple d'appel

  {"name": "list_ecosystem_projects", "arguments": {"limit": 1, "query": "texte", "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_fibre_blobs≈ 353 tokens

  List the latest blobs published through Celestia Fibre with who signed them: time, namespace, size, fee in TIA, signatures against the validator set, share of stake that signed and whether it reached 2/3, best probe region, and whether Cumulo could prove the data is available by sampling rows. Mocha testnet (mocha-5), newest first. Without filters this is a snapshot refreshed every 15 minutes; with a namespace, payer or validator filter, or more than 25 blobs, it is fetched live from Cumulo. Namespace names are chosen by the publisher and marked untrusted. Use get_fibre_blob for one blob with its signers.

  Paramètres, retour & exemple (5)

  Paramètres

  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • limit · integer · optionnel
  • payer · string · optionnel
    Account that paid (celestia1...)
  • namespace · string · optionnel
    Namespace as hex or text
  • validator · string · optionnel
    Consensus address (celestiavalcons1...) of a validator in the set

  Exemple d'appel

  {"name": "list_fibre_blobs", "arguments": {"chain": "texte", "limit": 1, "payer": "texte", "namespace": "texte", "validator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_fibre_events≈ 350 tokens

  List what happened on the Celestia Fibre network (Mocha testnet, mocha-5), newest first: blob payments, validators registering or leaving their Fibre host, status changes, host reconfirmations and escrow deposits, as recorded by Cumulo's Fibre Network Monitor. Without filters this is a snapshot refreshed every 15 minutes; with a type or validator filter, or more than 50 events, it is fetched live from Cumulo. Event titles quote names typed by validators and publishers and are marked untrusted. For one validator's whole record use get_fibre_validator.

  Paramètres, retour & exemple (4)

  Paramètres

  • type · array · optionnel
    Only these event types
  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • limit · integer · optionnel
  • validator · string · optionnel
    A validator (celestiavalcons1... or celestiavaloper1...) or, for escrow events, a publisher account (celestia1...)

  Exemple d'appel

  {"name": "list_fibre_events", "arguments": {"type": [], "chain": "texte", "limit": 1, "validator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_fibre_validators≈ 517 tokens

  List the validators of the Celestia Fibre network with Cumulo's measurements: whether each registered a Fibre host and is ready, stake rank and share, typical round trip, uptime over 24 hours, 7 and 30 days, and where the host runs (country, hosting provider). Mocha testnet (mocha-5). Filter by registered or not, status, name, country or provider; sort by stake, latency, uptime or name. From a snapshot refreshed every 15 minutes of an open API by Cumulo, credited in each answer. Validator names and hosts are typed by the validators and marked untrusted. Use get_fibre_validator for one validator with its signing record, data retention, probes and diagnosis.

  Paramètres, retour & exemple (9)

  Paramètres

  • sort · string · optionnel · stake | latency | uptime_7d | uptime_30d | name
    stake = largest first; latency = fastest first; uptime_* = best first; name = A-Z
  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • limit · integer · optionnel
  • query · string · optionnel
    Part of the validator name
  • offset · integer · optionnel
  • status · string · optionnel
    Cumulo status of the host, e.g. online or no_host; the answer lists the statuses present
  • country · string · optionnel
    Two-letter country code of the host, e.g. DE
  • provider · string · optionnel
    Part of the hosting provider name, e.g. hetzner
  • registered · string · optionnel · registered | not_registered | any
    registered = has a Fibre host on chain; not_registered = still has none

  Exemple d'appel

  {"name": "list_fibre_validators", "arguments": {"sort": "stake", "chain": "texte", "limit": 1, "query": "texte", "offset": 1, "status": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_github_discussions≈ 204 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • repo · string · optionnel
    Filter by repo, e.g. "celestiaorg/docs"
  • limit · integer · optionnel
  • category · string · optionnel
    Filter by Discussions category, e.g. "Q&A", "Ideas"

  Exemple d'appel

  {"name": "list_github_discussions", "arguments": {"repo": "texte", "limit": 1, "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_repos≈ 100 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_repos", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_videos≈ 258 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "list_videos", "arguments": {"limit": 1, "since": "texte", "offset": 1, "channel": "texte", "has_transcript": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_whitepapers≈ 88 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_whitepapers", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search≈ 249 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • type · string · optionnel · all | cip | doc | discussion | whitepaper | blog | youtube | github
  • limit · integer · optionnel
  • query · string · requis
    Search query

  Exemple d'appel

  {"name": "search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_fibre≈ 312 tokens

  Search the Celestia Fibre history kept by Cumulo (Mocha testnet, mocha-5), live: give a transaction hash, blob id or commitment, a block height, an account (celestia1...), a namespace, a validator (name, celestiavalcons1... or celestiavaloper1...) or a UTC day (YYYY-MM-DD) and get the blobs, events, validators or the daily totals that match, with the archive files of a day. Use it when you hold an identifier and do not know what it is. For the latest blobs or events without an identifier use list_fibre_blobs or list_fibre_events. Names in results are typed by validators and publishers and marked untrusted.

  Paramètres, retour & exemple (3)

  Paramètres

  • q · string · requis
    Transaction hash, blob id, commitment, height, account, namespace, validator or a UTC day (YYYY-MM-DD)
  • chain · string · optionnel
    Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet)
  • limit · integer · optionnel
    Blobs and events to show per kind

  Exemple d'appel

  {"name": "search_fibre", "arguments": {"q": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_github_issues≈ 241 tokens

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

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Max rows (default 10).
  • query · string · requis
    Free-text query.
  • state · string · optionnel · open | closed | all
    Issue state filter (default: all).
  • offset · integer · optionnel
    Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

  Exemple d'appel

  {"name": "search_github_issues", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_release_notes≈ 122 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • feature · string · requis
    Feature keyword, e.g. "blob size limit", "namespace", "data availability sampling".

  Exemple d'appel

  {"name": "search_release_notes", "arguments": {"feature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_talks≈ 198 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max rows (default 5).
  • query · string · requis
    Free-text query. Appears in title or transcript.
  • offset · integer · optionnel
    Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

  Exemple d'appel

  {"name": "search_talks", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• semantic_search≈ 304 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
  • query · string · requis
    Free-form question or phrase.
  • source_types · array · optionnel
    Restrict to these source types. Omit for all.

  Exemple d'appel

  {"name": "semantic_search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• size_fibre_node≈ 360 tokens

  Size the extra hardware a Celestia Fibre node needs on top of a validator, from the validator's share of voting power: storage rows, disk, sustained ingress, monthly inbound traffic, RAM and the uplink to order. A port of the Celestia Foundation's public Fibre calculator as Pulse implements it, calibrated to Mocha. The november_preview throughput is an UNCONFIRMED estimate, not an official Celestia figure. A sizing calculator, not live network data; the output links to the Pulse page that lists the servers for this plan.

  Paramètres, retour & exemple (4)

  Paramètres

  • throughput · string · optionnel · current | november_preview
    current = Mocha-level; november_preview = unconfirmed 15x estimate for a possible 2.2 GB/s target
  • retention_hours · number · optionnel
    Blob retention window the store must cover (calculator default 4 h)
  • stake_share_pct · number · requis
    Your share of consensus voting power in percent, e.g. 1 for 1%
  • bandwidth_allowance_pct · number · optionnel
    Share of your uplink you let Fibre use; sizes the recommended port (default 20%)

  Exemple d'appel

  {"name": "size_fibre_node", "arguments": {"stake_share_pct": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://blobpedia.org/mcp