Remote MCP · Endpoint

Shreddy MCP server

No. Shreddy answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://api.shreddy.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.shreddy/shreddy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
244 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Measured mountain bike jumps and speeds at bike parks: public clips, read-only.
Website
https://www.shreddy.ai/ai
Listing
From the official MCP registry (active).
Recent checks of Shreddy
CheckedResultHandshake
6 hours agoHandshake completed244 ms
2 days agoHandshake completed177 ms
4 days agoHandshake completed218 ms
6 days agoHandshake completed214 ms
8 days agoHandshake completed228 ms
10 days agoHandshake completed213 ms
12 days agoHandshake completed193 ms
13 days agoHandshake completed237 ms
14 days agoHandshake completed218 ms
15 days agoHandshake completed216 ms
18 days agoHandshake completed212 ms
20 days agoHandshake completed212 ms
21 days agoHandshake completed216 ms
23 days agoHandshake completed306 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Shreddy and makes no claim about it beyond what these checks measured.