Home / MCP registry index / ai.kliqo/ai-visibility
Kliqo AI
ai.kliqo/ai-visibility in the official MCP registry.
Endpoint https://kliqo.ai/mcp.
The registry describes it as: Free AI visibility checks, then see if ChatGPT and Google AI name you or your competitors instead.
We read its 24 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
check_ai_crawlers audit_page_for_ai generate_ai_fix_files check_chatgpt_answer verify_crawler_ip list_ai_crawlers generate_ai_robots_rules get_briefing get_fix_plan verify_fix update_action add_prompts track_competitor list_projects get_ai_visibility get_answers get_answer get_competitor_gaps get_top_sources get_prompt_performance get_actions get_impact get_crawler_activity search_workspace
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-kliqo-ai-visibility)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.