io.github.pahaa97/seonix
Seonix
Is the Seonix MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-08.
Automated SEO: Site Health, fix plan, Search Console, keywords and draft scoring for AI agents.
needs auth probed 2026-11-14 · unchanged since 2026-11-08 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: no bearer token
- Endpoint
- https://api.seonix.ai/mcp (streamable-http)
- Host
- api.seonix.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.seonix.ai/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 api.seonix.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes read write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/seonix-ai/mcp
- Website
- https://seonix.ai/mcp
- Registry
- active, updated 2026-11-08 · registry entry
- Changes
- 4 recorded, reachable in 4 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention automated or keywords.
- ai.adramp/google-ads · needs auth
- SellerForge for Amazon Sellers ai.sellerforge/sellerforge · needs auth
- SEOmatic ai.seomatic/seomatic · needs auth
- TrustGrowth ai.trustgrowth/trustgrowth · needs auth
- Gridar app.gridar/gridar · needs auth
- ai.smithery/saidsef-mcp-github-pr-issue-analyser · not found
- Parahuman co.parahuman/parahuman · needs auth
- com.affogata.app/affogata · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-02 11:42 | needs auth | ||||
| 2026-10-30 10:34 | alive | 1.8 s | 41 | 8.5k | 4.9k |
| 2026-10-25 21:21 | alive | 1.1 s | 41 | 8.5k | 4.9k |
| 2026-10-20 09:51 | 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.