Remote MCP · Endpoint

Bullrun MCP server

No. Bullrun answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://mcp.bull-run.org/mcp

The last check completed an MCP handshake.

Registry name
org.bull-run/bullrun
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
337 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Global stock research, ML forecasts, valuation signals, screeners & portfolio tracking in Claude
Listing
From the official MCP registry (active).
Recent checks of Bullrun
CheckedResultHandshake
9 hours agoHandshake completed337 ms
2 days agoHandshake completed866 ms
4 days agoHandshake completed348 ms
5 days agoHandshake completed335 ms
7 days agoHandshake completed364 ms
8 days agoHandshake completed349 ms
9 days agoHandshake completed335 ms
12 days agoHandshake completed335 ms
13 days agoHandshake completed338 ms
15 days agoHandshake completed350 ms
16 days agoHandshake completed340 ms
17 days agoHandshake completed337 ms
19 days agoHandshake completed330 ms
19 days agoHandshake completed337 ms
20 days agoHandshake completed338 ms
21 days agoHandshake completed361 ms
23 days agoHandshake completed390 ms

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

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 Bullrun and makes no claim about it beyond what these checks measured.