Home / MCP registry index / ai.clearvoyance/clearvoyance
Clearvoyance
ai.clearvoyance/clearvoyance in the official MCP registry.
Endpoint https://clearvoyance.ai/mcp.
The registry describes it as: Anonymous feedback from real people by voice or text, with an AI report. Flat price per campaign.
We read its 27 tools on 2026-10-21. 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
get_pricing create_account get_account get_ledger create_card_topup check_topup quote_campaign launch_campaign list_my_campaigns get_campaign get_campaign_results analyze_campaign close_campaign close_account get_agent_config get_session_nonce initialize_session verify_payment validate_campaign create_campaign verify_campaign_funding verify_campaign_activation get_login_nonce verify_login_signature list_campaigns get_campaign_details export_campaign_data
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-clearvoyance-clearvoyance)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.