Summary

The job model shapes every call worth making here: creating returns an id, and reading is a separate step.

create_serp and create_keyword hand back an id, get_serp and get_keyword fetch the result, the delete calls clear it, and the list variants exist so a batch is one request instead of a queue of them; synchronous:true moves the polling server-side, which is convenient right up until a job is slow. What raises the confidence in this surface is how plainly the descriptions name their own edges — get_whois may return 5xx under registrar throttling and is worth retrying, get_technologies comes back with empty arrays for some large sites, a 404 from delete_keyword means the job is either gone or past its retention window, and list_regions is explicitly safe to cache for 24h.

What it is

A client for the GeoRanker API in 17 tools, covering SERP creation and retrieval, keyword jobs and suggestions, multi-region comparison, region listing, WHOIS and domain technology lookups, and account status.

What you get

SERPs handled as jobs rather than blocking calls: create_serp takes keyword, region and searchEngine with optional device, maxResults, language and a priority of LOW, NORMAL, REALTIME or INSTANT, and returns an id that get_serp reads back; synchronous:true hands the polling to the server instead.
Regions accepted in whichever form you have: an ISO2 code such as "US", a canonical string such as "New York,United States", or a numeric id — and list_regions pages the catalogue filtered by countryCode, type and query, marked safe to cache for 24h.
Bulk routes where per-item calls would cost turns: create_serp_list posts an array of create_serp objects, get_serp_list reads many results from an ids array, and create_keyword_list and get_keyword_list do the same for keyword jobs.
Keyword work end to end: create_keyword takes a keywords array with region, language, source, searchPartners, suggestions and priority; search_keywords takes a seed and returns a suggestions array; get_keyword reads a job by id and delete_keyword removes one.
The same keyword across places in one request: compare_locations creates a SERP for each region in a regions list and waits for them.
Background on a domain: get_whois returns registration data, and get_technologies returns the technologies detected on it.
Account and queue visibility: heartbeat reports API status and the state of the queues, and get_user returns the current account with its remaining credits.

Requirements

A GeoRanker API key, supplied as GEORANKER_API_KEY, and credit on the account — get_user reports the balance alongside the current user.

Setup effort

One command plus a key — npm i -g georanker-mcp, then supply credentials