Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Shreddy

REMOTE · API.SHREDDY.AI

Measured mountain bike jumps and speeds at bike parks: public clips, read-only.

Available components

0 this week 85 Trust /100

Last scanned (5 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1454 tokens (~363/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Server version: 2.0.218 → 2.0.222 functional
  • 4 Nov 26 0
    • Server version: 2.0.213 → 2.0.218 functional
  • 3 Nov 26 0
    • Server version: 2.0.209 → 2.0.213 functional
  • 2 Nov 26 0
    • Server version: 2.0.204 → 2.0.209 functional
  • 1 Nov 26 0
    • Server version: 2.0.198 → 2.0.204 functional
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_clips” rewrote its description, which is the text the model reads security
    • Tool “get_clip” rewrote its description, which is the text the model reads security
    • Tool “get_venue” rewrote its description, which is the text the model reads security
    • Server version: 2.0.187 → 2.0.198 functional
    • “search_clips” reworded the description of “metric” cosmetic
  • 30 Oct 26 0
    • Server version: 2.0.186 → 2.0.187 functional
  • 29 Oct 26 0
    • Server version: 2.0.181 → 2.0.186 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.shreddy.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.shreddy.ai CN=Amazon RSA 2048 M04,O=Amazon,C=US 28 Jan 2026 26 Feb 2027 RSA 2048 SHA256-RSA 2ea11cbf2dfe60597bcb9bd5e4711b7
SANs: *.shreddy.ai
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.shreddy.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
shreddy.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.shreddy.ai/mcp Verified 200
http (plaintext) http://api.shreddy.ai/mcp HTTPS enforced 301 https://api.shreddy.ai:443/mcp
MCP tools · 4 exposed · ~922 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_clip ~160

One public clip by id: where and when it was recorded (day and clock time at the venue), the rider if named, every measurement (jump height, speed, lap times, plus airtime), how it was calibrated, and for a group clip (a train of riders) each rider with their own stats, timing and link. `timing` lists each timing line the rider crossed with the lap it closed, the best earlier lap and the difference, and the split from the line before; a rider nobody tagged has crossings with no lap. A clip that is private, removed or does not exist all read as not found.

NameTypeReqDescription
id–yesThe clip id (the number in https://www.shreddy.ai/clips/<id>).
NameTypeReqDescription
date–yes–
featurestring|nullyes–
idintegeryes–
is_trainbooleanyes–
lap_time_snumber|nullyes–
linkstringyes–
measuredbooleanyes–
membersarrayyes–
messagestringyes–
rank–yes–
recorded_at–yes–
recorded_at_localstring|nullyes–
riderstring|nullyes–
riders_in_clipintegeryes–
runstring|nullyes–
setupobjectyes–
statsobjectyes–
thumbnail–yes–
timingarrayyes–
venue–yes–

No examples provided.

get_venue ~122

Everything about one bike park in one call: its runs and their features (with clip counts), how many public clips and measured rides it has, its records (the top 3 public rides for jump height, speed and airtime, biggest first; no lap record yet) and its newest clips, each with a link and its lap time when it has one. `venue` is a name ("bradley", "snow summit") or an id.

NameTypeReqDescription
venue–yesA bike park name ("bradley", "Snow Summit") or its id.
NameTypeReqDescription
candidatesarrayyes–
messagestringyes–
statusstringyes–
venue–yes–

No examples provided.

list_venues ~189

List the bike parks (venues) that have public Shreddy clips: name, city, state, how many clips and how many measured rides, the runs and features there, and a link. Filter by `query` (matches name, city or state) or sort nearest first with `near` (coordinates; for a place name like "San Diego", pass its approximate latitude and longitude). Distances come in km and miles. Use it for "what parks do you have" and to learn valid venue names.

NameTypeReqDescription
limitinteger–How many venues to return (1 to 25, default 25).
nearobject–Sort by distance from this point (decimal degrees). For a city, pass its approximate coordinates.
querystring–Free text matched against venue name, city and state, e.g. "bradley" or "CA".
NameTypeReqDescription
messagestringyes–
venuesarrayyes–

No examples provided.

search_clips ~451

Search public clips. Newest first by default; sort "biggest" or "smallest" with a `metric` for the biggest jumps, most airtime or fastest runs (ranked results list each rider of a group clip on their own, and leave out rides with no value for that metric). Filter by `venue`, `feature` (a feature or a run at the venue, e.g. "double black" or "jump 2"), `rider`, and time (`when`, or `since`/`until`). A newest search includes clips with no measurements (normal: no calibration). Every clip has a link to give the viewer and its lap time (`lap_time_s`) when it has one; laps are not a ranking metric yet. Pass `next_cursor` back as `cursor`, with the same other arguments, for the next page.

NameTypeReqDescription
cursorstring–The next_cursor from the previous page of the same search.
feature––A feature or a run at the venue, by name ("jump 2", "double black") or id. Works without a venue too.
limitinteger–How many clips (1 to 25, default 10).
metricstring–What to rank by: jump_height (default when ranked), speed, or airtime. Lap times are returned on each clip but cannot be ranked.
riderstring–A rider's name. Only riders who linked their account and allow it can be found.
since––Only clips videoed at or after this ISO date (2026-09-01) or datetime.
sortstring–newest (default), or biggest / smallest by `metric`. Giving a metric without a sort means biggest.
until––Only clips videoed at or before this ISO date (the whole day counts) or datetime.
venue––A bike park name ("bradley", "Snow Summit") or its id.
whenstring–today = the last 24 hours, week = the last 7 days, month = the last 30 days, all (default). since/until override it.
NameTypeReqDescription
candidatesarrayyes–
clipsarrayyes–
messagestringyes–
next_cursorstring|nullyes–
queryobjectyes–
resolvedobjectyes–
statusstringyes–
total–yes–

No examples provided.

Install

How do I install the Shreddy MCP server?

Shreddy is a hosted endpoint at https://api.shreddy.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.shreddy.ai

# add to Claude Code
claude mcp add --transport http ai-shreddy-shreddy 'https://api.shreddy.ai/mcp'
Common questions

What is the Shreddy MCP server?

Shreddy is an MCP server listed in the public MCP registry as ai.shreddy/shreddy. Measured mountain bike jumps and speeds at bike parks: public clips, read-only. This page covers its hosted endpoint (https://api.shreddy.ai/mcp).

Is the Shreddy MCP server safe to use?

Shreddy scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Shreddy MCP server expose?

Shreddy exposes 4 tools: list_venues, get_venue, search_clips, get_clip. Their descriptions and schemas cost roughly 922 tokens of context every time the server is loaded.

Does the Shreddy MCP server require authentication?

No. We connected to Shreddy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Shreddy MCP server still maintained?

Shreddy is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.