Skip to main content
Glama

Rank Checker by GSC Wizard

Server Details

Daily Google rankings for the keywords you choose, from your own Search Console data.

Ownership verified
Status
Healthy
Uptime
33.3% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
jbobbink/seo-rank-checker
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation4/5

Tools target distinct objects (account, sites, keyword sets, keyword data, single-query trend, top queries, period movers) and descriptions explicitly cross-reference siblings ("Not for X: use Y"), which resolves most confusion. The only mild overlap is among the query-oriented tools (query_top_queries vs get_query_performance vs get_ranking_changes), but their boundary is drawn clearly (ranked list / single-query daily / period comparison).

Naming Consistency4/5

All names are snake_case and follow a verb_noun shape (get_*, list_*, query_top_queries). The only deviation is 'query' used as a verb in query_top_queries, which is slightly odd alongside 'get'/'list' but still readable and predictable.

Tool Count5/5

Seven tools is well-scoped for a GSC rank-checking server: one entry point per resource/workflow (account, sites, sets, keyword data, query performance, top queries, ranking changes) with no redundant filler.

Completeness3/5

The read surface is fairly complete for analysis, but the server is read-only in practice and references operations that don't exist here: add_rank_keywords (to create sets/add keywords) and set_dashboard_visibility (to activate properties that list_sites says are otherwise unusable) are cited in descriptions but absent, leaving dead ends. There is also no way to create, rename, or delete keyword sets or trigger a rank check.

Publisher details

Operator
GSC Wizard · Publisher source
Vendor relationship
First-party
Restrictions
Not available

Available Tools

7 tools
get_account_infoGet account infoA
Read-only
Inspect

Use this when the user asks which Google accounts, scopes or plan their GSC Wizard login has. Returns the authenticated user, the connected Google accounts (email + scopes), and the subscription status. Useful as a first call to confirm the MCP server is wired up correctly and the user has the data sources you expect. Not for the property list: use list_sites. googleAccounts are oldest first (connectedAt ascending); the first is isPrimary, the default account.

Inputs: no named parameters. Returns: user, access, apiKey, thenBy, +14 more

get_query_performanceQuery performance over timeA
Read-only
Inspect

Use this when the user asks how one search query performed day by day. Daily performance for a single search query, optionally restricted to one landing page. Useful for tracking position changes after on-page edits. Not for a ranking of queries: use query_top_queries. query (and pageUrl) must match exactly. Rows run by date, oldest first; days without impressions are absent, not zero. ctr is a 0-100 percentage. Served from the ClickHouse warehouse when available, otherwise the live Search Console API (see dataSource). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Inputs: query (required), siteUrl (required), endDate, pageUrl, +2 more. Returns: note, daily, query, range, +17 more

get_ranking_changesGet ranking changes between two periodsA
Read-only
Inspect

