BitBasic
Proof-of-stake network health, validators, staking rewards and governance. Read-only.
Should I use this
Quality & Safety
Findings (12)
- LOWin estimate-staking-rewards
- LOWin list-networks
- LOWin network-status
- LOWin network-parameters
- LOWin find-validators
- LOWin list-validators
- LOWin validator-details
- LOWin compare-validators
- LOWin estimate-staking-rewards
- LOWin governance-proposals
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"bitbasic": {
"url": "https://bitbasic.com/mcp"
}
}
}Remote endpoints
https://bitbasic.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (11)
π’list-networks
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.
Input Schema
{
"type": "object",
"properties": {}
}π’network-status(network)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks, such as \"kava\" or \"aztec\".",
"type": "string"
}
},
"required": [
"network"
]
}π’network-parameters(network)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks, such as \"kava\" or \"aztec\".",
"type": "string"
}
},
"required": [
"network"
]
}π’find-validators(query, network, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"description": "A name, an operator, or an address (whole or from its start, 6 characters or more).",
"type": "string"
},
"network": {
"description": "Only this network (a slug from list-networks). Default: every network.",
"type": "string"
},
"limit": {
"description": "Validators to return, 1 to 25. Default: 10.",
"minimum": 1,
"maximum": 25,
"type": "integer"
}
},
"required": [
"query"
]
}π’list-validators(network, status, sort, direction, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks.",
"type": "string"
},
"status": {
"description": "Only validators with this status. Default: all.",
"enum": [
"active",
"queued",
"exiting",
"inactive",
"exited"
],
"type": "string"
},
"sort": {
"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.",
"type": "string"
},
"direction": {
"description": "Default: desc.",
"enum": [
"asc",
"desc"
],
"type": "string"
},
"limit": {
"description": "1 to 25. Default: 10.",
"minimum": 1,
"maximum": 25,
"type": "integer"
}
},
"required": [
"network"
]
}π’validator-details(network, address)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks.",
"type": "string"
},
"address": {
"description": "The validator's address as BitBasic lists it (its validator id on Concordium).",
"type": "string"
}
},
"required": [
"network",
"address"
]
}π’compare-validators(network, addresses)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks.",
"type": "string"
},
"addresses": {
"description": "2 to 4 validator addresses on that network, as BitBasic lists them.",
"minItems": 2,
"maxItems": 4,
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"network",
"addresses"
]
}π’estimate-staking-rewards(network, amount, validator, days, fee)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks (mainnets only).",
"type": "string"
},
"amount": {
"description": "Whole tokens to delegate, such as \"1000\" or \"2500.5\". Default: rates only.",
"type": "string"
},
"validator": {
"description": "A validator address on that network. Default: the network's rate.",
"type": "string"
},
"days": {
"description": "A period in days to estimate for, besides day, month and year.",
"minimum": 1,
"type": "integer"
},
"fee": {
"description": "Mina only: the pool's fee in percent, which Mina pools keep off-chain.",
"type": "string"
}
},
"required": [
"network"
]
}π’governance-proposals(network, status, open, proposal)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks. Default: every network with governance (not with \"proposal\").",
"type": "string"
},
"status": {
"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.",
"enum": [
"open",
"soon",
"passed",
"rejected",
"other"
],
"type": "string"
},
"open": {
"description": "The same as status \"open\". Default: the latest 10.",
"type": "boolean"
},
"proposal": {
"description": "One proposal's number, for it in full (needs \"network\").",
"minimum": 0,
"type": "integer"
}
}
}π’decentralisation-report(network, month)
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.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "A network slug from list-networks.",
"type": "string"
},
"month": {
"description": "The month as yyyy-mm. Default: the last finished month with readings, else the current one.",
"type": "string"
}
},
"required": [
"network"
]
}π’latest-news(network, limit)
BitBasic's latest news posts (upgrades, governance, advisories, reports), on every network or one, newest first, each with its summary and link.
Input Schema
{
"type": "object",
"properties": {
"network": {
"description": "Only posts about this network (a slug from list-networks). Default: all.",
"type": "string"
},
"limit": {
"description": "1 to 10. Default: 5.",
"minimum": 1,
"maximum": 10,
"type": "integer"
}
}
}Community
Evidence