Remote MCP · Endpoint
Homespun MCP server
No. Homespun answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 250 ms
- Tools exposed
- 27 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
- Website
- https://homespun.dev/
- Repository
- https://github.com/homespunapps/homespun
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 250 ms |
| 1 day ago | Handshake completed | 251 ms |
| 2 days ago | Handshake completed | 242 ms |
| 3 days ago | Handshake completed | 257 ms |
| 4 days ago | Handshake completed | 508 ms |
| 5 days ago | Handshake completed | 247 ms |
| 6 days ago | Handshake completed | 257 ms |
| 9 days ago | Handshake completed | 259 ms |
| 12 days ago | Handshake completed | 499 ms |
| 14 days ago | Handshake completed | 258 ms |
| 16 days ago | Handshake completed | 246 ms |
| 18 days ago | Handshake completed | 249 ms |
| 20 days ago | Handshake completed | 251 ms |
| 22 days ago | Handshake completed | 250 ms |
| 24 days ago | Handshake completed | 267 ms |
| 26 days ago | Handshake completed | 265 ms |
| 27 days ago | Handshake completed | 260 ms |
| 29 days ago | Handshake completed | 248 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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.