Use this when the user asks which queries or pages moved up or down between two periods: each is filed as new, lost, improved or declined (improved = better, lower average position). Not for pages losing clicks over time: use find_decaying_content. limit (1-10000, default 50) applies PER BUCKET; counts gives the full size of each bucket before that cut. Buckets run largest first: improved and declined by the size of positionDelta (prevPosition minus position; a new or lost key's missing side reads 0), new by clicks, lost by prevClicks. ctr is a 0-100 percentage. Each period reads its top scanLimit keys by clicks (warehouse: max(limit*10, 1000), capped at 50000; live API: 25000), and counts are measured within them. The warehouse reads every key in either period's top scanLimit in both periods, so new and lost are real; on the live API the reads are independent, so a key just below one cut can show as new or lost. Query movers are only the queries Google lists: on most properties a large share of clicks has no query row (analyze_sampling_impact measures it). Served from the GSC Wizard ClickHouse warehouse when available, otherwise the live Search Console API (see dataSource). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Inputs: siteUrl (required), limit, endDate, dimension, +4 more. Returns: Rendered view model consumed by the GSC Wizard widget, plus the result data the…

get_rank_keyword_dataGet Rank Checker positionsA
Read-only
Inspect

Use this when the user asks how their tracked keywords rank, which moved, or for the ranking history of a keyword. Reads the data points the GSC Wizard Rank Checker collected for one keyword set (setId from list_rank_keyword_sets): Search Console average positions for the set's country and device, stored once a day. Without keyword: every keyword's impression-weighted position, clicks and impressions over the period (days: 7, 28, 91, 182, 365 or 485; default 7) against the same number of days before, with the change (positive = better) and the ranking URL, plus the daily trend of the set (average position, top 3 / top 10 counts). period.comparable is false when the period before starts earlier than the stored history (period.storedFrom): then there is no previous position, change, new or lost. With keyword: that keyword's daily data points over the period. Lower position is better. Not for keywords outside a set: use get_query_performance.

Inputs: setId (required), siteUrl (required), days, keyword. Returns: setId, trend, device, period, +10 more

list_rank_keyword_setsList Rank Checker keyword setsA
Read-only
Inspect

Use this when the user asks which keywords they track in the Rank Checker, or before reading or adding to a keyword set. Returns every Rank Checker keyword set on a property, whoever on the team made it (createdByYou says whether the caller did): each set's id, name, country and device (null = all), alert settings, keyword count, the summary of its last daily check (average position, top 3 / top 10 counts, keywords ranking, improved and declined over the last 7 days) and when it was checked. Not for the positions themselves: use get_rank_keyword_data with a set id; to create a set or add keywords use add_rank_keywords.

Inputs: siteUrl (required). Returns: sets, siteUrl, nextStep, emptyBecause, +1 more

list_sitesList Search Console propertiesA
Read-only
Inspect

Use this when the user asks which Search Console properties they can analyze. Lists all Google Search Console properties connected to the authenticated GSC Wizard account: the site URL (a domain property prefixed with sc-domain: or a URL prefix property), tags, and which data source backs the property. Properties another user has shared with you are included too, badged with sharedBy (the owner) and accessLevel (READ_ONLY or FULL). Each property row carries permissionLevel, readable and activated; a table view shows the last two as its Status column ("Not verified in GSC" for readable: false, "Not activated" for activated: false, empty when both are true). permissionLevel is the Google Search Console permission (siteOwner / siteFullUser / siteRestrictedUser / siteUnverifiedUser), and readable: false means Google will refuse every data request for that property: it is listed in Search Console but not verified, so the user must verify it at search.google.com/search-console before any report will work, and other tools refuse it with reason property_not_verified. Do not attempt reads on a property with readable: false; tell the user to verify it instead. Activating it does not help. activated: false means the property is connected but is not shown on the account dashboard and is not synced to full storage, or is shown but past the plan's dashboard property limit, so every other property-scoped tool will refuse it (reason property_not_selected or over_api_property_limit). Do not attempt reads on those either: where this connection offers it, call set_dashboard_visibility to activate the property first (hiding another one if the plan is at its limit), or choose one with activated: true. Properties shared with the caller are always activated: true, because the grant is itself the selection; a share whose owner no longer has an active GSC Wizard plan is left out, since no tool can read it. gscScope is the Search Console access of the Google connection behind the property: "full" allows submit_sitemap and create_gsc_property, "readonly" means Google will refuse those two (reads still work); absent when unknown. Not for Bing, Yandex or GA4: use list_bing_sites, list_yandex_sites or list_ga4_properties. Owned properties come first, then shared ones, each by siteUrl ascending.

Inputs: no named parameters. Returns: Rendered view model consumed by the GSC Wizard widget, plus the result data the…

query_top_queriesTop search queriesA
Read-only
Inspect

Use this when the user asks which search queries bring a property the most clicks. Returns the top queries over a date range: a wrapper around query_search_analytics. Not for totals: use get_site_summary. Rows are sorted by clicks, highest first; ctr is a 0-100 percentage. Query rows cover only the queries Google lists: coverage.hiddenClicksShare (0-1) is the share of clicks with no query row, so quote totals from coverage.siteTotals, or coverage.filteredTotals when coverage.scope is "filtered", not summed rows. Served from the ClickHouse warehouse (longer history) when available, else the live Search Console API (dataSource says which). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Inputs: siteUrl (required), brand, limit, offset, +5 more. Returns: Rendered view model consumed by the GSC Wizard widget, plus the result data the…

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Google Search Console data including rankings, clicks, and impressions for websites. Provides tools for analyzing search performance, top queries, page metrics, and ranking changes.
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides comprehensive access to Google Search Console data with enhanced analytics capabilities, supporting up to 25,000 rows of performance data, advanced filtering with regex patterns, and automatic quick wins detection for SEO optimization opportunities.
      2
      -
    • A
      license
      A
      quality
      B
      maintenance
      Google Search Console for agents: search analytics by query, page, country, and device, plus a striking-distance report for queries ranking just off page one. Also lists, submits, and removes sitemaps and inspects URLs for index status, last crawl, and canonical.
      7
      56 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive access to Google Search Console data with enhanced analytics capabilities, supporting up to 25,000 rows of performance data, advanced filtering with regex patterns, and automatic detection of SEO optimization opportunities.
      9,552 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.