Remote MCP · Endpoint

AskHound MCP server

No. AskHound answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://askhound.haullabs.dev/api/mcp

The last check completed an MCP handshake.

Registry name
dev.haullabs/askhound
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
169 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find people asking for or seeking alternatives to a product, live from Stack Exchange and Bluesky.
Listing
From the official MCP registry (active).
Recent checks of AskHound
CheckedResultHandshake
34 minutes agoHandshake completed169 ms
9 days agoHandshake completed155 ms
10 days agoHandshake completed908 ms
11 days agoHandshake completed1.09 s
12 days agoHandshake completed101 ms
14 days agoHandshake completed256 ms
14 days agoHandshake completed91 ms
15 days agoHandshake completed103 ms
17 days agoHandshake completed154 ms
19 days agoHandshake completed801 ms
21 days agoHandshake completed115 ms
24 days agoHandshake completed174 ms
26 days agoHandshake completed375 ms
28 days agoHandshake completed623 ms

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

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