Bostrom MCP Server

bostrom-mcp npm v0.8.1

Published by cyberia-to — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 83

Each tool and what it can reach — statically extracted from the published source.

  • graph_particleingests untrusted input
  • contract_executeno sensitive capability
  • contract_execute_multino sensitive capability
  • economy_balancesno sensitive capability
  • economy_inflationno sensitive capability
  • economy_mint_priceno sensitive capability
  • economy_poolsno sensitive capability
  • economy_stakingno sensitive capability
  • economy_supplyno sensitive capability
  • gov_paramsno sensitive capability
Show 73 more tools ↓
  • gov_proposal_detailno sensitive capability
  • gov_proposalsno sensitive capability
  • gov_validatorsno sensitive capability
  • graph_create_cyberlinkno sensitive capability
  • graph_create_cyberlinksno sensitive capability
  • graph_create_knowledgeno sensitive capability
  • graph_investmintno sensitive capability
  • graph_neuronno sensitive capability
  • graph_pin_contentno sensitive capability
  • graph_rankno sensitive capability
  • graph_recent_linksno sensitive capability
  • graph_searchno sensitive capability
  • graph_statsno sensitive capability
  • grid_create_routeno sensitive capability
  • grid_delete_routeno sensitive capability
  • grid_edit_routeno sensitive capability
  • grid_list_routesno sensitive capability
  • ibc_channelsno sensitive capability
  • ibc_transferno sensitive capability
  • infra_chain_statusno sensitive capability
  • infra_tx_detailno sensitive capability
  • infra_tx_searchno sensitive capability
  • li_burn_statsno sensitive capability
  • li_claim_referral_rewardsno sensitive capability
  • li_claim_rewardsno sensitive capability
  • li_claim_unbondingno sensitive capability
  • li_community_poolno sensitive capability
  • li_core_configno sensitive capability
  • li_emissionno sensitive capability
  • li_mine_configno sensitive capability
  • li_mine_stateno sensitive capability
  • li_mine_statsno sensitive capability
  • li_miner_statsno sensitive capability
  • li_miner_tx_historyno sensitive capability
  • li_recent_proofsno sensitive capability
  • li_refer_configno sensitive capability
  • li_referral_infono sensitive capability
  • li_referrer_ofno sensitive capability
  • li_reward_estimateno sensitive capability
  • li_stakeno sensitive capability
  • li_stake_configno sensitive capability
  • li_stake_infono sensitive capability
  • li_staking_statsno sensitive capability
  • li_submit_proofno sensitive capability
  • li_total_mintedno sensitive capability
  • li_total_stakedno sensitive capability
  • li_unstakeno sensitive capability
  • li_window_statusno sensitive capability
  • liquidity_create_poolno sensitive capability
  • liquidity_depositno sensitive capability
  • liquidity_pool_detailno sensitive capability
  • liquidity_swapno sensitive capability
  • liquidity_withdrawno sensitive capability
  • swap_estimateno sensitive capability
  • swap_tokensno sensitive capability
  • token_burnno sensitive capability
  • token_change_adminno sensitive capability
  • token_createno sensitive capability
  • token_list_createdno sensitive capability
  • token_mintno sensitive capability
  • token_set_metadatano sensitive capability
  • wallet_claim_rewardsno sensitive capability
  • wallet_delegateno sensitive capability
  • wallet_infono sensitive capability
  • wallet_redelegateno sensitive capability
  • wallet_sendno sensitive capability
  • wallet_undelegateno sensitive capability
  • wallet_voteno sensitive capability
  • wasm_clear_adminno sensitive capability
  • wasm_instantiateno sensitive capability
  • wasm_migrateno sensitive capability
  • wasm_update_adminno sensitive capability
  • wasm_uploadno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.8.1 latest A 96/100 0 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bostrom-mcp/badge.svg)](https://mcptrustchecker.com/registry/bostrom-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/bostrom-mcp"><img src="https://mcptrustchecker.com/registry/bostrom-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bostrom-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan bostrom-mcp --online

Use the free API → How scoring works

More in Developer Tools