Remote MCP · Endpoint

Vectree MCP server

No. Vectree answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vectree.io/mcp

The last check completed an MCP handshake.

Registry name
io.vectree/diagrams
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
344 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and read ~95,000 interactive concept diagrams that explain how things work — visually.
Listing
From the official MCP registry (active).
Recent checks of Vectree
CheckedResultHandshake
1 hour agoHandshake completed344 ms
9 days agoHandshake completed150 ms
10 days agoHandshake completed326 ms
11 days agoHandshake completed326 ms
12 days agoHandshake completed339 ms
14 days agoHandshake completed1.04 s
14 days agoHandshake completed336 ms
15 days agoHandshake completed331 ms
17 days agoHandshake completed409 ms
19 days agoHandshake completed344 ms
21 days agoHandshake completed354 ms
24 days agoHandshake completed452 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed331 ms

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

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