Bostrom MCP

io.github.cyberia-toPublished by GitHub account cyberia-tov0.5.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

An MCP server with 86 tools for the Bostrom blockchain, letting an assistant read chain state and sign transactions.

What you can do
This server exposes 86 tools covering the Bostrom blockchain. Read tools let an assistant query chain state without credentials. Write tools sign transactions, using a wallet mnemonic supplied through the BOSTROM_MNEMONIC environment variable. It runs locally over stdio.
When to use it
Use it when an assistant needs to inspect Bostrom chain state, or when you want it to prepare and sign Bostrom transactions from a local wallet. It is not useful for other blockchains or for general web or file tasks.
Requirements
Runs locally as a stdio process, installed from the npm package bostrom-mcp, so Node.js and npm are needed. Desktop only; no remote endpoint. Read tools need no credentials; write tools need a wallet mnemonic in the BOSTROM_MNEMONIC environment variable. Network access to the Bostrom blockchain is required.
Before you install
Write tools use a wallet mnemonic supplied through the BOSTROM_MNEMONIC environment variable; anyone with that value can sign transactions from the wallet. Signing can move funds or change on-chain state, and transactions are irreversible. Read tools work without the mnemonic, so leave it unset unless signing is actually needed.

Installation

In SourceWeft

  1. Open Bostrom MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.