Remote MCP · Endpoint

Hat Trick Local Directory MCP server

No. Hat Trick Local Directory answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://hattricklocal.com/mcp

The last check completed an MCP handshake.

Registry name
com.hattricklocal/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
83 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
US youth sports clubs and sports stores: registration windows, fees, tryouts and claim links.
Listing
From the official MCP registry (active).
Recent checks of Hat Trick Local Directory
CheckedResultHandshake
37 minutes agoHandshake completed83 ms
4 days agoHandshake completed448 ms
7 days agoHandshake completed148 ms
16 days agoHandshake completed69 ms
16 days agoHandshake completed637 ms
18 days agoHandshake completed237 ms
19 days agoHandshake completed93 ms
20 days agoHandshake completed127 ms
21 days agoHandshake completed59 ms
22 days agoHandshake completed572 ms
23 days agoHandshake completed534 ms
26 days agoHandshake completed88 ms

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

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