Remote MCP · Endpoint

Hunch MCP server

No. Hunch answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://hunchsheet.app/mcp/%7Bapi_key%7D

The last check completed an MCP handshake.

Registry name
app.hunchsheet/hunch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
174 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Calibrated judgments for text: yes/no probabilities, picks from your options, or scores.
Listing
From the official MCP registry (active).
Recent checks of Hunch
CheckedResultHandshake
3 hours agoHandshake completed174 ms
2 days agoHandshake completed117 ms
4 days agoHandshake completed217 ms
6 days agoHandshake completed123 ms
8 days agoHandshake completed92 ms
10 days agoHandshake completed122 ms
12 days agoHandshake completed90 ms
14 days agoHandshake completed125 ms
15 days agoHandshake completed117 ms
16 days agoHandshake completed158 ms
18 days agoHandshake completed151 ms
20 days agoHandshake completed91 ms
22 days agoHandshake completed103 ms
24 days agoHandshake completed89 ms
25 days agoHandshake completed84 ms

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

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