# Shreddy (remote · api.shreddy.ai)

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

- Trust score: 85/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.shreddy.ai`: 85/100 (this document), [markdown](https://verifymcp.io/servers/ai-shreddy-shreddy/api.md), [page](https://verifymcp.io/servers/ai-shreddy-shreddy/api)

## Channel facts

- Endpoint: `https://api.shreddy.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http ai-shreddy-shreddy 'https://api.shreddy.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-shreddy-shreddy": {
      "url": "https://api.shreddy.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-shreddy-shreddy": {
      "type": "http",
      "url": "https://api.shreddy.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-shreddy-shreddy]
url = "https://api.shreddy.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-shreddy-shreddy": {
      "type": "remote",
      "url": "https://api.shreddy.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-shreddy-shreddy --url 'https://api.shreddy.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-shreddy-shreddy:
    url: "https://api.shreddy.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-shreddy-shreddy": {
      "Transport": "http",
      "Url": "https://api.shreddy.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-shreddy-shreddy -t streamable-http -u 'https://api.shreddy.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-shreddy-shreddy": {
      "type": "http",
      "url": "https://api.shreddy.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, 0)

- [functional] Server version: 2.0.218 → 2.0.222

### 2026-11-04 (score 85, 0)

- [functional] Server version: 2.0.213 → 2.0.218

### 2026-11-03 (score 85, 0)

- [functional] Server version: 2.0.209 → 2.0.213

### 2026-11-02 (score 85, 0)

- [functional] Server version: 2.0.204 → 2.0.209

### 2026-11-01 (score 85, 0)

- [functional] Server version: 2.0.198 → 2.0.204

### 2026-10-31 (score 85, 0)

- [security] 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
- [functional] Server version: 2.0.187 → 2.0.198
- [cosmetic] “search_clips” reworded the description of “metric”

### 2026-10-30 (score 85, 0)

- [functional] Server version: 2.0.186 → 2.0.187

### 2026-10-29 (score 85, 0)

- [functional] Server version: 2.0.181 → 2.0.186

## MCP tools (4)

### `list_venues` (~189 tokens)

List bike parks

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.

Input parameters:

- `limit` (integer): How many venues to return (1 to 25, default 25).
- `near` (object): Sort by distance from this point (decimal degrees). For a city, pass its approximate coordinates.
- `query` (string): Free text matched against venue name, city and state, e.g. "bradley" or "CA".

Output parameters:

- `message` (string)
- `venues` (array)

### `get_venue` (~122 tokens)

Bike park details

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.

Input parameters:

- `venue` (required): A bike park name ("bradley", "Snow Summit") or its id.

Output parameters:

- `candidates` (array)
- `message` (string)
- `status` (string)
- `venue`

### `search_clips` (~451 tokens)

Search clips

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.

Input parameters:

- `cursor` (string): 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.
- `limit` (integer): How many clips (1 to 25, default 10).
- `metric` (string): What to rank by: jump_height (default when ranked), speed, or airtime. Lap times are returned on each clip but cannot be ranked.
- `rider` (string): 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.
- `sort` (string): 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.
- `when` (string): today = the last 24 hours, week = the last 7 days, month = the last 30 days, all (default). since/until override it.

Output parameters:

- `candidates` (array)
- `clips` (array)
- `message` (string)
- `next_cursor` (string|null)
- `query` (object)
- `resolved` (object)
- `status` (string)
- `total`

### `get_clip` (~160 tokens)

Clip details

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.

Input parameters:

- `id` (required): The clip id (the number in https://www.shreddy.ai/clips/<id>).

Output parameters:

- `date`
- `feature` (string|null)
- `id` (integer)
- `is_train` (boolean)
- `lap_time_s` (number|null)
- `link` (string)
- `measured` (boolean)
- `members` (array)
- `message` (string)
- `rank`
- `recorded_at`
- `recorded_at_local` (string|null)
- `rider` (string|null)
- `riders_in_clip` (integer)
- `run` (string|null)
- `setup` (object)
- `stats` (object)
- `thumbnail`
- `timing` (array)
- `venue`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-shreddy-shreddy/api#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 85
- 2026-10-26: 84
- 2026-10-25: 84
- 2026-10-24: 84
- 2026-10-23: 83
- 2026-10-22: 83
- 2026-10-21: 82
- 2026-10-20: 82
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-05: 75
- 2026-10-04: 75
- 2026-10-03: 74
- 2026-10-02: 74

## 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.

## Links

- Remote endpoint: https://api.shreddy.ai/mcp
- Website: https://www.shreddy.ai/ai
- Changelog RSS feed: https://verifymcp.io/servers/ai-shreddy-shreddy/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-shreddy-shreddy/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-shreddy-shreddy/api