Remote MCP · Endpoint

MBEstudio MCP server

Yes, as of 33 minutes ago: the server returned an HTTP error.

DownLast checked 33 minutes ago

Server URL

https://studio.vectorstreamsystems.com/mcp

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

Registry name
com.vectorstreamsystems/mbestudio
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
31 tools
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
SysML v2 systems engineering: generate, verify, simulate and export system models from text.
Listing
From the official MCP registry (active).
Recent checks of MBEstudio
CheckedResultHandshake
33 minutes agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed402 ms
13 days agoHandshake completed184 ms
15 days agoHandshake completed160 ms
16 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
25 days agoCredentials required—

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

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