com.keytomic/mcp
Keytomic
Is the Keytomic MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Keytomic AI SEO agent: SEO audits, Search Console, GA4, keyword research, articles and publishing
needs auth probed 2026-11-14 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"missing authorization header"},"id":null}- Endpoint
- https://app.keytomic.com/mcp (streamable-http)
- Host
- app.keytomic.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.keytomic.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.keytomic.com, PKCE S256, grants authorization_code, client_credentials, refresh_token.
Scopes gsc:read audit:read audit:run workspace:read workspace:write content:read content:write content:publish analytics:read indexing:write visibility:read visibility:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/epicx-labs/keytomic-mcp
- Website
- https://keytomic.com/mcp
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention publishing or articles.
- AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
- AutEng Docs — Agent Document Workspace & Publishing ai.auteng/docs · alive
- SEO Content Factory ai.b77/seo-content-factory · needs auth
- AutEng MCP - Markdown Publishing & Document Share Links ai.auteng/mcp · alive
- BetterPost ai.betterpost/server · alive
- LatticeNet ai.latticenet/latticenet · needs auth
- MotiBlog ai.motiblog/mcp · needs auth
- OpenArx ai.openarx/openarx · 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.