Remote MCP · Endpoint

VectoSolve MCP server

No. VectoSolve answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://vectosolve.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Vectosolve/vectosolve
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Convert PNG/JPG images to clean SVG, DXF or EPS vectors for cutting machines, laser and print.
Listing
From the official MCP registry (active).
Recent checks of VectoSolve
CheckedResultHandshake
3 hours agoHandshake completed100 ms
4 days agoHandshake completed94 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed142 ms
15 days agoHandshake completed103 ms
17 days agoHandshake completed130 ms
18 days agoHandshake completed95 ms
19 days agoHandshake completed298 ms
20 days agoHandshake completed60 ms
21 days agoHandshake completed478 ms
23 days agoHandshake completed137 ms

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

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