Remote MCP · Endpoint

Hire Solidmade MCP server

No. Hire Solidmade answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://solidmade-mcp.solidmade.workers.dev/mcp?src=mcpreg-co

The last check completed an MCP handshake.

Registry name
co.solidmade/hire-solidmade
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hire a studio for Shopify, web, automation and data jobs: live services, USD prices, quote requests.
Listing
From the official MCP registry (active).
Recent checks of Hire Solidmade
CheckedResultHandshake
5 hours agoHandshake completed56 ms
9 days agoHandshake completed117 ms
10 days agoHandshake completed70 ms
11 days agoHandshake completed53 ms
12 days agoHandshake completed53 ms
14 days agoHandshake completed59 ms
14 days agoHandshake completed62 ms
15 days agoHandshake completed100 ms
17 days agoHandshake completed127 ms
19 days agoHandshake completed55 ms
21 days agoHandshake completed65 ms
24 days agoHandshake completed49 ms
26 days agoHandshake completed127 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 Hire Solidmade and makes no claim about it beyond what these checks measured.