Remote MCP · Endpoint

hackshop MCP server

No. hackshop answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.hackshop.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.hackshop/hackshop-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
488 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Plan and build a physical body for your AI agent: boards, parts list, assembly and pairing.
Website
https://www.hackshop.dev/
Listing
From the official MCP registry (active).
Recent checks of hackshop
CheckedResultHandshake
1 hour agoHandshake completed488 ms
2 days agoHandshake completed99 ms
5 days agoHandshake completed135 ms
7 days agoHandshake completed89 ms
9 days agoHandshake completed248 ms
11 days agoHandshake completed98 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed294 ms
17 days agoHandshake completed61 ms
19 days agoHandshake completed80 ms
20 days agoHandshake completed591 ms
21 days agoHandshake completed115 ms
23 days agoHandshake completed119 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with hackshop and makes no claim about it beyond what these checks measured.