Remote MCP · Endpoint

FastballAPI MCP server

No. FastballAPI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.fastballapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.noahowsh/fastballapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
MLB since 2015 plus college: pitches, plate appearances, box scores, odds by book. REST and MCP.
Listing
From the official MCP registry (active).
Recent checks of FastballAPI
CheckedResultHandshake
2 hours agoHandshake completed128 ms
1 day agoHandshake completed110 ms
2 days agoHandshake completed113 ms
3 days agoHandshake completed119 ms
4 days agoHandshake completed115 ms
5 days agoHandshake completed133 ms
6 days agoHandshake completed148 ms
9 days agoHandshake completed143 ms
11 days agoHandshake completed193 ms
14 days agoHandshake completed120 ms
16 days agoHandshake completed126 ms
18 days agoHandshake completed156 ms
20 days agoHandshake completed131 ms
22 days agoHandshake completed112 ms
24 days agoHandshake completed123 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 FastballAPI and makes no claim about it beyond what these checks measured.