Remote MCP · Endpoint

Sports Feeds MCP server

No. Sports Feeds answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://gateway.pipeworx.io/sports-feeds/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/sports-feeds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Sports Feeds MCP.
Listing
From the official MCP registry (active).
Recent checks of Sports Feeds
CheckedResultHandshake
4 hours agoHandshake completed94 ms
1 day agoHandshake completed111 ms
3 days agoHandshake completed108 ms
3 days agoHandshake completed135 ms
4 days agoHandshake completed64 ms
6 days agoHandshake completed112 ms
7 days agoHandshake completed141 ms
10 days agoHandshake completed71 ms
13 days agoHandshake completed98 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed70 ms
19 days agoHandshake completed62 ms
21 days agoHandshake completed46 ms
23 days agoHandshake completed54 ms
25 days agoHandshake completed187 ms
27 days agoHandshake completed56 ms
28 days agoHandshake completed55 ms
29 days agoHandshake completed81 ms

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

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