Remote MCP · Endpoint

BotSharper MCP server

No. BotSharper answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://botsharper.com/mcp

The last check completed an MCP handshake.

Registry name
com.botsharper/botsharper
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Test & simulate Solana trading bots on real pump.fun data; flag serial creators & launch teams.
Listing
From the official MCP registry (active).
Recent checks of BotSharper
CheckedResultHandshake
1 hour agoHandshake completed205 ms
1 day agoHandshake completed117 ms
2 days agoHandshake completed78 ms
3 days agoHandshake completed66 ms
4 days agoHandshake completed84 ms
5 days agoHandshake completed210 ms
6 days agoHandshake completed110 ms
9 days agoHandshake completed50 ms
11 days agoHandshake completed67 ms
14 days agoHandshake completed57 ms
16 days agoHandshake completed48 ms
18 days agoHandshake completed84 ms
20 days agoHandshake completed55 ms
22 days agoHandshake completed71 ms
24 days agoHandshake completed83 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with BotSharper and makes no claim about it beyond what these checks measured.