# Show It Works (remote · showitworks.app)

Verification videos for AI coding agents: record the run, upload over MCP, share a viewer link.

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

## Components

- remote · `showitworks.app`: 85/100 (this document), [markdown](https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp.md), [page](https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp)

## Channel facts

- Endpoint: `https://showitworks.app/api/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- 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-07.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1501 tokens (~214/item across 7 items; 7 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**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "complete_video_upload" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 8 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 Show It Works MCP server?

Show It Works is a hosted endpoint at https://showitworks.app/api/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 app-showitworks-show-it-works 'https://showitworks.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-showitworks-show-it-works": {
      "url": "https://showitworks.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-showitworks-show-it-works": {
      "type": "http",
      "url": "https://showitworks.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-showitworks-show-it-works]
url = "https://showitworks.app/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-showitworks-show-it-works --url 'https://showitworks.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-showitworks-show-it-works:
    url: "https://showitworks.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-showitworks-show-it-works": {
      "Transport": "http",
      "Url": "https://showitworks.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-showitworks-show-it-works -t streamable-http -u 'https://showitworks.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-showitworks-show-it-works": {
      "type": "http",
      "url": "https://showitworks.app/api/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-06 (score 85, 0)

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

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

- [security] Stability: 0.97 → pass

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

- [functional] Stability: pass → 0.97

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

- [security] Stability: 0.97 → pass

### 2026-10-17 (score 85, +1)

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

### 2026-10-15 (score 84, +1)

- [security] Tool “complete_video_upload” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 183 → 214
- [functional improvement] Tool coverage: 33% → 38%
- [cosmetic] “complete_video_upload” reworded the description of “videoId”

### 2026-10-13 (score 83, +1)

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

### 2026-10-12 (score 82, +1)

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

## MCP tools (7)

### `create_video_upload` (~306 tokens)

Write title, taskName, ownerContext and publicContext in English (code en, locale en-US) — this project's language — and follow that locale for dates and numbers. The answer says so when what you sent is not in it. Leave code, identifiers, commands and file paths exactly as they appear in the repository, and leave worktreeName as the checkout's own directory name rather than translating it. This creates a direct R2 upload for an MP4 or WebM recording, filed under the project this API key belongs to. Worktree and task are public; ownerContext is shown to project members only, never through the public link; publicContext is shown only when explicitly supplied as public-safe.

Input parameters:

- `byteSize` (integer, required)
- `filename` (string, required)
- `mimeType` (string, required)
- `ownerContext` (string): Detailed context shown to every member of the project, never to public-link viewers.
- `publicContext` (string): Context explicitly confirmed safe for anyone with the public viewer link. Never derive it from private context.
- `taskName` (string): Concise public task name. Omit it if the task name is not safe to publish.
- `title` (string, required)
- `workspaceName`: Deprecated alias for worktreeName, kept for agents on an older skill version.
- `worktreeName` (string): Public git worktree or repository name. Omit it if the real name is not safe to publish.

### `complete_video_upload` (~239 tokens)

Publish a pending recording after its direct upload finishes. Call only after create_video_upload and a successful PUT of the entire file to the returned upload URL; this tool does not upload bytes. Requires a project API key with video.upload permission. Checks the stored object's byte size, MIME type and MP4/WebM container signature, not the correctness of the work shown or the full media contents. On success, changes PENDING to READY and returns the recording; use get_video_link next to retrieve its public viewer link and report retainUntil. Anyone with that link can watch until retainUntil; delete_video can remove the recording earlier. A size, MIME type or container-signature mismatch refuses publication and initiates deletion of the uploaded object. Failure to inspect the stored object's metadata marks the recording FAILED. For either failure, create a new upload and upload the file again rather than retrying completion on that recording. Only PENDING recordings can be completed: calling again after success returns an error, so use get_video_link instead.

Input parameters:

- `videoId` (string, required): The video.id returned by create_video_upload, after the file has been successfully uploaded using its upload URL.

### `list_videos` (~88 tokens)

List the recordings in this API key's project, including dashboard reviewer comments and viewed status. Expired recordings are omitted; each row's retainUntil is when that recording and its public link are deleted, and firstViewedAt is when someone first played the public link, or null if nobody has. Ignore expiresAt, which is upload-authorization plumbing and always reads as past on a published recording.

### `list_tasks` (~489 tokens)

List the task names already used in this API key's project, so you can reuse an existing one instead of inventing a near-duplicate. Copy `taskName` verbatim into `create_video_upload`. Names are folded case-insensitively and on whitespace, so one entry can cover several spellings, listed as `variants`. `recordingCount` is how many recordings carry the task right now, and `untagged` counts the recordings filed under no task at all. A name is listed while at least one of its recordings is still inside its retention window — 14 to 60 days after upload depending on the project's plan — and once the last of them reaches that deadline the name goes from this list with it. `firstUsedAt`/`lastUsedAt` are upload times. Only your own uploads are counted by default; pass `mine: false` to count every project member's. Without `query`, entries come back most-recently-used first, `truncated` means more names exist than `limit` returned, and `totalTasks` says how many. Other optional filters: `taskName` (substring), `createdAfter`/`createdBefore` (ISO timestamps), `limit`. A filter narrows the recordings that are counted, so the counts and dates then describe that window rather than the project's whole history. Optional `query` instead returns the tasks of the recordings that best match a description of the work, ordered by match quality — only the best-matching recordings nominate a task, so that answer is a shortlist rather than the project's whole vocabulary, `totalTasks` and `truncated` describe just those tasks, and `untagged` is omitted. The counts and dates of a task shown that way still cover every one of its recordings, not only the matching ones. `query` matches by meaning in any language, and a query in English (code en, locale en-US) — this project's language — also matches on wording.

Input parameters:

- `createdAfter` (string)
- `createdBefore` (string)
- `limit` (integer)
- `mine` (boolean): Count only your own uploads. Defaults to true; pass false to include every project member's recordings.
- `query` (string)
- `taskName` (string): Substring of a task name, matched case-insensitively.

### `search_videos` (~224 tokens)

Find recordings in this API key's project by meaning as well as by wording — describe what the session was about, or name a task, and the closest recordings come back ranked. Use it before inventing a new TASK value, to find the recordings an earlier session already filed under one. Optional filters: taskName (substring), mine (only your own uploads — unlike list_tasks, this one searches every project member's recordings unless you pass it), createdAfter/createdBefore (ISO timestamps) and limit. Expired recordings are never returned. A query in any language works, because matching is semantic; this project works in English (code en, locale en-US), and a query in that language also matches on wording, which is the more precise half.

Input parameters:

- `createdAfter` (string)
- `createdBefore` (string)
- `limit` (integer)
- `mine` (boolean)
- `query` (string, required)
- `taskName` (string): Concise public task name. Omit it if the task name is not safe to publish.

### `get_video_link` (~45 tokens)

Get a public link for a ready recording, with the retainUntil deadline after which the link stops working. Report the expiry alongside the link.

Input parameters:

- `videoId` (string, required)

### `delete_video` (~22 tokens)

Permanently delete a recording.

Input parameters:

- `videoId` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp#diagnostics

## Score history

- 2026-11-07: 85
- 2026-11-06: 85
- 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: 85
- 2026-10-25: 85
- 2026-10-24: 85
- 2026-10-23: 85
- 2026-10-22: 85
- 2026-10-21: 85
- 2026-10-20: 85
- 2026-10-19: 85
- 2026-10-18: 85
- 2026-10-17: 85
- 2026-10-16: 84
- 2026-10-15: 84
- 2026-10-14: 83
- 2026-10-13: 83
- 2026-10-12: 82
- 2026-10-10: 81
- 2026-10-08: 81
- 2026-10-06: 80

## Common questions

### What is the Show It Works MCP server?

Show It Works is an MCP server listed in the public MCP registry as app.showitworks/show-it-works. Verification videos for AI coding agents: record the run, upload over MCP, share a viewer link. This page covers its hosted endpoint (https://showitworks.app/api/mcp).

### Is the Show It Works MCP server safe to use?

Show It Works 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 Show It Works MCP server expose?

Show It Works exposes 7 tools: create_video_upload, complete_video_upload, list_videos, list_tasks, search_videos, and 2 more. Their descriptions and schemas cost roughly 1,413 tokens of context every time the server is loaded.

### Does the Show It Works MCP server require authentication?

Yes. Show It Works asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Show It Works MCP server still maintained?

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

### What did VerifyMCP test on the Show It Works MCP server?

VerifyMCP ran 13 checks on Show It Works, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://showitworks.app/api/mcp
- Authorisation metadata: https://showitworks.app/.well-known/oauth-protected-resource/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-showitworks-show-it-works/api-mcp