Remote MCP · Endpoint

Homespun MCP server

No. Homespun answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://homespun.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.homespun/homespun
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
251 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
Listing
From the official MCP registry (active).
Recent checks of Homespun
CheckedResultHandshake
1 hour agoHandshake completed251 ms
2 days agoHandshake completed250 ms
4 days agoHandshake completed267 ms
5 days agoHandshake completed265 ms
7 days agoHandshake completed260 ms
8 days agoHandshake completed248 ms
9 days agoHandshake completed240 ms
12 days agoHandshake completed249 ms
13 days agoHandshake completed251 ms
15 days agoHandshake completed252 ms
16 days agoHandshake completed248 ms
18 days agoHandshake completed253 ms
19 days agoHandshake completed248 ms
20 days agoHandshake completed251 ms
20 days agoHandshake completed238 ms
21 days agoHandshake completed246 ms
22 days agoHandshake completed245 ms

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

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