Remote MCP · Endpoint

BPJ Startup Research MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://baipiaoji.com/api/startup-mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.f-tiger/bpj-startup-research
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
BPJ startup cases, launch signals and validation plans. Free preview; member tools use scoped keys.
Listing
From the official MCP registry (active).
Recent checks of BPJ Startup Research
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
4 days agoHandshake completed440 ms
14 days agoHandshake completed238 ms
15 days agoHandshake completed442 ms
15 days agoHandshake completed559 ms
17 days agoHandshake completed181 ms
18 days agoHandshake completed180 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed99 ms
21 days agoHandshake completed219 ms
23 days agoHandshake completed153 ms
25 days agoHandshake completed111 ms
28 days agoHandshake completed102 ms

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

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