Remote MCP · Endpoint

Sports Feeds MCP server

No. Sports Feeds answered an MCP handshake 1 day ago.

UpLast checked 1 day 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
46 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Sports Feeds MCP.
Listing
From the official MCP registry (active).
Recent checks of Sports Feeds
CheckedResultHandshake
1 day agoHandshake completed46 ms
3 days agoHandshake completed54 ms
5 days agoHandshake completed187 ms
6 days agoHandshake completed56 ms
8 days agoHandshake completed55 ms
9 days agoHandshake completed81 ms
11 days agoHandshake completed1.45 s
13 days agoHandshake completed92 ms
15 days agoHandshake completed88 ms
16 days agoHandshake completed49 ms
17 days agoHandshake completed41 ms
19 days agoHandshake completed50 ms
20 days agoHandshake completed53 ms
20 days agoHandshake completed35 ms
21 days agoHandshake completed61 ms
22 days agoHandshake completed53 ms

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

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.