Remote MCP · Endpoint

PuckAPI MCP server

No. PuckAPI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.puckapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.noahowsh/puckapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
175 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
NHL and PWHL stats, play-by-play, expected goals and odds. REST API and MCP server. Free to start.
Listing
From the official MCP registry (active).
Recent checks of PuckAPI
CheckedResultHandshake
2 hours agoHandshake completed175 ms
2 days agoHandshake completed115 ms
4 days agoHandshake completed115 ms
5 days agoHandshake completed116 ms
7 days agoHandshake completed129 ms
8 days agoHandshake completed112 ms
9 days agoHandshake completed127 ms
12 days agoHandshake completed112 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed118 ms
17 days agoHandshake completed124 ms
18 days agoHandshake completed199 ms
19 days agoCredentials required—
20 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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