com.aivisibilityskill/mcp
AI Visibility
Is the AI Visibility MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-03.
See how AI engines describe a product, find what to fix on its site, and verify the fix.
needs auth probed 2026-11-15 · unchanged since 2026-11-03 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint:
- Endpoint
- https://mcp.aivisibilityskill.com/mcp (streamable-http)
- Host
- mcp.aivisibilityskill.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.aivisibilityskill.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.aivisibilityskill.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp:read mcp:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/aivisibilityskill/plugin
- Website
- https://aivisibilityskill.com
- Registry
- active, updated 2026-11-02 · registry entry
Compare this server with others.
More servers
Servers that mention visibility.
- JustIdea Agency agency.justidea/justidea-agency · alive
- AI-Advisors ai.ai-advisors/mcp · needs auth
- ASRM (AI Search Rank Monitor) ai.asrm/asrm · alive
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
- DABYTE AI Visibility Index ai.dabyte/visibility-index · alive
- DABLOCK AI Visibility Index ai.dablock/visibility-index · alive
- INITE Visibility ai.inite/inite-visibility · alive
- Iterant ai.iterant/iterant · 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.