mcpbeat Sign in

Show It Works MCP Server

by showitworks Your server? Claim it
not responding

Show It Works is listed as active in the registry but did not answer our last check. It exposes 7 tools.

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

Uptime history 52 days of history · worst day 0%
52 days agonow
0.0%
Uptime 24h
0 of 92 checks
7
Tools
read from the server
94 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct a tool description was rewritten complete_video_upload
17 Oct a tool changed the parameters it asks for complete_video_upload

Show It Works does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add show-it-works --transport http https://showitworks.app/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://showitworks.app/api/mcp
~/.codex/config.toml
[mcp_servers.show-it-works]
url = "https://showitworks.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "show-it-works": {
      "url": "https://showitworks.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "show-it-works": {
      "type": "http",
      "url": "https://showitworks.app/api/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

video
create_video_upload
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.
delete_video
Permanently delete a recording.
get_video_link
Get a public link for a ready recording, with the retainUntil deadline after which the link stops working. Report the expiry alongside the link.
videos
list_videos
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.
search_videos
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.
complete
complete_video_upload
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.
tasks
list_tasks
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.

Endpoints

URLTransportStateLatencyChecked
https://showitworks.app/api/mcp streamable-http answering 94 ms 7 min ago

Alternatives to Show It Works

same job, measured the same way
mnema: decision records for AI coding agents
by mnema-work

Signed, append-only decision records for AI coding agents, over MCP. Verify them offline.

518 installs/wk local only
Concord MCP
by get-concord-ai

Cross-harness communication and shared work-state for AI coding agents.

880 installs/wk local only
Sv Number
by sv-number

Phone numbers for AI agents: order a private number, read the SMS verification code, hand it back.

52 installs/wk local only
Koda
by aabxtract

Verification and memory layer for coding-agent workflows.

77 installs/wk local only
MaterialsCodeGraph
by materialscodegraph

Materials simulations for AI agents over MCP: binding token quote before every run, record after it.

15 tools answering
MCP Test Utils
by jeenyjai

Desktop UI automation for AI agents: verified clicks, UI Automation, OCR, scenario runs, recording

local only
Recraft MCP Server
by muhammetali

Recraft AI Image Generation MCP Server for AI coding agents

78 installs/wk local only
Mailsink
by heocoi

Disposable inboxes for AI agents and CI: catch the verification email, read the OTP or link.

44 installs/wk local only

Show It Works — questions

Answers built from our own checks of this server.

What can Show It Works do?
It exposes 7 tools, read directly from the server on our last check. Among them: complete_video_upload, create_video_upload, delete_video, get_video_link, list_tasks, list_videos and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Show It Works mostly used for?
Its tools cluster around video and videos. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Show It Works working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 94 ms. The bar chart above shows every period we have measured.
The registry lists Show It Works as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Show It Works?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Show It Works need an API key?
No. Show It Works completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.