BitBasic MCP server
com.bitbasic/bitbasicbitbasic.comstreamable-httpv1.0.0Scanned
Proof-of-stake network health, validators, staking rewards and governance. Read-only.
11 tools: 6 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BitBasic MCP server can do
The BitBasic MCP server is published by bitbasic.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (6 tools: network-parameters, validator-details, estimate-staking-rewards, governance-proposals and 2 more), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 6Claude Code: ask
decentralisation-reportHow 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 mo…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Decentralisation report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
estimate-staking-rewardsWhat 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Estimate staking rewards
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
governance-proposalsGovernance 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Governance proposals
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
latest-newsBitBasic's latest news posts (upgrades, governance, advisories, reports), on every network or one, newest first, each with its summary and link.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it BitBasic's latest news posts (upgrades, governance, advisories, reports), on every network or one, newest first, each with its summary and link.
Annotations the server declares
- title: Latest news
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
network-parametersOne 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Network parameters
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validator-detailsOne 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 signe…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Validator details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
compare-validatorsTwo 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.No findings
Why it is in this group
- The name "compare-validators" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Compare validators
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find-validatorsValidators and staking providers whose name, address or operator matches a query, on every network or one: exact addresses first, then by stake.No findings
Why it is in this group
- The name "find-validators" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find validators
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-networksEvery 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.No findings
Why it is in this group
- The name "list-networks" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List networks
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-validatorsA 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 …No findings
Why it is in this group
- The name "list-validators" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List validators
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
network-statusOne 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.No findings
Why it is in this group
- The name "network-status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Network status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://bitbasic.com/mcp: tools/list returned 11 tools to an anonymous client, including network-parameters (write), validator-details (write), estimate-staking-rewards (write), governance-proposals (write), decentralisation-report (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bitbasic https://bitbasic.com/mcpclaude mcp add --transport http bitbasic https://bitbasic.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bitbasic__list-networks",
"mcp__bitbasic__network-status",
"mcp__bitbasic__find-validators",
"mcp__bitbasic__list-validators",
"mcp__bitbasic__compare-validators"
],
"ask": [
"mcp__bitbasic__network-parameters",
"mcp__bitbasic__validator-details",
"mcp__bitbasic__estimate-staking-rewards",
"mcp__bitbasic__governance-proposals",
"mcp__bitbasic__decentralisation-report",
"mcp__bitbasic__latest-news"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bitbasic. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.bitbasic/bitbasic/verify?hash=0365af0401d6eb1ff5343c04b10e168f530451cce2c12274d7adfecd2d594fdc" | jq -e '.changed == false'Pinned hash 0365af0401d6, from Nov 13, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.bitbasic/bitbasic/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.bitbasic/bitbasic)Source: MCP Registry. Synced Nov 13, 2026, 15:17 UTC.
BitBasic MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BitBasic MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BitBasic MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BitBasic MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the BitBasic MCP server have?
- 11 tools: 6 write, 5 read. network-parameters, validator-details, estimate-staking-rewards, governance-proposals, decentralisation-report, latest-news, list-networks, network-status and 3 more.
Does the BitBasic MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BitBasic MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BitBasic MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.