Home / MCP registry index / com.everlange/mcp
com.everlange/mcp
com.everlange/mcp in the official MCP registry.
Endpoint https://everlange.com/api/mcp.
The registry describes it as: Everlange: audit AEO on 67 criteria across 10 answer engines, apply fixes, prove the gain.
We read its 36 tools on 2026-10-27. 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
aeo_list_sites aeo_audit aeo_audit_status aeo_batch_audit aeo_report aeo_improvements aeo_generate aeo_apply aeo_citations aeo_proof aeo_monitor ads_list_accounts ads_performance ads_search_terms ads_change_history ads_quality_breakdown ads_landing_pages ads_geo_performance ads_asset_performance ads_campaign_criteria ads_geo_target_search ads_audiences ads_device_performance ads_set_bid_modifier ads_add_location ads_remove_criterion ads_attach_audience ads_keywords ads_audit ads_add_negative_keywords ads_pause_keyword ads_update_budget ads_campaign_status ads_list_ads ads_ad_status ads_add_keywords
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-everlange-mcp)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.