Growthr SEO + GEO MCP server

• growthr_ai_visibilitywrite actionFree

  Run one buyer-shaped prompt through Gemini with Google Search grounding (a real, cited web search, the same mechanism behind Google AI Overviews) and report where the brand lands on the five-rung ladder: absent, cited (a page of the brand's site is a source), mentioned (named in the text), recommended (on the shortlist), or recommended against. Also returns the other names on the shortlist and the source domains the answer was built from. One prompt per call; limited to a few calls per day per user because grounded requests are billed per query.

• growthr_fix_orderwrite actionFree

  Run the scan and sort every failed check into buckets: blockers (fix before anything else, they hide everything downstream), this afternoon (metadata, llms.txt, trust pages, on-page), needs a sprint (schema, markdown negotiation, speed), and the off-site work no scan can measure (reviews, directories, third-party mentions), which is what decides whether AI engines recommend a business.

• growthr_llms_txtFree

  Read a site's homepage, sitemap (or homepage links), and up to twelve pages, then draft an llms.txt in the llmstxt.org format: H1 name, blockquote summary, grouped page list with one-line descriptions, contact, profiles, links. The 'When to use' section is left as a marked placeholder on purpose; it is a judgment about the business that no crawler can write. Returns the draft plus notes on anything skipped.

• growthr_scanFree

  Fetch a public domain the way search engines and AI crawlers do (ChatGPT's GPTBot, Claude's ClaudeBot, and the fetchers behind Perplexity and Google AI Overviews: from a datacenter IP, no JavaScript) and run 22 weighted checks: reachability as a browser, GPTBot, and ClaudeBot; server-rendered content; metadata; strict JSON-LD and Organization schema; robots.txt access for AI crawlers; llms.txt and an in-page link to it; sitemap; honest 404s; markdown negotiation; trust pages; speed; and on-page SEO (title, description, single h1, viewport, alt text, favicon). Returns a 0-100 score and every check with pass/fail, what was found, and a fix hint. Reads about a dozen public URLs once. Growthr logs the domain and tool name for usage stats.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 380ms20/20
• Tool poisoning4 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Growthr SEO + GEO MCP: common questions

Is Growthr SEO + GEO MCP server safe?

With care: it is graded C, so read the findings first (60/100). Read the Growthr SEO + GEO MCP safety report

How do I install Growthr SEO + GEO MCP?

It runs remotely at mcp.growthr.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Growthr SEO + GEO MCP need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Growthr SEO + GEO MCP maintained?

The latest release is v1.2.0.

Is Growthr SEO + GEO MCP up?

100% of our last 7 checks got an answer. We check remote servers about four times a day.

What can I use instead of Growthr SEO + GEO MCP?

Servers from other publishers that do the same job: Accessoticketing MCP server, Apify MCP server and Federal Register MCP server. Compare all Growthr SEO + GEO MCP alternatives.