Wincher MCP by usefulapi
REMOTE · WINCHER.USEFULAPI.IO
Read Wincher keyword rankings, SERPs, competitors and history; add keywords, groups and notes.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://wincher.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wincher.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://wincher.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://wincher.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://wincher.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://wincher.usefulapi.io/mcp |
| Authorisation server | https://wincher.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wincher.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/wincher/ |
| http (plaintext) | http://wincher.usefulapi.io/mcp | Inconclusive | 302 | http://wincher.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
wincher_add_keywords Add keywords to track ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| groups | array | – | Keyword group names to assign to all of these keywords (default none). |
| keywords | array | yes | 1-50 keywords to add (each uses one keyword slot). |
| website_id | integer | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_create_annotation Create annotation ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The date the note is shown at, yyyy-mm-dd. |
| description | string | yes | The note text. |
| keyword_ids | array | – | Keyword ids this note relates to; omit for a global note. |
| website_id | integer | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_create_group Create keyword group ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword_ids | array | – | Existing keyword ids to put in the group (default none). |
| name | string | yes | Group name (1-200 characters). |
| website_id | integer | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_get_account Get account and plan limits ~60
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wincher_get_group Get keyword group ~185
One keyword group with its keyword ids and (optionally) ranking summary for the period. GET /websites/{website_id}/groups/{group_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End of the period (date or ISO date-time, UTC). |
| group_id | integer | yes | 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_get_keyword Get keyword ~138
One tracked keyword with its groups, volume, CPC, difficulty and (default) ranking for the period. GET /websites/{website_id}/keywords/{keyword_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher keyword id (from wincher_list_keywords). |
| start | string | – | Start of the period (date or ISO date-time, UTC). |
| website_id | integer | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_get_keyword_ranking_history Get keyword ranking history ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_get_keyword_serps Get keyword SERPs ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword_id | integer | yes | Wincher keyword id (from wincher_list_keywords). |
| website_id | integer | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_get_ranking_history_bulk Get ranking history for several keywords ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | End of the period (date or ISO date-time, UTC). |
| keyword_ids | array | yes | Keyword ids (1-50). |
| start | string | yes | Start of the period (date or ISO date-time, UTC). |
| website_id | integer | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_get_user Get current user ~40
The Wincher user the token belongs to: id, role, state, project access and profile (name, email, language). GET /user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wincher_get_website Get website ~168
One tracked website with its settings, competitors, brand keywords, counts and (for the period) ranking summary. GET /websites/{website_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_annotations List annotations ~102
The annotations (notes on the ranking graphs: automatic, alert and user-written) for a website, optionally within a period. GET /websites/{website_id}/annotations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_competitor_keyword_positions Competitor keyword positions ~126
For each tracked keyword, the position of your site and of each competitor in the period. GET /websites/{website_id}/competitors/keyword-positions.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_competitor_ranking_summaries Competitor ranking summaries ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_competitors List competitors ~128
The competitor domains tracked for a website (id, domain, created_at). GET /websites/{website_id}/competitors.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_groups List keyword groups ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_keywords List keywords ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Wincher website id (from wincher_list_websites). |
No output schema declared.
No examples provided.
wincher_list_projects List projects ~170
List projects (folders that group websites): id, name, website_ids, user_ids, and optionally the ranking summary for a period. GET /projects.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
wincher_list_search_engines List search engines ~41
The search engines Wincher can track (id, domain such as google.com, country, languages, default location). GET /search-engines.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wincher_list_segments List segments ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| only_named | boolean | – | Only named (saved) segments. Default false. |
No output schema declared.
No examples provided.
wincher_list_websites List tracked websites ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
wincher_search_locations Search tracking locations ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US (required by the Wincher API). |
| search | string | yes | Free text, at least 3 characters, e.g. 'new york' (required by the Wincher API). |
No output schema declared.
No examples provided.
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.
remote · wincher.usefulapi.io
claude mcp add --transport http io-usefulapi-wincher 'https://wincher.usefulapi.io/mcp'
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.