mcpcost

ai.skryvo/mcp

Skryvo

Is the Skryvo MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-09.

Write articles, social posts, emails, ads and listings in your brand's voice and schedule them

needs auth probed 2026-11-15 · unchanged since 2026-11-09 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error": "Send a live Skryvo API key as 'Authorization: Bearer sk_skryvo_\u2026'."}
Endpoint
https://api.skryvo.ai/mcp (streamable-http)
Host
api.skryvo.ai
Getting access
OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.skryvo.ai/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.skryvo.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes skryvo.
Read from the server's public OAuth metadata, without a token. Method.
Repository
https://github.com/Skryvo/agent
Website
https://skryvo.ai/agents/
Registry
active, updated 2026-11-09 · registry entry

Compare this server with others.

More servers

Servers that mention articles or listings.

Badge for the README

mcpcost: needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

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

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.