Home / MCP registry index / io.usefulapi/wincher
Wincher MCP by usefulapi
io.usefulapi/wincher in the official MCP registry.
Endpoint https://wincher.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Wincher keyword rankings, SERPs, competitors and history; add keywords, groups and notes.
We read its 22 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
wincher_get_account wincher_get_user wincher_list_search_engines wincher_search_locations wincher_list_projects wincher_list_websites wincher_get_website wincher_list_keywords wincher_get_keyword wincher_get_keyword_serps wincher_get_keyword_ranking_history wincher_get_ranking_history_bulk wincher_list_groups wincher_get_group wincher_list_competitors wincher_list_competitor_ranking_summaries wincher_list_competitor_keyword_positions wincher_list_annotations wincher_list_segments wincher_add_keywords wincher_create_group wincher_create_annotation
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-wincher)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.