Blender integration through the Model Context Protocol
Nothing to run from here
Modisign 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
11
tools declared
local
runs on your machine
—
downloads a day
What it does
Make animated overlays and edit short videos with Modisign. Everything renders on your computer.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user modisign-mcp '--' npx -y @modisign/mcp
# 2 — ask your agent for something these tools do
# list_overlays, get_overlay, configure_overlay and 8 more
Modisign costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SLAll 1 server
slvDev1 server
1 category
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 Modisign 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 modisign-mcp '--' npx -y @modisign/mcpReconnect, 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 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
11 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.
Find animated overlays by topic, family or niche. Returns compact preset choices and editor links. Reuse the same filters and pass the returned next_cursor as cursor for another page.
No parameter schema on file.
Inspect an overlay preset's editable fields, types, allowed values and limits, looks, aspects, duration and free status before configuring it.
No parameter schema on file.
Configure an animated overlay with editable values, look, aspect, duration or background. Returns its configuration URL and free/Pro tier. Field errors list allowed inputs so you can correct and retry. Changes to free preset text generally need Pro to render.
No parameter schema on file.
Start a local animated overlay render and return job_id. MP4 uses green screen by default; MOV is transparent ProRes 4444; WebM is transparent VP9. Needs the user's FFmpeg. Free configurations need no login; others need Pro. Poll job_status for the file.
No parameter schema on file.
Render an overlay transparently and composite it onto one local video (up to 60 seconds) at start_seconds. Automatically selects and reauthorizes the nearest supported aspect, returned as aspect. The start must fit the overlay within the video. Returns job_id; poll job_status. Produces H.264/AAC…
No parameter schema on file.
Create a finished local Studio video from ordered clips/photos, trims, fill/fit, normalized pan (0–1), zoom (1–3), photo slow zoom, audio settings and source-second punch-ins. Up to 300 clips, 180 seconds after crossfades. after_clip is zero-based; transitions clamp to Studio limits. Remove…
No parameter schema on file.
Transcribe English speech in one local video (up to 180 seconds) using an English speech model on your computer. Optional in/out trim seconds; returned line times are source seconds. The transcript text is returned to your assistant/provider, so call only when the user wants to review or correct…
No parameter schema on file.
Check a local video job's state and progress (0–1). A done job includes the local artifact path, MIME type, bytes, duration and any history warning. Jobs last for this server process.
No parameter schema on file.
Cancel a queued or running local video job and clean its temporary files. A completed artifact is retained.
No parameter schema on file.
Check whether Modisign is signed in and has current Pro access. Anonymous free overlays work without signing in. Returns sign-in instructions when needed.
No parameter schema on file.
Start Modisign device sign-in. Show the returned verification URL and code to the user; they sign in with Google and explicitly approve. Polling continues in the background. Use account_status to check completion. This tool never opens a browser or returns credentials.
No parameter schema on file.
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 Modisign 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.1 · scanned 15 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 · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digeste865cf69339ebc9a32e1ea88063544d90e33c6c8d6b05a7013314374b923944d
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 (11 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 |
|---|---|---|
| list_overlays | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_overlay | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| configure_overlay | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| render_overlay | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| add_overlay_to_video | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| edit_video | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_transcript | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| job_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| cancel_job | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| account_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| login | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digeste865cf69339ebc9a
Scanned2026-10-15
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.1. Pin a release below and the command asks for exactly that one.
0.1.1
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 Modisign 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.