Model Context Protocol server for Rollbar
Nothing to run from here
CometBFT validator ops 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.
6
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
Read-only health, jail-risk, halt and upgrade checks for CometBFT validators and nodes
Quickstart
Install it the way its author documents:
1. Mount your cometbft-mcp config.yaml (node RPC URLs, optional Cosmos REST URL) read-only into the container
The full guide: https://github.com/wookja-0/cometbft-mcp
Publishernot claimed
W0All 1 server
wookja-01 server
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. This one runs on your machine: your client starts CometBFT validator ops as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Install it the way its author documents:
1. Mount your cometbft-mcp config.yaml (node RPC URLs, optional Cosmos REST URL) read-only into the container
The full guide: https://github.com/wookja-0/cometbft-mcp
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
One-call health sweep of every configured node and validator: sync, peers, signing liveness over the last 50 blocks
No parameter schema on file.
Check whether CometBFT nodes are synced and following the chain head.
No parameter schema on file.
Check p2p connectivity of CometBFT nodes: peer count, inbound/outbound split, peers on public addresses, and peers on another chain.
No parameter schema on file.
Check whether a validator is signing blocks, from the commit signatures of the last N blocks (default 100).
No parameter schema on file.
Inspect the live consensus round: current height, round and step, how long the node has been at this height,
No parameter schema on file.
Check the chain's scheduled software upgrade and whether the fleet is ready for it.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- 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 CometBFT validator ops 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 ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.4.5.
0.4.5
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 CometBFT validator ops 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.