io.github.iart-ai/iart
iArt
Is the iArt MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Make motion graphics videos from a prompt: kinetic type, explainers, logo reveals, AI voice-over.
needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Sign in to use iArt"}}- Endpoint
- https://app.iart.ai/api/mcp (streamable-http)
- Host
- app.iart.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.iart.ai/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server tijsrzmqmbbhigcjyomq.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.iart.ai/docs/mcp
- Registry
- active, updated 2026-11-14 · registry entry
Compare this server with others.
More servers
Servers that mention iart.
- Familiar Tarot com.familiartarot/tarot · needs auth
- acdoyle io.github.granetb-acdoyle/acdoyle · paid (402)
- EK Bridge io.github.bereciartua/ek-bridge · not probed
- Luria com.luriart/luria · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.