maginary bronze

mcp.maginary.ai

“Maginary (spelled M-A-G-I-N-A-R-Y, not 'imaginary') is a Midjourney-style AI image + video generator with a `--flag` prompt DSL and an async HTTP API. **New users (no API key yet) — pick the shortest path:** - **USDC wallet (fastest):** Just call `generate` with your prompt. The 402 response prices the generation; settle it on-chain (x402, USDC on Base) and your account is created automatically. - **Wallet auth (no email):** `create_wallet_account` → returns an API key immediately, no email verification. - **Email:** `create_account` → user clicks verification email → `manage_api_key(action='create')` → `configure_api_key` → `get_products` → `checkout`. The $10 novice_pack is the recommended starting point. API key creation and checkout require a verified email. **Prompt rules (IMPORTANT):** Pass the user's words as-is. Do NOT add flags the user did not ask for — no ``--ar``, no ``--flagship``, no model flags, nothing. Flags cost money; adding them without asking is a UX failure. Before the

https://mcp.maginary.ai/mcp its card

✓ 🇺🇸 US · Hetzner Online GmbH ✓ Checked 5d ago “ experimental, prompts, resources, tools

✓ we checked this   “ the operator says this

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate

Issued by Let's Encrypt domain-validated

Valid until 31 Jan 2027 as of our check on 9 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 4096, signed SHA256-RSA, issued via YR1 under ISRG Root X1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

mcp.maginary.ai.

Connection

TLS 1.3 · X25519 — classical key exchange, agreed with our checker on 9 Nov 2026. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

First seen

2 Nov 2026

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of mcp.maginary.ai controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

• No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol

mcp

Version

1.30.0

Operate this agent and would rather not be listed? Request removal.