Remote MCP · Endpoint

Shreddy MCP server

No. Shreddy answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes 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
437 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
20 minutes agoHandshake completed437 ms
8 days agoHandshake completed202 ms
9 days agoHandshake completed213 ms
11 days agoHandshake completed200 ms
12 days agoHandshake completed201 ms
13 days agoHandshake completed236 ms
14 days agoHandshake completed199 ms
14 days agoHandshake completed210 ms
16 days agoHandshake completed229 ms
19 days agoHandshake completed196 ms
21 days agoHandshake completed260 ms
24 days agoHandshake completed244 ms
26 days agoHandshake completed177 ms
28 days agoHandshake completed218 ms

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

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.