ai.clevera/mcp
Clevera
Is the Clevera MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Make how-to videos, social clips and help articles from Claude or ChatGPT, and run your help center.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthenticated","message":"Send a Clevera agent token (Authorization: Bearer clv_agent_\u20- Endpoint
- https://app.clevera.ai/mcp (streamable-http)
- Host
- app.clevera.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.clevera.ai/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.clevera.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes content:read articles:write structure:write site-pages:write changelog:write media:write site:publish help:read insights:read site:configure sites:create library:read videos:create videos:export videos:publish research:run research:read credits:spend jobs:read materials:write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.clevera.ai/mcp
- Registry
- active, updated 2026-10-21 · registry entry
Compare this server with others.
More servers
Servers that mention clevera or articles or chatgpt.
- com.cleveralpha.www/calculators · alive
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- adplane ai.adplane/google-ads · needs auth
- AIMentionTracker ai.aimentiontracker/mcp · needs auth
- Amazon Seller MCP Server — AgentXray ai.agentxray/mcp · needs auth
- Askline ai.askline/askline · not found
- SEO Content Factory ai.b77/seo-content-factory · needs auth
- ai.butlerbrain/mcp · 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.