Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ludo AI Game Assets

REMOTE · MCP.LUDO.AI

Generate game assets with AI: sprites, animations, 3D models with rigging, video, music, SFX, voices

Available components

−1 this week 75 Trust /100

Last scanned (14 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Recent critical change

Authorization (16 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 19026 tokens (~328/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 59 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “payTopup”, which the server declares destructive security
    • Tool “createTileset” rewrote its description, which is the text the model reads security
    • Tool “editTileset” rewrote its description, which is the text the model reads security
    • Tool “getAccount” rewrote its description, which is the text the model reads security
    • Tool “getPricing” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 94% ▼ functional
    • New tool “createTopupLink” functional
    • New tool “getTopupLink” functional
    • New tool “getTopupQuote” functional
  • 20 Nov 26 0
    • Tool “upscaleImage” rewrote its description, which is the text the model reads security
  • 18 Nov 26 0
    • Tool “create3DModel” rewrote its description, which is the text the model reads security
    • New tool “createTile” functional
    • New tool “createTileset” functional
    • New tool “editTileset” functional
  • 17 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “animateSprite” rewrote its description, which is the text the model reads security
    • Tool “animateSpriteKeyframes” rewrote its description, which is the text the model reads security
    • Tool “createSpriteAudio” rewrote its description, which is the text the model reads security
    • Tool “createVideo” rewrote its description, which is the text the model reads security
    • Tool “editSpritesheet” rewrote its description, which is the text the model reads security
    • Tool “transferMotion” rewrote its description, which is the text the model reads security
    • “animateSpriteKeyframes” reworded the description of “requestBody” cosmetic
  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “animate3DModelPreset” rewrote its description, which is the text the model reads security
    • Tool “listAnimationPresets” rewrote its description, which is the text the model reads security
    • Tool “transferMotion” rewrote its description, which is the text the model reads security
    • New tool “createAnimation” functional
    • New tool “listMyAnimations” functional
    • “animate3DModelPreset” reworded the description of “requestBody” cosmetic
    • “transferMotion” reworded the description of “requestBody” cosmetic
    • Tool “animate3DModelPreset” changed its title: Animate 3D model with a preset → Animate 3D model with a preset or your animation cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
    • Tool “getPricing” rewrote its description, which is the text the model reads security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.ludo.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ludo.ai CN=WR3,O=Google Trust Services,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 1b6223e6b7774024107dbb0bf579285a
SANs: mcp.ludo.ai
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ludo.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
ludo.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ludo.ai/mcp Verified 200
http (plaintext) http://mcp.ludo.ai/mcp HTTPS enforced
MCP tools · 58 exposed · ~17,871 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
rotateSprite ~301

Re-render an existing sprite from a different camera viewpoint while keeping the same character and pose, taking a source image (URL or base64), a required camera_rotation azimuth (one of 0, 45, 90, 135, 180, -135, -90, -45 degrees), an optional camera_elevation (0, 30, or 60 degrees; omit to keep the current elevation), and an optional n (1-4) for the number of variations. Only works with sprite image types (not icons, screenshots, etc.). The job result is an array of rotate-sprite results, each with the generated image url and the camera_rotation and camera_elevation that were applied. Credits are held when the job is accepted and refunded if it fails or is cancelled; the charge scales with the number of images generated. Use this to produce alternate view angles of a character; use generatePose instead to change the character's pose rather than the camera, and animateSprite or transferMotion to bring a sprite to life. Pass an optional request_id to tag the results so you can retrieve them later via listGenerations (type spritesheet). Async generation job: returns `{id, status}` - poll `getApiJob` (job and credit contract: see the server instructions). Credits: This endpoint consumes 0.5 credits per result.

NameTypeReqDescription
requestBodyobjectyesPayload for rotating the camera view of an existing sprite

No output schema declared.

No examples provided.

rotateSpritesheet ~486

Re-render a previously generated sprite animation from a new view: the same motion and timing, seen from a different angle (e.g. a front-facing walk cycle turned into the same walk seen from the back). Pass the `spritesheet_url` you received from `animateSprite`, `animateSpriteKeyframes`, `transferMotion`, `editSpritesheet` or an earlier call - it must be a spritesheet you generated within the last 7 days; arbitrary external images are not accepted - and, as `image` (URL or base64), the character exactly as it must appear in the new view: it becomes the first frame of the animation. To produce that image, call rotateSprite on the animation's first frame (or any image of the character) and pick the view you want. An optional `final_image` fixes the last frame (it defaults to the first frame, for cyclic or returning animations), and an optional `prompt` steers the result: the character's facing in the new view ("its back to the camera"), where the action goes ("the kick goes to the left of the frame"), or anything else about the motion. Runs on hydra (default) or hydra-plus (finer detail). The job result is the same sprite result as animateSprite (`spritesheet_url`, `video_url`, grid fields, optional GIF and frame URLs). The animation covers the source's own length (up to 5 seconds; a longer source is sped up to fit), so omit `duration` unless you need to change that. Credits are held for that length when the job is accepted, or for 3 seconds when it is shorter (a new view is a new generation, and hydra generates at least 3 seconds); the final charge is the model's rate × seconds of video generated, never more than was held, and the difference (or everything, if the job fails or is cancelled) is refunded. Pass an optional request_id to tag the result for later retrieval via listGenerations (type spritesheet). Async generation job: returns `{id, status}` - poll `getApiJob` (job and credit contract: see the server instructions). Credits: Cost varies by model and durat…

NameTypeReqDescription
requestBodyobjectyesPayload for re-rendering a previously generated sprite animation from a new view.

No output schema declared.

No examples provided.

searchDocs ~311

Search Ludo's own documentation with a plain-language question and get back only the few sections that answer it - the fastest way to learn how a feature is meant to be used before you generate with it (how to pick a sprite animation mode or model, how margins behave, what something costs, known limitations). Start here rather than reading whole documents. Each result carries `doc` and `section`, which you can pass straight to getDocs to re-read that section, and the section's full markdown `content`. Results are best first; weak matches are left out, so an empty `results` list means the documentation does not cover the question - rephrase it, or call getDocs with no parameters to browse the table of contents. This is the same documentation the Ludo web app shows its users, so it occasionally describes buttons rather than parameters; the substance applies to the API and MCP surfaces just the same. Returns up to `n` sections (default 3, max 10). If it answers 503 the search backend is briefly unavailable: call getDocs instead rather than retrying in a loop. This is a free discovery endpoint: it does not charge credits and does not queue a job.

NameTypeReqDescription
ninteger–Maximum number of sections to return. Defaults to 3.
querystringyesWhat you want to know, in plain language, e.g. "how do I keep a sprite animation's colors consistent" or "what does a 3D model cost".

No output schema declared.

No examples provided.

submitApiFeedback ~298

Report a problem with the Ludo API itself to the Ludo team. Use it ONLY for API bugs (an error, a failed or stuck job, a crash, a response that does not match this documentation) and API limitations (a parameter, operation or format you needed that the API does not support, and that you could not work around). NEVER use it to report model limitations or the quality of a result: an image, sprite, animation, 3D model, video or sound that looks wrong, ignores part of the prompt, has artifacts or is not what you wanted is not an API bug. Do not report those; retry with a different prompt, model or settings instead. Before reporting a limitation, call searchDocs with what you tried: if the docs already describe it as a known limitation, do not report it. Describe what you were trying to do and what went wrong, and name the operation it relates to. Always send the id of every job the report is about, in job_ids (up to 10): we look at those jobs' inputs and outputs, and a report about a result we cannot find cannot be investigated. Do not include personal data, secrets or file contents. Send one report per issue, and if you are an agent, tell the user what you sent. Free (no credits).

NameTypeReqDescription
requestBodyobjectyesPayload for reporting a bug, limitation or missing capability to Ludo

No output schema declared.

No examples provided.

transferMotion ~634

Transfer motion from a reference video, a named animation preset or one of the account's generated animations (an `animation_id` from createAnimation or listMyAnimations) onto a static sprite image, producing an animated spritesheet that mimics the reference movement. Provide the sprite as image (URL or base64) plus either a video (URL or base64) or a preset_id together with perspective and direction (all three from listAnimationPresets; if a video is sent with a preset_id or animation_id, the preset or animation is used and the video is ignored). The job result is the same sprite result as animateSprite: `spritesheet_url`, `video_url`, grid fields, optional GIF / frame / with-background URLs, and `audio_url` when the model is hydra. `duration` defaults to 1.5s where the chosen model offers it, otherwise to that model's shortest (hydra, the default, starts at 3s) - and a longer reference clip or preset is compressed to fit, so pass the preset's own `duration` (returned by listAnimationPresets) to keep its timing. It returns HTTP 400 if neither a video nor a complete preset_id/perspective/direction triple is supplied, if the named preset, perspective, or direction cannot be resolved, or if the model/duration combination is invalid. Credits are held for the duration you requested when the job is accepted; the final charge is rate × seconds of video generated (which follows the reference clip or preset; legacy models keep their minimum charge), never more than for the duration you requested, and the difference (or everything, if the job fails or is cancelled) is refunded. The returned sheet is then trimmed to its best loop and can run slightly shorter than the video; that trim is not deducted. Use this when you have an existing motion clip or preset to copy; prefer animateSprite to generate animation purely from a text prompt. Omit `model` to run on hydra (the default - most capable, and returns audio); pick ignis for a cheaper run on simple motion with a preset (it d…

NameTypeReqDescription
requestBodyobjectyesPayload for transferring motion from a video, an animation preset or a generated animation onto a static sprite image, producing an animated spritesheet.

No output schema declared.

No examples provided.

upscaleImage ~306

Upscale an image: the same picture at a higher resolution, up to 4x, with the result capped at about 3.1 megapixels (width x height) whatever its shape: a square image comes back 1776x1776 at most, and a wide or tall one can be longer than 2048px on its longest side. The source image (URL or base64) must be under 3 megapixels, for example 1700x1700 or 2000x1500; a larger one is rejected with HTTP 400. A result that reached the cap is itself over 3 megapixels, so it cannot be upscaled again. The job result is a single image result with a url (not an array). The image is uploaded and validated, and an image larger than 15MB is rejected with HTTP 400. Credits are held when the job is accepted and refunded if it fails or is cancelled. Use upscaleImage to raise the resolution of an image you already have; createImage and editImage make new or changed images instead. Pass an optional request_id to tag the result so you can retrieve it later via listGenerations (type image). Async generation job: returns `{id, status}` - poll `getApiJob` (job and credit contract: see the server instructions). Credits: This endpoint consumes 0.5 credits per result.

NameTypeReqDescription
requestBodyobjectyesPayload for upscaling an image

No output schema declared.

No examples provided.

upscaleVideo ~298

Upscale a previously generated video to twice its resolution (2x). Pass the video `url` you received from `createVideo`, `createVideoFromReferences`, or `editVideo` - it must be a video you generated within the last 7 days; arbitrary external videos are not accepted. Both dimensions of the source must be under 960 pixels: griffin-hd (768p) output qualifies only when square (768x768), not landscape (1344x768) or portrait (768x1344); output from the retired griffin (480p) does. A too-large source fails the job and the held credits are refunded. The job result is the new video URL (2x width and height, same duration) and its duration in seconds. Billed per second of video, independent of model; held when the job is accepted and refunded if it fails or is cancelled. Pass an optional `request_id` to tag the result so you can locate it later via listGenerations (type video). Related tools: `createVideo` for image-to-video, `editVideo` to modify a generated video. Async generation job: returns `{id, status}` - poll `getApiJob` (job and credit contract: see the server instructions). Credits: 0.2 credits per second of video.

NameTypeReqDescription
requestBodyobjectyesPayload for upscaling a previously generated video to twice its resolution.

No output schema declared.

No examples provided.

validateApiKeyEndpoint ~27

Validates an API key. Returns 200 if valid, 403 if invalid.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Ludo AI Game Assets MCP server?

Ludo AI Game Assets is a hosted endpoint at https://mcp.ludo.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.ludo.ai

# add to Claude Code
claude mcp add --transport http ai-ludo-game-assets 'https://mcp.ludo.ai/mcp'
Common questions

What is the Ludo AI Game Assets MCP server?

Ludo AI Game Assets is an MCP server listed in the public MCP registry as ai.ludo/game-assets. Generate game assets with AI: sprites, animations, 3D models with rigging, video, music, SFX, voices. This page covers its hosted endpoint (https://mcp.ludo.ai/mcp).

Is the Ludo AI Game Assets MCP server safe to use?

Ludo AI Game Assets scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Ludo AI Game Assets MCP server expose?

Ludo AI Game Assets exposes 58 tools: validateApiKeyEndpoint, createImage, generateWithStyle, editImage, animateSprite, and 53 more. Their descriptions and schemas cost roughly 17,871 tokens of context every time the server is loaded.

Does the Ludo AI Game Assets MCP server require authentication?

No. We connected to Ludo AI Game Assets without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ludo AI Game Assets MCP server still maintained?

Ludo AI Game Assets is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ludo AI Game Assets MCP server?

VerifyMCP ran 13 checks on Ludo AI Game Assets, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.