Remote MCP · Endpoint

StrikerAPI MCP server

No. StrikerAPI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.strikerapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.noahowsh/strikerapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Premier League, MLS and European football: lineups, shot maps, xG, tables and odds. REST and MCP.
Listing
From the official MCP registry (active).
Recent checks of StrikerAPI
CheckedResultHandshake
1 hour agoHandshake completed114 ms
1 day agoHandshake completed113 ms
2 days agoHandshake completed111 ms
3 days agoHandshake completed117 ms
4 days agoHandshake completed138 ms
5 days agoHandshake completed140 ms
6 days agoHandshake completed123 ms
9 days agoHandshake completed255 ms
11 days agoHandshake completed125 ms
14 days agoHandshake completed119 ms
16 days agoHandshake completed288 ms
18 days agoHandshake completed160 ms
20 days agoHandshake completed212 ms
22 days agoHandshake completed121 ms
24 days agoHandshake completed124 ms

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

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