Skip to main content
Glama
730,642 tools. Updated 2026-10-31 21:28

"Google Earth Engine" matching MCP tools:

  • Get the stored day-by-day ranking history for one keyword on one search engine over a date range. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. History is inherently single-engine, so engine is required (use get_keyword_rankings first to compare across engines). Days with no synced data are simply absent from rows rather than filled with a zero or placeholder value -- do not treat a missing date as "not ranking". Bing and Yandex are opt-in and lower-frequency than Google; their responses may report availability as provider_limited, meaning that provider did not return enough data for that day rather than the keyword ranking nowhere.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • Prompts people ask an AI engine (ChatGPT or Google AI Overview) about a topic or brand, from the provider's index of observed answers. Not keywords. Use when: "what do people ask ChatGPT about X", "which prompts mention our brand", building an AI visibility baseline. Not for: Google keywords and volumes, use seo_search_keywords. What the AI engines answer right now, use aeo_run_ai_answers. Returns: List. rows[]: prompt, ai_search_volume (a People Also Ask proxy, not query logs), engines[], mentions_brand (a domain input is cited, a keyword input appears in the answer), cited_domains[], retrieved_domains[] (read while answering but not cited), search_queries[] (the web searches the engine ran), named_brands[], answer_preview, first_seen, last_seen. Give exactly one of keyword or domain. Cost: 31 + 31 per 100 rows. Default 50 rows = 47 credits. Cached 7 days. Example: {"domain": "example.com", "limit": 50}
    ConnectorAPI key
  • The sitemaps submitted for one of the user's properties, with when they were read, how many URLs they carry and their errors. Use when: "is my sitemap picked up", "how many URLs did Google read from the sitemap", checking a submission after a site change. Not for: submitting or resubmitting one, use console_submit_sitemap. Whether one URL is indexed, use console_inspect_url. Finding pages a sitemap misses, use seo_run_technical_crawl. Returns: List. rows[]: path, type, submitted_at, last_read_at, pending, is_index, urls_submitted, urls_indexed (Google reports 0 today), warnings, errors. null = the engine does not say. Cost: 0 credits. Cached 10 minutes. Example: {"property": "https://www.example.com/"}
    ConnectorAPI key
  • Create an indexing task: Rapid Indexer signals Googlebot to crawl each URL so Google discovers it fast. also_bing sends Bingbot to each URL too; engine "bing" sends Bingbot only. Bing is priced per URL (see get_pricing), in beta (not guaranteed) and only available while Bing Indexing is enabled. brave adds Brave Search Boost (signals to Brave's Web Discovery Project, free next to Google); engine "brave" sends Brave only. Not guaranteed. SPENDS CREDITS immediately (standard ~1 credit/URL, VIP ~5 credits/URL). Run estimate_cost first and confirm with the user for large batches. Standard queue starts within minutes; VIP starts immediately with priority. drip_feed spreads submissions over several days for a natural pattern. Returns the task id; poll get_task for progress and get_task_links for per-URL status. Google makes the final indexing decision.
    ConnectorNo auth
  • Shows what Proofsource measures, without signing in: a real visibility card for one example brand (Tesla), from answers collected from ChatGPT, Perplexity, Claude and Google AI Overviews. It shows how often AI answers mention the brand, per engine, which competitors they name instead, and sample answers. Use it when someone asks whether their brand shows up in AI answers and has not signed in. It always shows the example brand; to check their own brand they sign in.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Sentinel and Landsat imagery catalogue from Element 84's Earth Search over the AWS Open Data…

  • Rarefied Earth Groundwork MCP: company memory for AI agents. 14-day full-access trial, no card.

  • Shows what Proofsource measures, without signing in: a real visibility card for one example brand (Tesla), from answers collected from ChatGPT, Perplexity, Claude and Google AI Overviews. It shows how often AI answers mention the brand, per engine, which competitors they name instead, and sample answers. Use it when someone asks whether their brand shows up in AI answers and has not signed in. It always shows the example brand; to check their own brand they sign in.
    ConnectorNo auth
  • Use this when the user asks how something works or why something happens in physics, engineering, AI, biology and medicine, earth and space science or mathematics, or asks to see or try a mechanism: e.g. “why do we have seasons”, “how does a jet engine work”, “潮汐是怎么形成的”, “Transformer 的注意力是什么”. Searches the interactive 3D models (“plates”) on world.lapla.si: first an index of the questions each plate answers (Chinese and English), then titles and topics. Returns the best plates, each with its slug, the chapter that answers the question and sometimes lab settings, to pass to show_model. Returns no results when no plate covers the question. Not for news, prices, homework calculations, or medical, legal or financial advice.
    ConnectorNo auth
  • List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token.
    ConnectorNo auth
  • List all Google Trends category and subcategory labels you can pass to other Google Trends tools in the category field. Returns cat (array of category names, including All categories) and msg. Use this before interest-over-time or interest-by-region calls when filtering by category. Cost = 5 tokens.
    ConnectorNo auth
  • List all countries and subregions you can pass to other Google Trends tools in the country and region fields. Returns geo.countries: each country name maps to country (label) and regions (array of subregion names). Also returns msg. Use this before interest-over-time or interest-by-region calls when filtering by geography. Pair with google-trends.categories when filtering by category. Cost = 5 tokens.
    ConnectorNo auth
  • List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, add a site with google-search-console.add_site or register a domain with domains.register. Cost = 5 tokens.
    ConnectorNo auth
  • Ten planets with sign, degree, whole-sign house and retrograde flag; the Ascendant, midheaven and their opposites; the twelve whole-sign houses; the mean lunar nodes; the five major aspects with orb and whether each is applying or separating; plus stelliums, retrogrades and the Moon's phase. Tropical zodiac, geocentric apparent positions, astronomy-engine. This is the one endpoint that requires lat, lng and tz: the angles and houses are a place on the Earth meeting the sky. A time is optional, and without one the angles and houses are null rather than taken from noon, and the Moon is a noon estimate the notes warn about. The same thing over HTTP: POST https://asternym.com/api/v1/natal.
    ConnectorNo auth
  • The Search Console and Bing Webmaster properties the workspace's connected accounts can read. The first console call; every other console tool takes a property from here. Use when: "what sites are in my Search Console", before any console_get_* call, or to check which engine is connected. Not for: third-party sites the user does not own, use seo_get_domain_overview. Live rankings, use seo_get_serp. Returns: List. rows[]: engine (google | bing), property (the id to pass on: sc-domain:example.com, https://example.com/ or a Bing site URL), permission (Google: siteOwner, siteFullUser, siteRestrictedUser, siteUnverifiedUser; Bing: null), verified. NotConnected when no account of that engine is connected; its connect_url is where the user connects one. Cost: 0 credits. The user's own data is free; 60 console calls per minute per workspace. Cached 1 hour. Example: {"engine": "all"}
    ConnectorAPI key
  • Read an AI citation test, poll until it is done Returns the test started by `POST /api/v1/tools/citation-check`. While `status` is `pending` or `running`, call again every 3 seconds: each engine fills in as soon as it has answered. When `status` is `done`, at least one engine answered; `summary.citedBy` engines cite your domain out of `summary.enginesAnswered` engines that answered. When `status` is `failed`, `failureCode` says why (NO_ENGINE_ANSWERED, TIMEOUT, INTERNAL). Per engine: `cited` is true when a source of the answer is on your registrable domain or one of its subdomains, and `citedUrls` lists those pages; `mentioned` is true when your brand name appears in the answer text, which is NOT a citation. `status` no_answer means the engine showed no answer for this question (Google often shows no AI Overview), which is not a failure. No quota is consumed. The `checkId` is random: whoever holds it can read the test, which is what makes share links work. Tests expire after 30 days. Reads that are not attributed to an account are capped at 1000 per IP address and per UTC day, far above any legitimate polling: crossing it returns 429 READ_RATE_LIMITED with `Retry-After`.
    ConnectorNo auth
  • Long-search finder for a pasted Search Console export. Use this when the user pastes Search Console Performance rows or a CSV and asks which questions to answer on their pages, or how to get named in ChatGPT or Google AI answers. Pass the text as csv, or JSON rows as rows, with query and impressions, and page if there is one. Up to 5000 rows. Returns the searches of 7 or more words ranked by impressions, marked when they look like questions. Each has the page Google shows, the question as a heading, and a 2-sentence answer skeleton with a placeholder for one real number or fact that only the owner knows. Also groups by page. It reads only what is pasted: no Google login, no Search Console call, no AI engine. It does not write the answer or invent the number. Not for a user with no export: ask them to paste one.
    ConnectorNo auth
  • skypeek: List asteroid and comet close approaches to Earth. For space weather use get_space_weather. Returns near-Earth object close approaches to Earth in the next 1-30 days within a miss distance (default 0.05 au, about 19.5 lunar distances): designation, approach time, nominal distance with its 3-sigma range, relative velocity, absolute magnitude and diameter (published or a rough range). Data: NASA/JPL Solar System Dynamics close-approach API (US Government work); no endorsement by NASA or JPL is implied. At most 100 approaches per answer. Not an impact-risk assessment. Cached up to an hour. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/asteroid-close-approach-api.html
    ConnectorNo auth
  • skypeek: List asteroid and comet close approaches to Earth. For space weather use get_space_weather. Returns near-Earth object close approaches to Earth in the next 1-30 days within a miss distance (default 0.05 au, about 19.5 lunar distances): designation, approach time, nominal distance with its 3-sigma range, relative velocity, absolute magnitude and diameter (published or a rough range). Data: NASA/JPL Solar System Dynamics close-approach API (US Government work); no endorsement by NASA or JPL is implied. At most 100 approaches per answer. Not an impact-risk assessment. Cached up to an hour. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/asteroid-close-approach-api.html
    ConnectorNo auth
  • Live search-engine result page as JSON: organic results, ads (paid_results), featured snippets, related questions and searches, knowledge graph. Google by default; set search_engine for Bing, Yandex or DuckDuckGo. SPENDS 1 request of the monthly quota per successful call (failed calls are not charged); do not repeat a call needlessly. ai_overview=true also returns Google's AI Overview and costs 3 requests when one is returned (Small plan or higher). GET /v2/search.
    Connector
    Destructive
    No auth
  • Submits or resubmits a sitemap for one of the user's properties, asking Google or Bing to read it again. A write to the user's own account. Use when: "get my new pages indexed", "I just published", "tell Google about the sitemap", after a site change or migration. Resubmitting the same sitemap is how to say it changed. Not for: specific URLs on Bing now, use console_submit_urls. Whether a page is indexed, use console_inspect_url. Google has no API to request indexing of one URL; the sitemap is the way. Returns: Record. engine, property, sitemap_url, submitted_at (when Manifold sent it). The engine reads it later, usually within hours; console_get_sitemaps shows when. Cost: 0 credits. Never cached. A connection made with read access only answers NotConnected; the user reconnects to grant submit access. Example: {"property": "sc-domain:example.com", "sitemap_url": "https://www.example.com/sitemap.xml"}
    ConnectorAPI key
  • skypeek: List asteroid and comet close approaches to Earth. For space weather use get_space_weather. Returns near-Earth object close approaches to Earth in the next 1-30 days within a miss distance (default 0.05 au, about 19.5 lunar distances): designation, approach time, nominal distance with its 3-sigma range, relative velocity, absolute magnitude and diameter (published or a rough range). Data: NASA/JPL Solar System Dynamics close-approach API (US Government work); no endorsement by NASA or JPL is implied. At most 100 approaches per answer. Not an impact-risk assessment. Cached up to an hour. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/asteroid-close-approach-api.html
    ConnectorNo auth