Remote MCP · Endpoint

harvis.dev MCP server

No. harvis.dev answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://harvis.dev/api/mcp

The last check completed an MCP handshake.

Registry name
dev.harvis/harvis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
971 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Deploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.
Website
https://harvis.dev/
Listing
From the official MCP registry (active).
Recent checks of harvis.dev
CheckedResultHandshake
1 hour agoHandshake completed971 ms
1 day agoHandshake completed917 ms
2 days agoHandshake completed374 ms
3 days agoHandshake completed990 ms
4 days agoHandshake completed686 ms
5 days agoHandshake completed1.52 s
6 days agoHandshake completed972 ms
9 days agoHandshake completed1.28 s
12 days agoHandshake completed1.46 s
14 days agoHandshake completed1.20 s
16 days agoHandshake completed1.30 s
18 days agoHandshake completed975 ms
20 days agoHandshake completed1.01 s
22 days agoHandshake completed362 ms
24 days agoHandshake completed755 ms
26 days agoHandshake completed1.66 s
27 days agoHandshake completed774 ms
28 days agoHandshake completed299 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.

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