# Wincher MCP by usefulapi (remote · wincher.usefulapi.io)

Read Wincher keyword rankings, SERPs, competitors and history; add keywords, groups and notes.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `wincher.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-wincher/wincher.md), [page](https://verifymcp.io/servers/io-usefulapi-wincher/wincher)

## Channel facts

- Endpoint: `https://wincher.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3261 tokens (~148/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Wincher MCP by usefulapi server?

Wincher MCP by usefulapi is a hosted endpoint at https://wincher.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-wincher 'https://wincher.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-wincher": {
      "url": "https://wincher.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-wincher": {
      "type": "http",
      "url": "https://wincher.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-wincher]
url = "https://wincher.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-wincher": {
      "type": "remote",
      "url": "https://wincher.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-wincher --url 'https://wincher.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-wincher:
    url: "https://wincher.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-wincher": {
      "Transport": "http",
      "Url": "https://wincher.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-wincher -t streamable-http -u 'https://wincher.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-wincher": {
      "type": "http",
      "url": "https://wincher.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (22)

### `wincher_get_account` (~60 tokens)

Get account and plan limits

The Wincher account behind the token: id, timezone and the plan limits with current usage (websites, users, keywords, keyword lookups, map-tracking credits, history days). Check keyword usage here before adding keywords. GET /account.

### `wincher_get_user` (~40 tokens)

Get current user

The Wincher user the token belongs to: id, role, state, project access and profile (name, email, language). GET /user.

### `wincher_list_search_engines` (~41 tokens)

List search engines

The search engines Wincher can track (id, domain such as google.com, country, languages, default location). GET /search-engines.

### `wincher_search_locations` (~122 tokens)

Search tracking locations

Search the locations Wincher can track rankings for (code, name, country), most popular first, at most 100. Both are required by the API: an ISO country code and a free-text search (at least 3 characters). GET /locations.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2 country code, e.g. US (required by the Wincher API).
- `search` (string, required): Free text, at least 3 characters, e.g. 'new york' (required by the Wincher API).

### `wincher_list_projects` (~170 tokens)

List projects

List projects (folders that group websites): id, name, website_ids, user_ids, and optionally the ranking summary for a period. GET /projects.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_ranking` (boolean): Include ranking data (slower and larger). Default false.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Field to order by; prefix with '-' for descending, e.g. 'keyword' or '-created_at'.
- `start` (string): Start of the period (date or ISO date-time, UTC).

### `wincher_list_websites` (~220 tokens)

List tracked websites

List the websites tracked in Wincher: id, domain, display name, search engine, location, language, mobile flag, keyword/group/competitor counts, competitors and brand keywords. Optionally with the ranking summary for a period. GET /websites.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_ranking` (boolean): Include ranking data (slower and larger). Default false.
- `include_serp_features` (boolean): Include serp_features in the ranking data. Default true; false makes replies much smaller and faster.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Field to order by; prefix with '-' for descending, e.g. 'keyword' or '-created_at'.
- `start` (string): Start of the period (date or ISO date-time, UTC).

### `wincher_get_website` (~168 tokens)

Get website

One tracked website with its settings, competitors, brand keywords, counts and (for the period) ranking summary. GET /websites/{website_id}.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_ranking` (boolean): Include ranking data (slower and larger). Default false.
- `include_serp_features` (boolean): Include serp_features in the ranking data. Default true; false makes replies much smaller and faster.
- `segment_id` (string): Filter by a saved or temporary segment id (see wincher_list_segments).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_keywords` (~246 tokens)

List keywords

List the keywords tracked for a website with groups, volume, CPC, difficulty, competition, search intents and, with include_ranking, the latest position, traffic, ranking pages, SERP features and best position in the period. Positions are tracked down to the top 30. GET /websites/{website_id}/keywords.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_ranking` (boolean): Include ranking data (slower and larger). Default false.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Field to order by; prefix with '-' for descending, e.g. 'keyword' or '-created_at'.
- `segment_id` (string): Filter by a saved or temporary segment id (see wincher_list_segments).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_get_keyword` (~138 tokens)

Get keyword

One tracked keyword with its groups, volume, CPC, difficulty and (default) ranking for the period. GET /websites/{website_id}/keywords/{keyword_id}.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_ranking` (boolean): Include ranking data. Default true; false is faster.
- `keyword_id` (integer, required): Wincher keyword id (from wincher_list_keywords).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_get_keyword_serps` (~104 tokens)

Get keyword SERPs

The most recent search result pages Wincher stored for a keyword (up to 30): date, search volume, SERP features and the ranking results (position, URL, domain, traffic). GET /websites/{website_id}/keywords/{keyword_id}/serps.

Input parameters:

- `keyword_id` (integer, required): Wincher keyword id (from wincher_list_keywords).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_get_keyword_ranking_history` (~154 tokens)

Get keyword ranking history

Historical position (or estimated traffic) for ONE keyword as time series, optionally split per ranking page or per competitor. GET /websites/{website_id}/keyword/{keyword_id}/ranking-history.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `group_by` (string): Split into one series per ranking page or per competitor.
- `keyword_id` (integer, required): Wincher keyword id (from wincher_list_keywords).
- `metric` (string): Default position.
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_get_ranking_history_bulk` (~131 tokens)

Get ranking history for several keywords

Historical positions for up to 50 keywords at once (one time series per keyword). This is a read: it uses POST only because the keyword id list goes in the body. POST /websites/{website_id}/ranking-history.

Input parameters:

- `end` (string, required): End of the period (date or ISO date-time, UTC).
- `keyword_ids` (array, required): Keyword ids (1-50).
- `start` (string, required): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_groups` (~245 tokens)

List keyword groups

List the keyword groups of a website: id, name, keyword_ids, average difficulty, search-intent counts and optionally ranking summaries. GET /websites/{website_id}/groups.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_ranking` (boolean): Include ranking data (slower and larger). Default false.
- `include_serp_features` (boolean): Include serp_features in the ranking data. Default true; false makes replies much smaller and faster.
- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Field to order by; prefix with '-' for descending, e.g. 'keyword' or '-created_at'.
- `segment_id` (string): Filter by a saved or temporary segment id (see wincher_list_segments).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_get_group` (~185 tokens)

Get keyword group

One keyword group with its keyword ids and (optionally) ranking summary for the period. GET /websites/{website_id}/groups/{group_id}.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `group_id` (integer, required): Keyword group id (from wincher_list_groups).
- `include_ranking` (boolean): Include ranking data (slower and larger). Default false.
- `include_serp_features` (boolean): Include serp_features in the ranking data. Default true; false makes replies much smaller and faster.
- `segment_id` (string): Filter by a saved or temporary segment id (see wincher_list_segments).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_competitors` (~128 tokens)

List competitors

The competitor domains tracked for a website (id, domain, created_at). GET /websites/{website_id}/competitors.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Field to order by; prefix with '-' for descending, e.g. 'keyword' or '-created_at'.
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_competitor_ranking_summaries` (~172 tokens)

Competitor ranking summaries

Ranking summaries (average position, share of voice, traffic, position distribution, volume) for the website's competitors over a period, for comparison with your own. GET /websites/{website_id}/competitors/ranking-summaries.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `include_serp_features` (boolean): Include serp_features in the ranking data. Default true; false makes replies much smaller and faster.
- `segment_id` (string): Filter by a saved or temporary segment id (see wincher_list_segments).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_competitor_keyword_positions` (~126 tokens)

Competitor keyword positions

For each tracked keyword, the position of your site and of each competitor in the period. GET /websites/{website_id}/competitors/keyword-positions.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `segment_id` (string): Filter by a saved or temporary segment id (see wincher_list_segments).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_annotations` (~102 tokens)

List annotations

The annotations (notes on the ranking graphs: automatic, alert and user-written) for a website, optionally within a period. GET /websites/{website_id}/annotations.

Input parameters:

- `end` (string): End of the period (date or ISO date-time, UTC).
- `start` (string): Start of the period (date or ISO date-time, UTC).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_list_segments` (~59 tokens)

List segments

The saved segments (keyword filters) usable as segment_id in other tools. By default also temporary ones; only_named limits to saved ones. GET /segments.

Input parameters:

- `only_named` (boolean): Only named (saved) segments. Default false.

### `wincher_add_keywords` (~196 tokens)

Add keywords to track

WRITE: start tracking up to 50 new keywords on ONE website. EACH keyword uses one keyword slot of the plan's keyword quota (see wincher_get_account), and it is tracked and updated from then on; this tool cannot remove keywords again. Each keyword may name a preferred_url (the landing page expected to rank). Invalid or already-tracked keywords are ignored by Wincher (not created). 'groups' are keyword group NAMES to put every keyword in (may be empty; use names from wincher_list_groups, an unknown name may create a new group). POST /websites/{website_id}/keywords/bulk.

Input parameters:

- `groups` (array): Keyword group names to assign to all of these keywords (default none).
- `keywords` (array, required): 1-50 keywords to add (each uses one keyword slot).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_create_group` (~99 tokens)

Create keyword group

WRITE: create a keyword group on a website, optionally containing existing keywords (ids from wincher_list_keywords). Uses no keyword quota. POST /websites/{website_id}/groups.

Input parameters:

- `keyword_ids` (array): Existing keyword ids to put in the group (default none).
- `name` (string, required): Group name (1-200 characters).
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

### `wincher_create_annotation` (~148 tokens)

Create annotation

WRITE: add a user annotation (a note shown on the ranking graphs, e.g. 'Launched new landing page') for a date, optionally tied to specific keywords; without keyword_ids it is a global note for the website. Visible to everyone with access to the website. Uses no keyword quota. POST /websites/{website_id}/annotations.

Input parameters:

- `date` (string, required): The date the note is shown at, yyyy-mm-dd.
- `description` (string, required): The note text.
- `keyword_ids` (array): Keyword ids this note relates to; omit for a global note.
- `website_id` (integer, required): Wincher website id (from wincher_list_websites).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-wincher/wincher#diagnostics

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the Wincher MCP by usefulapi server?

Wincher MCP by usefulapi is listed in the public MCP registry as io.usefulapi/wincher. Read Wincher keyword rankings, SERPs, competitors and history; add keywords, groups and notes. This page covers its hosted endpoint (https://wincher.usefulapi.io/mcp).

### Is the Wincher MCP by usefulapi server safe to use?

Wincher MCP by usefulapi scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Wincher MCP by usefulapi server expose?

Wincher MCP by usefulapi exposes 22 tools: wincher_get_account, wincher_get_user, wincher_list_search_engines, wincher_search_locations, wincher_list_projects, and 17 more. Their descriptions and schemas cost roughly 3,054 tokens of context every time the server is loaded.

### Does the Wincher MCP by usefulapi server require authentication?

Yes. Wincher MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Wincher MCP by usefulapi server still maintained?

Wincher MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://wincher.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/wincher/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-wincher/wincher.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-wincher/wincher.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-wincher/wincher