Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Menivor 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.
What it does
Create short-form vertical reels and ads, check pricing, and get your finished MP4 from Menivor.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http menivor-mcp https://menivor.com/api/mcp --header 'Authorization: Bearer ${MENIVOR_API_KEY}'
# 2 — ask your agent for something these tools do
# create_reel, get_job, ad_from_url and 6 more
It needs MENIVOR_API_KEY (Bearer followed by your personal Menivor API key from https://menivor.com/account/api-keys): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
Menivor costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads MENIVOR_API_KEY (Bearer followed by your personal Menivor API key from https://menivor.com/account/api-keys) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx MENIVOR_API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http menivor-mcp https://menivor.com/api/mcp --header 'Authorization: Bearer ${MENIVOR_API_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer followed by your personal Menivor API key from https://menivor.com/account/api-keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 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.
Start rendering a vertical short-form reel. Uses one reel credit per variant, reserved at start and released if the render fails. Returns job_id; poll it with get_job.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | What the reel is about (the topic or hook) |
| script | string | no | Optional narration script; generated from the subject when omitted |
| language | string | no | Script language code, e.g. en or tr; defaults to auto |
| aspect | string | no | Output aspect ratio; defaults to 9:16 |
| voice_name | string | no | Voice id from GET /voices |
| avatar_id | string | no | Avatar presenter id from GET /avatars |
| screen_recording_key | string | no | Key of an uploaded screen recording you own |
| caption_style | string | no | Caption style id |
| variants | integer | no | Render 1 to 3 variants; each uses one credit |
Read a reel job's state, progress and, once finished, its download URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | Job id returned by create_reel |
Extract a product from a URL and draft ad angles as an Ad Studio project. With render=true, also renders ad variants for every angle in the chosen formats and aspects.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Product or landing page URL |
| title | string | no | Optional project title |
| language | string | no | Ad language code, e.g. en |
| render | boolean | no | Render variants right away (uses credits) |
| formats | array | no | Ad formats to render |
| aspects | array | no | Aspect ratios to render |
| avatar_id | string | no | Avatar presenter id; required for the ugc_avatar format |
Schedule a finished reel to auto-publish to connected TikTok, Instagram or YouTube Shorts accounts at a future UTC time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | A completed reel job id |
| platforms | array | yes | — |
| scheduled_at | string | yes | Future ISO-8601 UTC time |
| youtube_privacy_status | string | no | — |
List your scheduled publishes and their status.
No parameter schema on file.
Read logged performance (views, likes, retention) for one reel with job_id, or your most recent logged reels without it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | no | Optional reel job id |
| limit | integer | no | Rows when listing; default 20 |
Get a signed price quote before generating: name a generation profile, or map pipeline stages to catalog model ids. Optionally cap the budget.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| profile | string | no | Generation profile slug |
| stages | object | no | Stage to catalog model id, e.g. {"voice": "elevenlabs/multilingual-v2"} |
| max_cost_usd | string | no | Budget cap as a decimal USD string, e.g. "2.50" |
Read your Menivor wallet: available and reserved balance in USD.
No parameter schema on file.
List Menivor's image, video and audio generation models with their integer micro-USD prices (per image, per second of video, or per audio clip).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| modality | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Menivor or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| create_reel | code-execuntrusted-input | code-exec: parameter "script"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_job | untrusted-input | untrusted-input: keyword "download" |
| ad_from_url | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| schedule_publish | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_scheduled | no tags | |
| get_performance | no tags | |
| generation_quote | no tags | |
| wallet_balance | no tags | |
| list_media_models | 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.
Supply chain and provenance
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Menivor can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.