Skip to content

BotSharper

by botsharper.com · remote · no sign-in to list tools · v1.3.0 · published by com.botsharper

Test & simulate Solana trading bots on real pump.fun data; flag serial creators & launch teams.

Changes · 7
CompareRegistry entry

7 tools: 7 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http botsharper https://botsharper.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 7Claude Code: ask
  • botsharper_check_walletProtection filter for trading bots: tells whether a Solana address is a serial pump.fun creator (3+ launches in the last 7 days, how often it dumped within 5 minutes, how many of i…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
    Protection filter for trading bots: tells whether a Solana address is a serial pump.fun creator (3+ launches in the last 7 days, how often it dumped within 5 minutes, how many of its launches migrated) and/or a wallet that repeatedly buys in the launch block of a serial creator's tokens (launch team). Check a token's creator before buying. Updated hourly. Facts about the last 7 days, not advice.

    Annotations the server declares

    • title: Check a creator or wallet
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • botsharper_jetonToken sheet for a pump.fun token (mint address) observed by BotSharper: launch time, buyers in the launch block, in the first second and the first 10 seconds, what the creator boug…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
    Token sheet for a pump.fun token (mint address) observed by BotSharper: launch time, buyers in the launch block, in the first second and the first 10 seconds, what the creator bought and sold, share of the 5 largest buyers in the first 5 minutes, migration to PumpSwap, buyers and sellers, volume, and how many buyers appear in the wallet report (including best and weakest fifth). Past facts only, updated hourly: no forecast, no advice.

    Annotations the server declares

    • title: Token sheet
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • botsharper_pump_weatherToday's pump.fun weather (refreshed hourly): launches per hour, share of launches prepared in advance (3+ buyers in the launch block), share of creators dumping within 5 minutes, m…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
    Today's pump.fun weather (refreshed hourly): launches per hour, share of launches prepared in advance (3+ buyers in the launch block), share of creators dumping within 5 minutes, migrations, share of winning positions, which entry speed made money in the last 24 h (launch block / 1-10 s / 10 s-5 min / later), and serial launch teams of the last 7 days. Use it before tuning a bot or when someone asks what is happening on pump.fun now. Past facts, not a forecast.

    Annotations the server declares

    • title: pump.fun weather
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • botsharper_releveWallet report: where a public Solana address ranks among the pump.fun operators measured by BotSharper: percentile, quintile, number of closed positions, share of winning positions…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
    Wallet report: where a public Solana address ranks among the pump.fun operators measured by BotSharper: percentile, quintile, number of closed positions, share of winning positions, average multiple, share of total losses, with the benchmarks of its quintile. Past facts only: no forecast, no advice.

    Annotations the server declares

    • title: Wallet report
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • botsharper_reperesBenchmarks of the five quintiles of measured operators (share of winning positions, share of total losses, multiple) and the size of the measured population.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
    Benchmarks of the five quintiles of measured operators (share of winning positions, share of total losses, multiple) and the size of the measured population.

    Annotations the server declares

    • title: Benchmarks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • botsharper_simulate_botSimulate / backtest a pump.fun sniper or trading bot BEFORE risking SOL: replays its settings on real recent pump.fun launches (fees, priority fee and price impact included, pessim…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
    Simulate / backtest a pump.fun sniper or trading bot BEFORE risking SOL: replays its settings on real recent pump.fun launches (fees, priority fee and price impact included, pessimistic fills) and returns what 3 SOL would have become with 0.1 SOL per trade and 30 trades a day: median final balance, share of replays that ran out of SOL and after how many days, result per trade, share of winning trades, plus the median real result of bots that buy as fast, and a link to the interactive chart where any amount can be tried. Use it when someone asks whether a bot strategy or settings (entry delay, take profit, stop loss, holding time, filters) would make money. Past data, not a forecast, not advice.

    Annotations the server declares

    • title: Simulate a bot
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • botsharper_test_my_botTest / improve / debug a Solana trading bot (pump.fun, PumpSwap, sniper, copy-trading bot): give the bot's public wallet address and get its REAL net result in SOL over the measure…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
    Test / improve / debug a Solana trading bot (pump.fun, PumpSwap, sniper, copy-trading bot): give the bot's public wallet address and get its REAL net result in SOL over the measured period, up to 60 days (fees included, unsold tokens valued at the lower of cost and market price), number of positions, share of winning positions, rank among 100,000+ active bots, and the last 7 days. With a Pro key it also explains WHY: fees paid, unsold bags, entry speed after token launch, share of entries in the launch block, holding time. Use it whenever someone asks how to improve, tune, evaluate or benchmark their crypto trading bot. Past facts only, not advice.

    Annotations the server declares

    • title: Test my bot
    • 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.

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http botsharper https://botsharper.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__botsharper__botsharper_test_my_bot",
      "mcp__botsharper__botsharper_pump_weather",
      "mcp__botsharper__botsharper_simulate_bot",
      "mcp__botsharper__botsharper_check_wallet",
      "mcp__botsharper__botsharper_releve",
      "mcp__botsharper__botsharper_jeton",
      "mcp__botsharper__botsharper_reperes"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as botsharper. Review it before you use it.