Remote MCP · Endpoint

convention.sh MCP server

No. convention.sh answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.convention.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.convention/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ship production-ready TypeScript code in half the time, at half the cost.
Listing
From the official MCP registry (active).
Recent checks of convention.sh
CheckedResultHandshake
1 hour agoHandshake completed92 ms
2 days agoHandshake completed138 ms
4 days agoHandshake completed197 ms
5 days agoHandshake completed79 ms
7 days agoHandshake completed124 ms
8 days agoHandshake completed92 ms
9 days agoHandshake completed99 ms
12 days agoHandshake completed50 ms
13 days agoHandshake completed58 ms
15 days agoHandshake completed57 ms
16 days agoHandshake completed51 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed44 ms
20 days agoHandshake completed69 ms
21 days agoHandshake completed58 ms
21 days agoHandshake completed143 ms
23 days agoHandshake completed49 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 convention.sh and makes no claim about it beyond what these checks measured.