Skip to content

Show It Works MCP server

app.showitworks/show-it-worksshowitworks.appstreamable-httpv1.0.0Scanned

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

7 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 4 only read.

Tools: 1 delete, 1 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Show It Works MCP server can do

The Show It Works MCP server is published by showitworks.app, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: delete_video), do things that cannot be undone, such as sending, paying or publishing (complete_video_upload) and create or change data (1 tool: create_video_upload). 4 tools only read.

1 tool brings in text other people can write (list_videos).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Deletes or cancels 1Claude Code: deny
  • delete_videoPermanently delete a recording.No findings

    Why it is in this group

    • The name "delete_video" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    Description, as the server wrote it
    Permanently delete a recording.
Can't be undone 1Claude Code: ask
  • complete_video_uploadPublish a pending recording after its direct upload finishes.No findings

    Why it is in this group

    • The name "complete_video_upload" says "upload": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    Description, as the server wrote it
    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.
Changes things 1Claude Code: ask
  • create_video_uploadWrite title, taskName, ownerContext and publicContext in English (code en, locale en-US) — this project's language — and follow that locale for dates and numbers.No findings

    Why it is in this group

    • The name "create_video_upload" says "create": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • list_tasksList the task names already used in this API key's project, so you can reuse an existing one instead of inventing a near-duplicate.No findings

    Why it is in this group

    • The name "list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • list_videosList the recordings in this API key's project, including dashboard reviewer comments and viewed status.Reads text others writeNo findings

    Why it is in this group

    • The name "list_videos" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    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_videosFind 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.No findings

    Why it is in this group

    • The name "search_videos" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://showitworks.app/api/mcp: tools/list returned 7 tools to an anonymous client, including delete_video (destructive), complete_video_upload (irreversible), create_video_upload (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http show-it-works https://showitworks.app/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http show-it-works https://showitworks.app/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__show-it-works__list_videos",
      "mcp__show-it-works__list_tasks",
      "mcp__show-it-works__search_videos",
      "mcp__show-it-works__get_video_link"
    ],
    "ask": [
      "mcp__show-it-works__create_video_upload",
      "mcp__show-it-works__complete_video_upload"
    ],
    "deny": [
      "mcp__show-it-works__delete_video"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as show-it-works. Review it before you use it.

Capability tags behind 1 rule
  • mcp__show-it-works__list_videos untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.showitworks/show-it-works/verify?hash=275c4a3041c5920d5b6f9aa01de1e34e0c0fb39207c963129d7e091d2c84d345" | jq -e '.changed == false'

Pinned hash 275c4a3041c5, from Nov 12, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.showitworks/show-it-works/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.showitworks/show-it-works
[![Anlyon Radar](https://radar.anlyon.com/badge/app.showitworks/show-it-works.svg)](https://radar.anlyon.com/servers/app.showitworks/show-it-works)

Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.

Show It Works MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Show It Works MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Show It Works MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_video.

Can the Show It Works MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: complete_video_upload.

What tools does the Show It Works MCP server have?

7 tools: 1 destructive, 1 irreversible, 1 write, 4 read. delete_video, complete_video_upload, create_video_upload, list_videos, list_tasks, search_videos and get_video_link.

Does the Show It Works MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Show It Works MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Show It Works MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.