mcp-registry/io.github.magichourhq/magic-hour · v0.1.0
Also listed as github/magichourhq/magic-hour-mcp, mcp-registry/io.github.rhythmp28/magic-hour
As of 2026-10-19 21:46 UTC, the Magichourhq Magic Hour MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Create and edit images, videos, and audio through Magic Hour's hosted Streamable HTTP MCP server.
Claude Code
claude mcp add --transport http magichourhq-magic-hour-mcp-server https://mcp.magichour.ai/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"magichourhq-magic-hour-mcp-server": {
"type": "http",
"url": "https://mcp.magichour.ai/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 tool definition(s) exceed ~1,200 tokens each (largest: text_to_video_create_video, ~1,920).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~8,349 tokens every session. How to fix →
46 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
33 parameter(s) across 16 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Loading this server's tool list costs an agent ~30,075 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 2 tool(s) removed and 87 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
21 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.magichourhq/magic-hour"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.magichourhq/magic-hour"}) over MCP.
text_to_video_create_video ~1,920 tokensimage_to_video_create_video ~1,892 tokensai_image_generator_create_image ~1,773 tokensanimation_create_video ~1,766 tokensai_image_editor_create_image ~1,672 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.magichourhq%2Fmagic-hour?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.magichourhq%2Fmagic-hour?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.magichourhq%2Fmagic-hour.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.magichourhq%2Fmagic-hour.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.magichourhq%2Fmagic-hour?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:47f90e91fe84ee0c…, first seen 2026-10-18, included at leaf 19601 of 28,974. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable media servers · most reliable files servers · most reliable ml servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 21:46 UTC, the Magichourhq Magic Hour MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Magichourhq Magic Hour MCP server advertises 47 tools, including account_retrieve, ai_clothes_changer_create_image, ai_face_editor_edit_image, ai_gif_generator_create_image, ai_headshot_generator_create_image.
Point your MCP client at this streamable-http endpoint: https://mcp.magichour.ai/
Glimind scanned all 46 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.