Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
Expo Launch Video is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
16
downloads a day
local
runs on your machine
196
downloads in 30d
What it does
Record your Expo app on a real phone and edit a 1080p launch video with motion graphics and sound.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user expo-launch-video-mcp '--' npx -y expo-launch-video
# 2 — ask your agent for something these tools do
# video_capture, video_record, video_capture_tap and 7 more
Expo Launch Video costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RUAll 2 servers
Rudrasamadhiya2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Expo Launch Video as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user expo-launch-video-mcp '--' npx -y expo-launch-videoReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take EXPO_MCP_PORT (Port the phone connects to (default 8347)), LAUNCH_VIDEO_PORT (Studio web server port (default 8790)), ANTHROPIC_API_KEY (Optional: lets the studio send free-form edits to Claude) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Capture app screens for the launch video: screenshot, element positions and the full scroll content. Give routes to capture several screens in one call (in video order), or nothing to capture the current screen.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| routes | array | no | expo-router paths, e.g. ["/dashboard", "/analytics"] |
| name | string | no | name for the current screen when routes is empty |
| scroll | boolean | no | capture scroll content (default true) |
Screen-record the phone for a few seconds (real frames, ~6-12 fps): optionally navigate first, scroll smoothly, or tap an element mid-way. The clip plays in the video as a live recording.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route | string | no | page to open; the opening (loading, entrance animations) is recorded live |
| name | string | no | — |
| seconds | number | no | 1-15, default 4 |
| scroll | no | scroll smoothly while recording (true, or distance in dp) | |
| scrollFrom | number | no | when scrolling starts, as a fraction of the recording (default 0.5 with route: hold while the page loads) |
| liveLoad | boolean | no | record the page opening (default true when route is given) |
| tap | string | no | visible text of an element to tap mid-recording |
| tapAt | number | no | second at which to tap (default: halfway) |
Capture an interaction: the current screen, a tap on an element (animated finger + ripple in the video) and the screen it leads to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | no | — |
| text | string | no | — |
| testID | string | no | — |
| name | string | no | name for the screen before the tap |
Build the video timeline from all captured screens: intro, one scene per screen with automatic timing, zooms, scroll speed-ups and captions, then an outro. Replaces the current timeline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| targetSeconds | number | no | desired total length |
| format | string | no | — |
| appName | string | no | — |
| tagline | string | no | — |
| cta | string | no | — |
Show the current video timeline (compact).
No parameter schema on file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ops | array | yes | — |
Open the studio in the browser: live preview, timeline, per-scene controls and a prompt box where the user can type edits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| open | boolean | no | open the browser (default true) |
Render the video to MP4 (in the studio tab, opening it if needed) and return the file path.
No parameter schema on file.
Wait for the user to type an edit request in the studio prompt box (ones the studio could not apply itself). Apply it with video_edit, answer with video_reply, then call this again to keep collaborating.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timeoutSeconds | integer | no | default 600 |
Show a short message to the user in the studio chat.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Expo Launch Video or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.1.2 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestda4598eeb2ac034fe4983ea071b9ddca3ec2c82e6fc1f14dd4245efd23117489
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| video_capture | no tags | |
| video_record | no tags | |
| video_capture_tap | no tags | |
| video_plan | no tags | |
| video_timeline | no tags | |
| video_edit | no tags | |
| video_studio | no tags | |
| video_render | no tags | |
| video_wait_for_prompt | no tags | |
| video_reply | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestda4598eeb2ac034f
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.2. Pin a release below and the command asks for exactly that one.
0.1.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Expo Launch Video can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.