MCP.Market

StoryCapture MCP server

online · 100% uptime
by storycaptures.com·com.storycaptures/storycapture·v0.2.0

Write, rehearse, record and publish website demo videos, from the desktop app or the cloud.

C58/100grade C
What users say
No reviews yet
Be the first
Safety scan
C58/100

not scanned yet

Adoption
New

110 downloads/wk

Reviews

Write one

Nobody has reviewed StoryCapture yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

StoryCapture tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How StoryCapture compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
58/100
higher than 13% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
368 ms
faster than 40% of 30,031 servers
Downloads a week
110
more than 65% of 12,191 servers with a package

Release history: 2 versions in the registry since 2026-10-19, latest 2026-10-31, typically one every 12 days.

Install StoryCapture in Claude Code, Cursor or VS Code

claude mcp add --transport http storycapture https://mcp.storycaptures.com/mcp
Add to Cursor

StoryCapture: common questions

Is StoryCapture MCP server safe?
With care: it is graded C, so read the findings first (58/100). Read the StoryCapture safety report
How do I install StoryCapture?
It runs remotely at mcp.storycaptures.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does StoryCapture need an API key?
Yes. The registry entry asks for STORYCAPTURE_MCP_TOKEN.
Is StoryCapture maintained?
The latest release is v0.2.0.
Is StoryCapture up?
100% of our last 11 checks got an answer. We check remote servers about four times a day.
How does StoryCapture compare with other MCP servers?
safety score 58/100 (higher than 13% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 368 ms (faster than 40% of 30,031 servers). Full comparison.