Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
Blobpedia is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
64
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Celestia knowledge base: CIPs, docs, forum, videos, GitHub, plus live on-chain state
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http blobpedia-mcp https://blobpedia.org/mcp
# 2 — ask your agent for something these tools do
# search, get_cip, list_cips and 61 more
Blobpedia costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
UNAll 2 servers
UnityNodes2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http blobpedia-mcp https://blobpedia.org/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
64 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query |
| type | string | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
| type | string | no | Type filter, e.g. "Standards Track" |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Forum topic number, e.g. 2314, or the thread link https://blobpedia.org/discussions/2314 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Whitepaper slug, e.g. "celestia-whitepaper" |
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.
No parameter schema on file.
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 a
No parameter schema on file.
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_searc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Doc page ID (from search/semantic_search results) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042" |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CIP ID: "0001", "CIP-0042", or "PR-0117" |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| limit | integer | no | — |
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.
No parameter schema on file.
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
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter by category (e.g. "DeFi", "Wallets", "NaaS") |
| query | string | no | Search in title/description/tags |
| limit | integer | no | — |
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, provide
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | no | Only servers Pulse lists for this node role, and show that role verdict. Omit to list servers listed for any role |
| verdict | string | no | Only servers with this verdict for the role (any role when role is omitted) |
| mode | string | no | real = Unity Nodes measured minimum, docs = official Celestia docs envelope |
| region | string | no | eu, na, latam, apac, africa or me (Middle East) |
| country | string | no | ISO 3166-1 alpha-2 country code, e.g. "SG" |
| provider | string | no | Provider name or key, e.g. "OVHcloud", "hetzner", "cherry"; see list_datacenter_providers |
| traffic | string | no | How the provider bills bandwidth: unmetered, egress (only outbound counted), both (inbound counted too, risky for Fibre) or unknown |
| max_price_usd | number | no | Monthly price ceiling in approximate USD (euro prices at Pulse's fixed 1.12) |
| min_ram_gb | integer | no | — |
| min_nvme_gb | integer | no | NVMe capacity in GB the server can reach, counting the provider's storage upgrade options |
| include_out_of_stock | boolean | no | Also list servers that are currently out of stock |
| hide_auction | boolean | no | Hide auction/used units |
| hide_fdp_excluded | boolean | no | Hide servers the FDP rules exclude for the role (validator unless role is fibre) |
| sort | string | no | price = cheapest first; ram, nvme, cores = largest first |
| limit | integer | no | — |
| offset | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Offer id from list_datacenter_offers, e.g. "ovh-23scaleamd01-v3-sgp-sg" |
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 provide
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider | string | no | One provider by name or key, e.g. "Hetzner" or "cherry" |
| region | string | no | Only providers that list servers in this region |
| mode | string | no | real = Unity Nodes measured minimum, docs = official Celestia docs envelope |
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 Celesti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stake_share_pct | number | yes | Your share of consensus voting power in percent, e.g. 1 for 1% |
| retention_hours | number | no | Blob retention window the store must cover (calculator default 4 h) |
| bandwidth_allowance_pct | number | no | Share of your uplink you let Fibre use; sizes the recommended port (default 20%) |
| throughput | string | no | current = Mocha-level; november_preview = unconfirmed 15x estimate for a possible 2.2 GB/s target |
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, fro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | mainnet or the Mocha testnet |
| status | string | no | active = the bonded set that votes; inactive = not in the set; jailed = removed for downtime or double signing |
| query | string | no | Part of the validator name |
| sort | string | no | voting_power largest first; commission lowest first; missed_proposals_* most first; vp_change_30d largest gain first; name A-Z |
| limit | integer | no | — |
| offset | integer | no | — |
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 (celestiaval
| Parameter | Type | Required | Notes |
|---|---|---|---|
| validator | string | yes | Operator address (celestiavaloper...) or validator name |
| network | string | no | — |
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 la
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | — |
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 earni
No parameter schema on file.
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 com
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | — |
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)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | — |
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 drop
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | string | no | 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; missin |
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| range | string | no | For view history: 24h, 7d, 30d or all |
| period | string | no | For view report: week, month, year, or a named period such as 2026-W40, 2026-09 or 2026 |
| limit | integer | no | For view concentration: rows per list |
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 sna
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| registered | string | no | registered = has a Fibre host on chain; not_registered = still has none |
| status | string | no | Cumulo status of the host, e.g. online or no_host; the answer lists the statuses present |
| query | string | no | Part of the validator name |
| country | string | no | Two-letter country code of the host, e.g. DE |
| provider | string | no | Part of the hosting provider name, e.g. hetzner |
| sort | string | no | stake = largest first; latency = fastest first; uptime_* = best first; name = A-Z |
| limit | integer | no | — |
| offset | integer | no | — |
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 (cele
| Parameter | Type | Required | Notes |
|---|---|---|---|
| validator | string | yes | Validator name, operator address (celestiavaloper...) or consensus address (celestiavalcons...) |
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| include | array | no | Live extras from Cumulo: status, history, blobs, checks |
| days | integer | no | For include history: how many days of hourly points |
| role | string | no | For include blobs: only blobs where it signed, was not needed, or was not ready |
| limit | integer | no | For include blobs: how many blobs |
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 Monito
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| period | string | no | 24h, 7d, 30d or all |
| account | string | no | A publisher account (celestia1...); gives that publisher live from Cumulo |
| namespaces | integer | no | How many namespaces to list |
| publishers | integer | no | How many publishers to list |
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; wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| namespace | string | no | Namespace as hex or text |
| payer | string | no | Account that paid (celestia1...) |
| validator | string | no | Consensus address (celestiavalcons1...) of a validator in the set |
| limit | integer | no | — |
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 availabi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Blob id as listed by list_fibre_blobs ("<txhash>:<message index>"), a transaction hash, or a blob id |
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| type | array | no | Only these event types |
| validator | string | no | A validator (celestiavalcons1... or celestiavaloper1...) or, for escrow events, a publisher account (celestia1...) |
| limit | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Transaction hash, blob id, commitment, height, account, namespace, validator or a UTC day (YYYY-MM-DD) |
| chain | string | no | Chain id; leave out for the one Cumulo monitors today (mocha-5, the Mocha testnet) |
| limit | integer | no | Blobs and events to show per kind |
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.
No parameter schema on file.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | Filter by repo, e.g. "celestiaorg/docs" |
| category | string | no | Filter by Discussions category, e.g. "Q&A", "Ideas" |
| limit | integer | no | — |
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 dedic
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | GitHub GraphQL node ID, e.g. "D_kwDOMNgu5s4AY..." |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | YouTube video id, e.g. "dQw4w9WgXcQ" |
| transcript_chars | integer | no | Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | no | Channel name filter, e.g. "Celestia", "Celestia Foundation", "Modular". Case-insensitive substring. |
| since | string | no | Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound. |
| has_transcript | boolean | no | If true, only return videos with a stored transcript. If false, only those still missing one. Omit for both. |
| limit | integer | no | — |
| offset | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Free-text topic, e.g. "team", "executive director", "working groups", "membership", "grants", "board". |
| limit | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-form question or phrase. |
| source_types | array | no | Restrict to these source types. Omit for all. |
| limit | integer | no | — |
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), the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| background | string | yes | Developer's primary goal. Ask the user to pick one before proceeding. |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. |
| state | string | no | Issue state filter (default: all). |
| limit | integer | no | Max rows (default 10). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
Search blobpedia's indexed Celestia talks/videos (YouTube transcripts). Celestia-specific. Returns matches across title + transcript with a short snippet around the hit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text query. Appears in title or transcript. |
| limit | integer | no | Max rows (default 5). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
Search across release-notes bodies of all indexed Celestia repos for a feature/keyword. Celestia-specific. Use to find which release first mentioned X.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | yes | Feature keyword, e.g. "blob size limit", "namespace", "data availability sampling". |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_version | no | The app version you run now, e.g. 7 or v7; notes cover every version after it | |
| to_version | no | The app version you are moving to, e.g. 10; the newest held if left out | |
| detail | string | no | full: the official text; outline: only the section headings of each version |
Surface release notes likely to contain security or CVE fixes. Celestia-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max rows (default 10). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic keyword, e.g. "namespace", "light node sync", "blob submission". |
Look up one GitHub issue or PR by repo + number. Celestia repos only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | yes | Repo, e.g. "celestiaorg/celestia-app" or shorthand "celestia-app". |
| number | integer | yes | Issue or PR number. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic keyword. |
| limit | integer | no | Max rows (default 5). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
Rank likely Celestia experts on a topic across blobpedia: forum activity matching the topic, plus overall forum volume of that author. Celestia-specific.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic / domain to find experts for. |
| limit | integer | no | Max authors (default 5). |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic / category / project family. |
Given one Celestia ecosystem project, find others with complementary tags/category that could plug in. Celestia-specific. Lightweight heuristic: overlap of tags + adjacent categories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project name or slug to look around. |
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. R
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error_text | string | yes | Error message, stack trace, or status code. Longer/more distinctive text returns better matches. |
| limit | integer | no | Max matches per source (default 3). |
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").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_sdk | string | yes | Origin version, e.g. "9.0.0" or "v9.0.0". |
| to_sdk | string | yes | Target version, e.g. "9.1.0" or "v9.1.0". |
| repo | string | no | Optional repo hint: "app", "node", "core", "rollkit", "openrpc", or a full owner/name. Defaults to celestia-app. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cip_id | string | yes | Starting CIP or PR id, e.g. "5", "CIP-0005", or "PR-203". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | yes | Version tag, e.g. "9.0.6", "v9.0.6". |
| repo | string | no | Optional repo hint: app, node, core, rollkit, openrpc. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | What you're seeing. Short prose, not a stack trace (for that use diagnose_error). |
| limit | integer | no | Max rows per source (default 5). |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature | string | yes | Feature description, e.g. "blob size limit", "namespace format", "light client sampling". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | yes | Repo or package name: "app", "node", "core", "rollkit", "openrpc", or a full owner/repo. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| level | string | no | Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert. |
| limit | integer | no | How many alerts to return, most severe and most recent first. Default 25. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | Project description / idea. |
| limit | integer | no | Max rows (default 10). |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic to cross-check. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | yes | What the learner wants to do, e.g. "run a light node", "post a blob", "understand DAS". |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Blobpedia or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Blobpedia can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.