Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bostrom MCP

NPM · BOSTROM-MCP · SCANNED SEP 22

86-tool MCP server for Bostrom blockchain: read chain state and sign transactions

Available components

npm · bostrom-mcp 0
0 this week 0 Trust /100

Recent critical change

CVE-2026-41242 affects this package (2 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security73
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 194 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 4671 tokens (~55/item across 84 items; 84 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 84 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Bostrom MCP server?

Bostrom MCP runs locally as an npm package, launched with npx -y bostrom-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · bostrom-mcp

# add to Claude Code
claude mcp add cyberia-to-bostrom-mcp -- npx -y bostrom-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "cyberia-to-bostrom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bostrom-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyberia-to-bostrom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bostrom-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add cyberia-to-bostrom-mcp -- npx -y bostrom-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyberia-to-bostrom-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "bostrom-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyberia-to-bostrom-mcp --command npx --arg -y --arg bostrom-mcp
# ~/.hermes/config.yaml
mcp_servers:
  cyberia-to-bostrom-mcp:
    command: "npx"
    args: ["-y", "bostrom-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyberia-to-bostrom-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "bostrom-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add cyberia-to-bostrom-mcp -t stdio -c npx -a -y bostrom-mcp
// mcp.json
{
  "mcpServers": {
    "cyberia-to-bostrom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bostrom-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Sept 26 0
    • Stability: pass → 0.77 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 Sept 26 0
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 3 Sept 26 0
    • Stability: pass → 0.80 functional
  • 2 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Analysed npm/bostrom-mcp@0.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 42 findings
ID CVE Severity Vector Fix available
GHSA-35jp-ww65-95wh CVE-2026-44494 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N yes
GHSA-3g43-6gmg-66jw CVE-2026-44495 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-3p68-rc4w-qgx5 CVE-2025-62718 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-3w6x-2g7m-8v23 CVE-2026-42044 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-42h9-826w-cgv3 CVE-2026-67313 medium yes
GHSA-43fc-jf86-j433 CVE-2026-25639 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-445q-vr5w-6q77 CVE-2026-42037 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4hjh-wcwx-xvwj CVE-2025-58754 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5c9x-8gcm-mpgx CVE-2026-42034 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-62hf-57xw-28j9 CVE-2026-42039 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6chq-wfr3-2hj9 CVE-2026-42035 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-777c-7fjr-54vf CVE-2026-44488 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7q8q-rj6j-mhjq CVE-2026-67319 medium yes
GHSA-898c-q2cr-xwhg CVE-2026-44490 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-fvcv-3m26-pcqx CVE-2026-40175 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-hfxv-24rg-xrqf CVE-2026-44496 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-j5f8-grm9-p9fc CVE-2026-44486 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-jqh4-m9w3-8hp9 CVE-2026-67317 medium yes
GHSA-jr5f-v2jv-69x6 CVE-2025-27152 high yes
GHSA-m7pr-hjqh-92cm CVE-2026-42038 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-mmx7-hfxf-jppx CVE-2026-67316 medium yes
GHSA-p92q-9vqr-4j8v CVE-2026-44487 high yes
GHSA-pf86-5x62-jrwf CVE-2026-42033 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-pmv8-rq9r-6j72 CVE-2026-67312 medium yes
GHSA-pmwg-cvhr-8vh7 CVE-2026-42043 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-q8qp-cvcw-x6jj CVE-2026-42264 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vf2m-468p-8v99 CVE-2026-42036 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-w9j2-pvgh-6h63 CVE-2026-42041 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhjh-pmcv-23jw CVE-2026-42040 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-xx6v-rp6x-q39c CVE-2026-42042 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-848j-6mx2-7j84 CVE-2025-14505 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L no
GHSA-2pr8-phx7-x9h3 CVE-2026-44294 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-66ff-xgx4-vchm CVE-2026-44293 high yes
GHSA-685m-2w69-288q CVE-2026-44289 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-75px-5xx7-5xc7 CVE-2026-44291 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-f38q-mgvj-vph7 CVE-2026-54269 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-fx83-v9x8-x52w CVE-2026-44292 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-jggg-4jg4-v7c6 CVE-2026-45740 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-jvwf-75h9-cwgg CVE-2026-44290 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q6x5-8v7m-xcrf CVE-2026-44288 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wcpc-wj8m-hjx6 CVE-2026-48712 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xq3m-2v4x-88gg CVE-2026-41242 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 172 packages
Packages resolved 172
Deprecated 2
Stale 58
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 84 exposed · ~4,671 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
contract_execute ~77

Execute a CosmWasm smart contract message. Use this for generic contract interactions not covered by specialized tools.

NameTypeReqDescription
contractstringyesContract address (bostrom1...)
fundsarray–Coins to send with the message
memostring–Transaction memo
msgobjectyesExecute message as JSON object

No output schema declared.

No examples provided.

contract_execute_multi ~50

Execute multiple contract messages in a single transaction. More gas-efficient and atomic — all succeed or all fail.

NameTypeReqDescription
memostring–Transaction memo
operationsarrayyesArray of contract operations

No output schema declared.

No examples provided.

economy_balances ~50

Get all token balances for an address (BOOT, HYDROGEN, VOLT, AMPERE, LI, etc.)

NameTypeReqDescription
addressstringyesBostrom address (bostrom1...)

No output schema declared.

No examples provided.

economy_inflation ~19

Get current inflation rate and minting parameters

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

economy_mint_price ~22

Get current Volt and Ampere mint prices (resources module)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

economy_pools ~18

Get liquidity pool stats from the pools module

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

economy_staking ~41

Get staking info for an address: delegations, rewards, and unbonding

NameTypeReqDescription
addressstringyesDelegator address (bostrom1...)

No output schema declared.

No examples provided.

economy_supply ~58

Get total supply for a token denom. Use 'boot' for BOOT, full factory path for LI, etc.

NameTypeReqDescription
denomstringyesToken denom, e.g. 'boot', 'hydrogen', or full factory denom for LI

No output schema declared.

No examples provided.

gov_params ~38

Get chain parameters: staking, slashing, governance, distribution, or minting params

NameTypeReqDescription
modulestringyesModule to get params for

No output schema declared.

No examples provided.

gov_proposal_detail ~29

Get full proposal details including vote tally

NameTypeReqDescription
proposal_idstringyesProposal ID number

No output schema declared.

No examples provided.

gov_proposals ~47

List governance proposals. Filter by status: active (voting), passed, rejected, or all.

NameTypeReqDescription
limitnumber––
statusstring–Filter by proposal status

No output schema declared.

No examples provided.

gov_validators ~41

Get the active validator set with moniker, commission, and voting power

NameTypeReqDescription
limitnumber––
statusstring–Validator bond status

No output schema declared.

No examples provided.

graph_create_cyberlink ~66

Create a cyberlink between two CIDs in the knowledge graph. Requires VOLT and AMPERE energy (use graph_investmint to get them).

NameTypeReqDescription
from_cidstringyesSource particle CID
to_cidstringyesDestination particle CID

No output schema declared.

No examples provided.

graph_create_cyberlinks ~46

Create multiple cyberlinks in a single transaction (batch). More gas-efficient than individual calls.

NameTypeReqDescription
linksarrayyesArray of {from, to} CID pairs

No output schema declared.

No examples provided.

graph_create_knowledge ~101

Compound: pin content to IPFS then create cyberlink(s). Provide from_cid to link FROM an existing particle TO the new content, and/or to_cid to link FROM the new content TO an existing particle.

NameTypeReqDescription
contentstringyesText content to pin
from_cidstring–Existing CID to link FROM (→ new content)
to_cidstring–Existing CID to link TO (new content →)

No output schema declared.

No examples provided.

graph_investmint ~87

Convert HYDROGEN into millivolt or milliampere energy. VOLT powers cyberlink creation, AMPERE powers bandwidth. Length = number of base periods (~5 days each).

NameTypeReqDescription
amountstringyesAmount of HYDROGEN to investmint (base units)
lengthnumberyesNumber of base periods
resourcestringyesResource type

No output schema declared.

No examples provided.

graph_neuron ~34

Get neuron profile: number of cyberlinks created

NameTypeReqDescription
addressstringyesNeuron address (bostrom1...)

No output schema declared.

No examples provided.

graph_particle ~41

Fetch particle content by CID from IPFS. Returns text content (truncated at 50KB).

NameTypeReqDescription
cidstringyesIPFS CID of the particle

No output schema declared.

No examples provided.

graph_pin_content ~48

Pin text content to IPFS and return the CID. Use the returned CID with graph_create_cyberlink to add to knowledge graph.

NameTypeReqDescription
contentstringyesText content to pin

No output schema declared.

No examples provided.

graph_rank ~40

Get the cyberank score for a particle (CID). Higher rank = more important in the knowledge graph.

NameTypeReqDescription
particlestringyesCID of the particle

No output schema declared.

No examples provided.

graph_recent_links ~30

Get the most recent cyberlinks created on Bostrom

NameTypeReqDescription
limitnumber–Max results

No output schema declared.

No examples provided.

graph_search ~79

Search cyberlinks by particle CID or neuron address. Returns linked particles and their creators.

NameTypeReqDescription
limitnumber–Max results
neuronstring–Neuron address (bostrom1...) to find their links
offsetnumber–Pagination offset
particlestring–CID of a particle to find links from/to

No output schema declared.

No examples provided.

graph_stats ~20

Get knowledge graph statistics: total cyberlinks and active neurons

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

grid_create_route ~49

Create an energy route to allocate VOLT/AMPERE to another address.

NameTypeReqDescription
destinationstringyesDestination address (bostrom1...)
namestringyesRoute name/label

No output schema declared.

No examples provided.

grid_delete_route ~26

Delete an energy route.

NameTypeReqDescription
destinationstringyesRoute destination address to delete

No output schema declared.

No examples provided.

grid_edit_route ~58

Edit an existing energy route's allocated value.

NameTypeReqDescription
amountstringyesAmount to allocate (base units)
denomstringyesResource denom (millivolt or milliampere)
destinationstringyesRoute destination address

No output schema declared.

No examples provided.

grid_list_routes ~41

List all energy routes from an address. If no address, uses agent wallet.

NameTypeReqDescription
addressstring–Source address (optional — defaults to agent wallet)

No output schema declared.

No examples provided.

ibc_channels ~19

List active IBC channels with counterparty info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ibc_transfer ~98

Transfer tokens to another chain via IBC. Use ibc_channels to find the correct channel ID.

NameTypeReqDescription
amountstringyesAmount (base units)
channelstringyesIBC channel ID (e.g. 'channel-2')
denomstringyesToken denom to transfer
receiverstringyesReceiver address on destination chain
timeout_minutesnumber–Timeout in minutes (default: 10)

No output schema declared.

No examples provided.

infra_chain_status ~29

Get current Bostrom chain status: latest block height, time, chain ID, sync status

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

infra_tx_detail ~26

Get full decoded transaction by hash

NameTypeReqDescription
txhashstringyesTransaction hash

No output schema declared.

No examples provided.

infra_tx_search ~95

Search transactions by sender address, contract address, or message type.

NameTypeReqDescription
contractstring–Filter by contract address
limitnumber–Max results
message_typestring–Filter by message type, e.g. /cosmwasm.wasm.v1.MsgExecuteContract
offsetnumber–Pagination offset
senderstring–Filter by sender address (bostrom1...)

No output schema declared.

No examples provided.

li_block_context ~46

Get current block hash and data hash (cyberlinks merkle) for lithium v1 mining. Returns height, block_hash (hex), cyberlinks_merkle (hex), time.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

li_burn_stats ~36

Get LI burn stats: total_burned via contract-mediated transfers

NameTypeReqDescription
contractstring–litium-core contract address

No output schema declared.

No examples provided.

li_claim_referral_rewards ~47

Claim accumulated referral rewards from the litium-refer contract. Called by the referrer to collect earned referral share.

NameTypeReqDescription
contractstring–litium-refer contract address

No output schema declared.

No examples provided.

li_claim_rewards ~31

Claim LI staking rewards from the stake contract.

NameTypeReqDescription
contractstring–litium-stake contract address

No output schema declared.

No examples provided.

li_claim_unbonding ~50

Claim matured unbonding LI tokens from the stake contract. Only succeeds after unbonding_period_seconds has elapsed since unstaking.

NameTypeReqDescription
contractstring–litium-stake contract address

No output schema declared.

No examples provided.

li_community_pool ~39

Get unclaimed community pool balance (referral rewards for miners without referrer)

NameTypeReqDescription
contractstring–litium-refer contract address

No output schema declared.

No examples provided.

li_core_config ~35

Get litium-core config: token_denom, admin, paused

NameTypeReqDescription
contractstring–litium-core contract address

No output schema declared.

No examples provided.

li_emission ~48

Get Lithium emission breakdown: alpha, beta, emission_rate, gross_rate, mining_rate, staking_rate, windowed_fees

NameTypeReqDescription
contractstring–litium-mine contract address

No output schema declared.

No examples provided.

li_mine_config ~79

Get litium-mine config: max_proof_age, estimated_gas_cost_uboot, window_size, pid_interval, min_difficulty, alpha, beta, fee_bucket_duration, fee_num_buckets, warmup_base_rate, core/stake/refer/token contracts

NameTypeReqDescription
contractstring–litium-mine contract address

No output schema declared.

No examples provided.

li_mine_state ~41

Get full litium-mine state: config, window_status, stats, emission breakdown

NameTypeReqDescription
contractstring–litium-mine contract address

No output schema declared.

No examples provided.

li_mine_stats ~43

Get aggregate mining stats: total_proofs, total_rewards, unique_miners, avg_difficulty

NameTypeReqDescription
contractstring–litium-mine contract address

No output schema declared.

No examples provided.

li_miner_stats ~55

Get per-miner stats: proofs_submitted, total_rewards, last_proof_time

NameTypeReqDescription
addressstringyesMiner address (bostrom1...)
contractstring–litium-mine contract address

No output schema declared.

No examples provided.

li_miner_tx_history ~45

Get a miner's recent contract execution TX history and total count

NameTypeReqDescription
addressstringyesMiner address (bostrom1...)
limitnumber––

No output schema declared.

No examples provided.

li_recent_proofs ~40

Get recent proof submission transactions for the mine contract

NameTypeReqDescription
contractstring–litium-mine contract address
limitnumber––

No output schema declared.

No examples provided.

li_refer_config ~44

Get litium-refer config: core_contract, mine_contract, community_pool_addr, admin, paused

NameTypeReqDescription
contractstring–litium-refer contract address

No output schema declared.

No examples provided.

li_referral_info ~52

Get referral stats for a referrer: referral_rewards, referrals_count

NameTypeReqDescription
addressstringyesReferrer address (bostrom1...)
contractstring–litium-refer contract address

No output schema declared.

No examples provided.

li_referrer_of ~44

Get who referred a specific miner

NameTypeReqDescription
contractstring–litium-refer contract address
minerstringyesMiner address (bostrom1...)

No output schema declared.

No examples provided.

li_reward_estimate ~60

Estimate LI reward for a given difficulty: gross_reward, estimated_gas_cost_uboot, earns_reward

NameTypeReqDescription
contractstring–litium-mine contract address
difficulty_bitsnumberyesDifficulty in bits (leading zero bits)

No output schema declared.

No examples provided.

Common questions

What is the Bostrom MCP server?

Bostrom MCP is listed in the public MCP registry as io.github.cyberia-to/bostrom-mcp. 86-tool MCP server for Bostrom blockchain: read chain state and sign transactions. This page covers its npm package (bostrom-mcp).

What tools does the Bostrom MCP server expose?

Bostrom MCP exposes 84 tools: graph_search, graph_rank, graph_neuron, graph_particle, graph_recent_links, and 79 more. Their descriptions and schemas cost roughly 4,671 tokens of context every time the server is loaded.

Is the Bostrom MCP server still maintained?

Bostrom MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Bostrom MCP server under?

Bostrom MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.