Blender integration through the Model Context Protocol
Nothing to run from here
Corent 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
18
downloads a day
local
runs on your machine
526
downloads in 30d
What it does
MCP server for the Corent media generation API — give any AI agent the ability to generate images and videos.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'CORENT_API_KEY=${CORENT_API_KEY}' --transport stdio corent-mcp '--' npx -y corent-mcp
# 2 — ask your agent for something these tools do
# generate_image, generate_video, edit_video and 24 more
It needs CORENT_API_KEY: this reads it from your environment, so export it first.
Corent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GGAll 1 server
gg131211 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 Corent 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. Claude Code reads CORENT_API_KEY (Your Corent API key (co_live_...). Create one at https://corent.tech/dashboard/api-keys) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx CORENT_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'CORENT_API_KEY=${CORENT_API_KEY}' --transport stdio corent-mcp '--' npx -y corent-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 asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: CORENT_API_KEY — Your Corent API key (co_live_...). Create one at https://corent.tech/dashboard/api-keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
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
27 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.
Generate an image from a text prompt. Returns a permanent public URL. Synchronous, usually 2-20 seconds. Costs a few cents (premium ~7c); failed generations are never billed. Takes reference_image_urls to keep a face, character or product consistent (tier pro or up).
No parameter schema on file.
Start a video from text, a source image, or references (@Image 1, @Video 1, @Audio 1 in the prompt). Asynchronous: returns a job id; poll get_job until completed. Premium ~52c, pro ~84c per clip; failed generations are never billed. References need corent-seedance-2.5; photos of real people are…
No parameter schema on file.
Edit an existing clip with a prompt: add, remove, replace or change something in @Video 1. Keeps the source clip's length and shape. Asynchronous: returns a job id; poll get_job until completed. Runs on corent-seedance-2.5. Photos of real people are rejected as references; Corent-made characters…
No parameter schema on file.
Continue an existing clip (@Video 1) forward or backward, with a prompt for what happens next or before. Keeps the source shape; duration_s is the added length. Asynchronous: returns a job id; poll get_job until completed. Runs on corent-seedance-2.5. Pair with return_last_frame to chain shots.
No parameter schema on file.
Text to speech. Synchronous: returns the finished audio URL and the exact charge. Billed in started blocks of 1,000 characters (roughly 25-30c for the first block), so a short line costs the same as a paragraph. Call list_voices first to pick a voice_id. Failed generations are never billed.
No parameter schema on file.
Run a prompt or conversation through a frontier language model on the user's Corent account. Synchronous: returns the text, token usage and exact charge (fractions of a cent). Use it when the user wants a specific model's answer or work billed to Corent, not for your own reasoning. Supports tool…
No parameter schema on file.
The direct-access menu: every model that can be pinned by name (spelled corent-*) on the generate tools, with kind, quality score and live status. Carries no price; billing is flat cost-plus and each generation returns its exact charge. Read-only and free. Only needed when the user names a…
No parameter schema on file.
The voices generate_speech accepts as voice_id, with display name, preview clip and descriptors (gender, age, accent, use case). Read-only and free. Call it before generate_speech whenever the user wants a particular narrator; a voice_id cannot be guessed.
No parameter schema on file.
Stop a job that has not finished and release the money held for it. Charges nothing. Use it as soon as the user says they did not mean to start something, especially a video. A job that already finished stays completed and billed for what was delivered.
No parameter schema on file.
The live tier menu for image and video: each tier's price estimate, shapes, video durations, per-resolution pricing, and whether it accepts reference images (image) or a source image (video). Read-only and free. Check it before quoting a price. Tier-level only; never names a model.
No parameter schema on file.
Submit up to 50 image generations in one call. Asynchronous: returns a batch_id and a job id per item; poll get_batch, then get_job per image. Every item bills at the normal rate, so check get_balance first. Items are tier-routed; pin a model with generate_image instead. No reference images here.
No parameter schema on file.
Submit up to 50 video generations in one call. Asynchronous: returns a batch_id and a job id per item; poll get_batch, then get_job per clip. Video is the expensive lane: a 10-item batch can cost several dollars, so confirm with the user and check get_balance first. Items are tier-routed.
No parameter schema on file.
Progress of a batch from generate_image_batch or generate_video_batch: completed, failed and pending counts plus each item's job id. Read-only and free. Fetch a finished item's media with get_job.
No parameter schema on file.
Check a generation job (mainly video). When completed, the response carries the permanent media URL and the cost. Read-only and free.
No parameter schema on file.
The account balance in cents. balance_cents is the total, held_cents is reserved by running generations, available_cents is what a new request can actually spend; check that one before an expensive video. Read-only and free.
No parameter schema on file.
Live operational status of Corent's generation tiers (operational or degraded). Read-only and free; useful to pick a healthy tier.
No parameter schema on file.
Preview how Corent would handle a plain-language request, without generating: image vs video, tier, shape, duration and an estimated cost. Image and video only; speech is generate_speech. A story with several characters or anything over about 30 seconds is a film: use plan_film. Impossible asks…
No parameter schema on file.
Describe one image or one clip in plain language; Corent picks type, tier, shape and duration and generates it. max_cost_cents is a required ceiling: above it nothing is generated. Videos return a job id for get_job. Failed generations are never billed. A story with several characters or anything…
No parameter schema on file.
Turn a one-sentence film idea into a plan without spending anything: title, characters, every scene with its dialogue, total length and the price range. The plan lasts 24 hours. Show the user the plan and the price and get a clear yes before make_film. Use it for any story with several characters…
No parameter schema on file.
Start the film the user approved: pass plan_id from plan_film (or a brief), and max_cost_cents a little above the estimate. The charge never goes above max_cost_cents, and a failed or cancelled film is not billed. Returns film_id right away; a film takes about 15 to 30 minutes, so check get_film…
No parameter schema on file.
Progress of a film from make_film: the stage (queued, writing, casting, shooting, checking, editing, completed, failed, cancelled), progress_percent, and each scene. When completed it carries video_url, the finished film with sound, and cost_cents. Read-only and free. Tell the user the stage in…
No parameter schema on file.
Stop a film that has not finished. A cancelled film is not billed. Use it as soon as the user says they did not mean to start it or want to change the story. A film that already finished stays completed.
No parameter schema on file.
Make an existing image bigger and sharper from its public https URL. Synchronous, returns a new permanent URL. Flat price, no tier; failed runs are never billed. Optional prompt guides the added detail; omit it to enlarge faithfully. Upload a local file with upload_image first.
No parameter schema on file.
Cut the subject out of an image and return a PNG with a real transparent background, for logos, product shots and compositing. Synchronous, flat price, no tier; failed runs are never billed. Takes a public https URL; upload a local file with upload_image first.
No parameter schema on file.
Regenerate ONLY the white region of a mask and leave every pixel outside it byte-for-byte unchanged, so a product or logo stays exactly your file. Takes image_url, a same-size black-and-white mask_url (white = redo, black = keep) and a prompt for the masked area. Synchronous; failed runs are never…
No parameter schema on file.
Find media the account already made, so a result can be reused instead of paid for again. Reads the last 100 jobs, filtered by type and a prompt keyword (e.g. 'beach'), newest first. Returns id, type, status, date, tier, cost and URL per job. Read-only and free.
No parameter schema on file.
Upload a local image (base64) to Corent and get back a public https URL. Use that URL as image_url, mask_url, source_image_url or a reference in the other tools. Max 25 MB. Free; the file is stored on the account.
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 Corent 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.10.0 · scanned 14 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
Findings0 threat · 15 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest79691292d372e2f8cf41ddb701e97e7bcca17b45d90f1cf4d22bcd57e36f5ea7
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 (27 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 |
|---|---|---|
| generate_image | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| generate_video | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| edit_video | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| extend_video | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| generate_speech | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| generate_text | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_models | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_voices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| cancel_job | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| list_tiers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| generate_image_batch | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| generate_video_batch | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_batch | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| get_job | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_balance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| plan_film | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| make_film | external-sinksensitive-source | external-sink: parameter "webhook", declares readOnlyHint: false, openWorldHint: true; sensitive-source: parameter "secret" |
| get_film | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| cancel_film | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| upscale_image | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| remove_background | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| inpaint_image | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_media | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| upload_image | 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.
get_balance → make_film → cancel_film
A cross-tool exfiltration chain exists: get_balance → make_film → cancel_film.
flow-2
Tool "make_film" both reads sensitive data and can send it externally.
Supply chain and provenance
Integrityfirst-seen
Surface digest79691292d372e2f8
Scanned2026-10-14
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.10.0. Pin a release below and the command asks for exactly that one.
0.10.0
13 Sep 2026
latestNo release note was published with this version.
0.7.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Corent 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.