Remote MCP · Endpoint

Drivestock MCP server

No. Drivestock answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://drivestock.eu/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.clemensschmid1/drivestock
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
449 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
B2B industrial drives & automation: search parts, prices or on request, quote inquiries.
Listing
From the official MCP registry (active).
Recent checks of Drivestock
CheckedResultHandshake
33 minutes agoHandshake completed449 ms
3 days agoHandshake completed383 ms
13 days agoHandshake completed286 ms
13 days agoHandshake completed271 ms
15 days agoHandshake completed298 ms
16 days agoHandshake completed296 ms
17 days agoHandshake completed288 ms
18 days agoHandshake completed304 ms
18 days agoHandshake completed288 ms
20 days agoHandshake completed339 ms
22 days agoHandshake completed291 ms
25 days agoHandshake completed311 ms
27 days agoHandshake completed565 ms

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

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