me.brainrotify/brainrotify
Brainrotify
Is the Brainrotify MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Make faceless short videos and AI songs, and autopost series to TikTok, Instagram and YouTube.
needs auth probed 2026-11-14 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":0,"error":{"code":-32600,"message":"Sign in with OAuth, or send an API key from brainrot- Endpoint
- https://www.brainrotify.me/api/mcp (streamable-http)
- Host
- www.brainrotify.me
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.brainrotify.me/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 www.brainrotify.me, PKCE S256, grants authorization_code, refresh_token.
Scopes brainrotify.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.brainrotify.me/api-docs
- Registry
- active, updated 2026-10-20 · registry entry
Compare this server with others.
More servers
Servers that mention instagram or autopost.
- Adrio ai.adrio/adrio · needs auth
- Autoposting ai.autoposting/autoposting · not MCP
- Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram ai.bowmark/bowmark · alive
- Creator SKILL v2 — Influencer Discovery ai.deinai/creator-skill-v2 · needs auth
- Creator SKILL — Influencer Discovery ai.deinai/creator-skill · needs auth
- Kadenza ai.kadenza/mcp · needs auth
- Marky ai.mymarky/marky · needs auth
- Marketing Intelligence & Optimization ai.saifs/marketing-intelligence · 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.