BitBasic
Registry code: c4b4b06544151fc2
BitBasic (https://bitbasic.com), built by BitNordic, follows proof-of-stake networks (list-networks names them): their health, validators, staking rewards, governance and how decentralised they are. Use these tools to answer questions about them with BitBasic's figures.
- Start with list-networks when you don't know a network's slug; find-validators finds a validator or operator by name or address.
- endpoint
- https://bitbasic.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is BitBasic live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
- Is BitBasic free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does BitBasic have?
- 11 tools: network-status, network-parameters, find-validators, list-validators, validator-details, compare-validators, estimate-staking-rewards, decentralisation-report, ….
- Is BitBasic safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 11 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list-networks open 13h ago
Every proof-of-stake network BitBasic covers: its slug (the "network" argument of the other tools), token, kind, what it calls a validator, and its dashboard. Start here when you don't know a network's slug.
{ "type": "object", "properties": {} }arguments 4 linesgovernance-proposals open 13h ago
Governance proposals on one network or every one: the latest, those in one status (open for votes, opening soon, passed, rejected, other outcomes), or one proposal in full with its text, tally and (on Cosmos networks) how each validator voted.
{ "type": "object", "properties": { "open": { "type": "boolean", "description": "The same as status \"open\". Default: the latest 10." }, "status": { "enum": [ "open", "soon", "passed", "rejected", "other" ], "type": "string", "description": "Only proposals in this status, the same on every network: open (taking votes, soonest to close first), soon (opening soon), passed, rejected or other. Default: any." }, "network": { "type": "string", "description": "A network slug from list-networks. Default: every network with governance (not with \"proposal\")." }, "proposal": { "type": "integer", "minimum": 0, "description": "One proposal's number, for it in full (needs \"network\")." } } }arguments 29 lineslatest-news open 13h ago
BitBasic's latest news posts (upgrades, governance, advisories, reports), on every network or one, newest first, each with its summary and link.
{ "type": "object", "properties": { "limit": { "type": "integer", "maximum": 10, "minimum": 1, "description": "1 to 10. Default: 5." }, "network": { "type": "string", "description": "Only posts about this network (a slug from list-networks). Default: all." } } }arguments 15 linesnetwork-status unknown never probed
One network now: its health, where it is in its epoch, the active validator set, total stake, typical fee and other figures its dashboard leads with, as BitBasic last read them.
{ "type": "object", "required": [ "network" ], "properties": { "network": { "type": "string", "description": "A network slug from list-networks, such as \"kava\" or \"aztec\"." } } }arguments 12 linesnetwork-parameters unknown never probed
One network's rules as its chain states them: unbonding time, active set size, minimum commission, slashing, governance quorum and thresholds, inflation, fees and the rest, each in plain words, with recent changes. Read from the chain every hour.
{ "type": "object", "required": [ "network" ], "properties": { "network": { "type": "string", "description": "A network slug from list-networks, such as \"kava\" or \"aztec\"." } } }arguments 12 linesfind-validators unknown never probed
Validators and staking providers whose name, address or operator matches a query, on every network or one: exact addresses first, then by stake. Use it to find an operator's validators (such as "Chorus One") or which network an address is on.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Validators to return, 1 to 25. Default: 10." }, "query": { "type": "string", "description": "A name, an operator, or an address (whole or from its start, 6 characters or more)." }, "network": { "type": "string", "description": "Only this network (a slug from list-networks). Default: every network." } } }arguments 22 lineslist-validators unknown never probed
A network's validators, sorted as its dashboard sorts them (by stake on most networks) or by another figure, each with its status, stake, uptime, commission and delegators' reward rate.
{ "type": "object", "required": [ "network" ], "properties": { "sort": { "type": "string", "description": "A sort the network's validator list offers (stake, commission, uptime, produced…); a wrong one answers with the ones it takes. Default: the dashboard's." }, "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "1 to 25. Default: 10." }, "status": { "enum": [ "active", "queued", "exiting", "inactive", "exited" ], "type": "string", "description": "Only validators with this status. Default: all." }, "network": { "type": "string", "description": "A network slug from list-networks." }, "direction": { "enum": [ "asc", "desc" ], "type": "string", "description": "Default: desc." } } }arguments 41 linesvalidator-details unknown never probed
One validator in full: status, stake, delegators, commission and its delegators' reward rate, how much it signed and produced, its last 100 blocks (where the network says who signed each), and how it voted on the latest governance proposals. Find its address with find-validators.
{ "type": "object", "required": [ "network", "address" ], "properties": { "address": { "type": "string", "description": "The validator's address as BitBasic lists it (its validator id on Concordium)." }, "network": { "type": "string", "description": "A network slug from list-networks." } } }arguments 17 linescompare-validators unknown never probed
Two to four validators on one network side by side: status, stake, uptime, commission and what their delegators earn a year, as BitBasic's compare page shows them.
{ "type": "object", "required": [ "network", "addresses" ], "properties": { "network": { "type": "string", "description": "A network slug from list-networks." }, "addresses": { "type": "array", "items": { "type": "string" }, "maxItems": 4, "minItems": 2, "description": "2 to 4 validator addresses on that network, as BitBasic lists them." } } }arguments 22 linesestimate-staking-rewards unknown never probed
What delegating earns on a mainnet, as BitBasic's rewards calculator works it out: the yearly rate for any validator or a chosen one (after its commission), and for an amount, what it earns per day, month, year or a number of days. An estimate from today's rates, without restaking, not a promise or advice.
{ "type": "object", "required": [ "network" ], "properties": { "fee": { "type": "string", "description": "Mina only: the pool's fee in percent, which Mina pools keep off-chain." }, "days": { "type": "integer", "minimum": 1, "description": "A period in days to estimate for, besides day, month and year." }, "amount": { "type": "string", "description": "Whole tokens to delegate, such as \"1000\" or \"2500.5\". Default: rates only." }, "network": { "type": "string", "description": "A network slug from list-networks (mainnets only)." }, "validator": { "type": "string", "description": "A validator address on that network. Default: the network's rate." } } }arguments 29 linesdecentralisation-report unknown never probed
How concentrated a network's stake (and, where it has them, its staking providers) was over a month: the Nakamoto coefficient, the top 10's share, HHI and the active set, at the month's end, with its range and the change from the month before, from BitBasic's hourly readings.
{ "type": "object", "required": [ "network" ], "properties": { "month": { "type": "string", "description": "The month as yyyy-mm. Default: the last finished month with readings, else the current one." }, "network": { "type": "string", "description": "A network slug from list-networks." } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc4b4b06544151fc2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c4b4b06544151fc2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c4b4b06544151fc2?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.