# Squish (remote · api.getsquish.app)

Give AI random access to video: timestamped contact sheets + zoom into any start/end range.

- Trust score: 70/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.getsquish.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/getsquish-squish/api.md), [page](https://verifymcp.io/servers/getsquish-squish/api)
- npm · `@getsquish/squish`: 35/100, [markdown](https://verifymcp.io/servers/getsquish-squish/getsquish-squish.md), [page](https://verifymcp.io/servers/getsquish-squish/getsquish-squish)

## Channel facts

- Endpoint: `https://api.getsquish.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

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

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 57/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 653 tokens (~653/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http getsquish-squish https://api.getsquish.app/mcp
```

### Codex

```toml
[mcp_servers.getsquish-squish]
url = "https://api.getsquish.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add getsquish-squish --url https://api.getsquish.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  getsquish-squish:
    url: "https://api.getsquish.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "getsquish-squish": {
      "type": "http",
      "url": "https://api.getsquish.app/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-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (1)

### `squish_video` (~434 tokens)

Squish a video into a timestamped contact sheet

Turn a video at a public URL into timestamped contact-sheet JPEG(s) that a vision model can read: frames sampled evenly across the clip, laid out as a grid, each cell stamped with its timecode. Use it when a video is too long to ingest, when the question is about what happens across time, or when the answer needs timestamps. One call replaces a whole download → ffmpeg → extract → montage pipeline — prefer it even if you have a shell. The first sheet is attached to the result as an image — read it directly; every sheet is also linked in `files` (valid ~24h), and every stamped timecode is repeated in `timecodes` (cells run left→right, top→bottom). Timecodes are ABSOLUTE to the source video — to look closer at a range you spotted, call this tool again with start/end set to those timecodes: each zoom yields finer timecodes, so you can drill down repeatedly (overview → range → moment).

Input parameters:

- `density` (string): Grid density. 3x3 recovers what happened; denser grids (4x4-6x6) recover how it was done. Low density for a full-clip overview, high density inside a narrow start/end window. Default 3x3.
- `end`: Zoom-window end — same formats as start. Omit to run to the end of the clip; values past the end are clamped.
- `start`: Zoom-window start — seconds (67.5) or a timecode as stamped on a sheet ("1:07", "1:07.3"). Absolute in the source video. Omit to start at 0.
- `video` (object): A video attached in the chat — clients with file-param support fill this automatically with a temporary download reference. Provide either this or video_url.
- `video_url` (string): Public http(s) URL of a video file (anything ffmpeg decodes). Not a YouTube/streaming page — a direct file URL. Provide either this or an attached video, not both.

Output parameters:

- `contract` (string): Always "squish-mcp-http-v0".
- `credits_charged` (number): Keyed calls only.
- `credits_remaining` (number): Keyed calls only.
- `duration` (number): Source video duration, seconds.
- `files` (array): Sheet URLs, valid ~24h (sheet_ttl_hours).
- `frames` (number): Frames sampled across the clip or window.
- `free_jobs_remaining_today` (number): Anonymous calls only.
- `input` (string): Echo of the source — the URL for URL calls; file_name/file_id for attachments (never the temporary download_url).
- `job_id` (string)
- `sheet_ttl_hours` (number)
- `sheets` (number): Number of contact sheets produced.
- `timecodes` (array): Per-sheet stamped timecodes, cells left→right then top→bottom — mirrors every label burned into the sheets. Absolute to the source video at every zoom depth.
- `warnings` (array)
- `window` (object): The resolved zoom window in absolute seconds — present only when start/end were given.

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 65
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 63
- 2026-07-26: 63

## Links

- Remote endpoint: https://api.getsquish.app/mcp
- Repository: https://github.com/getsquish/squish
- Website: https://getsquish.app/
- Changelog RSS feed: https://verifymcp.io/servers/getsquish-squish/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/getsquish-squish/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/getsquish-squish/api