Magic Hour MCP vs PixVerse API

Magic Hour MCP 82

All 50 tools read from tools/list with JSON Schema inputs and 29 enums, built from Magic Hour's OpenAPI specification (25). llms.txt (10). Long descriptions with a get_workflow_guide tool for choosing between them (17 of 20). Typed inputs with enums and no free-form objects (15). Worked examples; error responses not documented (5 of 15). Dated changelog with entries on 3 to 5 November 2026 (10 of 15, product changelog rather than MCP versions). 25 + 10 + 17 + 15 + 5 + 10 = 82.

PixVerse API 58

No OpenAPI file published (0). llms.txt on the platform docs (10). Each endpoint page says what the operation does, and the model tables say which models support it. Older model tables still sit beside current ones (12). Typed parameters with fixed values for model, quality, duration and aspect ratio (11). Examples on each endpoint. Results use numeric status codes (1 done, 5 generating, 7 moderation failure, 8 failed) that an agent has to look up (10). A dated changelog that adds models and endpoints every few weeks (15).

Magic Hour MCP 75

Changelog entries on 3, 4 and 5 November 2026 (30). More than three dated entries in 90 days (20). Changelog and support; issues on the public MCP repository not read (10 of 25). Registry entry io.github.magichourhq/magic-hour (0.1.1, 4 November) (15). No package health read (0). 30 + 20 + 10 + 15 + 0 = 75. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

PixVerse API 52

Model reading. The changelog's latest entry is the One-click VibeMV API on 24 September 2026, with five dated entries since July, after C1 on 7 April (30). Legacy models from V3.5 to V5.6 stay callable, and no removals were found (10). Dated changelog and support through the platform (12). No official SDK. The stdio MCP package hasn't been released since October 2025 (0). Nothing current to assess for package health (0).

Magic Hour MCP 45

API keys as Bearer tokens or OAuth through the Claude and ChatGPT connectors (20 of 30). Destructive deletes are annotated; no read-only key (8 of 20). Tools return generated media, not third-party text (10). No audit log found (0). No security.txt or certifications found; face and voice tools come with policy limits in the terms (7 of 20). 20 + 8 + 10 + 0 + 7 = 45.

PixVerse API 28

Model reading of the checklist (credential, training, retention, operator visibility, programme). One API key in an API-KEY header (20). The platform terms don't say whether inputs or outputs train models (0). No retention period or deletion call found (0). A usage deduction query API since 18 August 2026 shows what each job cost, no audit log (8). No security.txt, bug bounty or certification found (0).

Magic Hour MCP 55

50 tools totalling about 160 KB of definitions (5). list_saved_items and project getters; limited size controls (10 of 20). Error handling not documented (5 of 20). Every tool annotated, 14 read-only and the three deletes marked destructive (20). Few required inputs and SDKs (Python, Node and others listed in the docs) (15). 5 + 10 + 5 + 20 + 15 = 55.

PixVerse API 70

Small JSON responses with a video id, plus webhooks so an agent needn't poll (25). Duration, quality and aspect ratio set output size. No task list endpoint found (10). Numeric status and error codes are documented but cryptic (12). Every submit needs a fresh UUID in Ai-trace-id, and reusing one returns the earlier job instead of creating a new one. That works as an idempotency key, though an agent that reuses an id by mistake gets the old video back (20). Required trace header, no official SDK. A CLI and an MCP server exist (3).

Magic Hour MCP 58

Closed service under terms naming Magic Hour AI, Inc., revised 3 October 2026 (15). The privacy policy says prompts, uploads and outputs aren't sold or used to train models, for free and paid accounts, and MCP requests are handled the same way; retention periods aren't given (20 of 30). No deprecation policy found (5 of 20). Subprocessors not read (10 of 20, model providers named in tool docs). 15 + 20 + 5 + 10 = 50.

PixVerse API 46

Closed models under platform terms (updated 4 September 2026) with MOTIVAI PRIVATE LIMITED, with AIVORA PTE. LTD. named as an affiliate. The terms give API users the rights in generated video and allow commercial use (15). The terms don't address training on inputs or outputs and give no retention period, only that data may be deleted when service ends. We didn't read the privacy policy against them (5). No deprecation policy, but legacy models are labelled (5). No subprocessor list or data locations found (0).

Magic Hour MCP 15

No machine payment protocol (0). Plan and credit-pack prices public, per-tool credit costs not read (10). 400 sign-up credits with no card, but API access sits on paid plans (5 of 20). A person signs up for a key in a browser (0). Tool discovery is open, but calls need a key (0). 0 + 10 + 5 + 0 = 15.

PixVerse API 10

No x402, MPP or L402 (0). Credits per second are public for every model, and the docs peg $1 at five 5 second V6 720p clips, but plan prices sit on a billing page that needs JavaScript, so the dollar price of a credit isn't stated outright (10). A Free API plan with 3 concurrent jobs is listed, but the docs don't say whether it includes credits (0). A person signs up on the platform (0).