# Growthr SEO + GEO MCP (remote · mcp.growthr.com)

SEO + GEO tools in your AI editor: scan as ChatGPT and Google crawlers see it, fix order, llms.txt.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.growthr.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-growthr-seo-geo-mcp/mcp.md), [page](https://verifymcp.io/servers/com-growthr-seo-geo-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.growthr.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 682 tokens (~170/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Growthr SEO + GEO MCP server?

Growthr SEO + GEO MCP is a hosted endpoint at https://mcp.growthr.com/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.

### Claude

```bash
claude mcp add --transport http com-growthr-seo-geo-mcp 'https://mcp.growthr.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-growthr-seo-geo-mcp": {
      "url": "https://mcp.growthr.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-growthr-seo-geo-mcp": {
      "type": "http",
      "url": "https://mcp.growthr.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-growthr-seo-geo-mcp]
url = "https://mcp.growthr.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-growthr-seo-geo-mcp": {
      "type": "remote",
      "url": "https://mcp.growthr.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-growthr-seo-geo-mcp --url 'https://mcp.growthr.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-growthr-seo-geo-mcp:
    url: "https://mcp.growthr.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-growthr-seo-geo-mcp": {
      "Transport": "http",
      "Url": "https://mcp.growthr.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-growthr-seo-geo-mcp -t streamable-http -u 'https://mcp.growthr.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-growthr-seo-geo-mcp": {
      "type": "http",
      "url": "https://mcp.growthr.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “growthr_scan” rewrote its description, which is the text the model reads
- [functional] Server version: 1.2.0 → 1.3.0

### 2026-09-18 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-07 (score 69)

First indexed and scored.

## MCP tools (4)

### `growthr_scan` (~209 tokens)

Scan a site for SEO and AI readability

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.

Input parameters:

- `domain` (string, required): Public domain, e.g. example.com (no path)

Output parameters:

- `checks` (array)
- `domain` (string)
- `score` (integer): 0-100
- `throttledCount` (integer): Requests the site answered with HTTP 429

### `growthr_llms_txt` (~117 tokens)

Draft an llms.txt for a site

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.

Input parameters:

- `domain` (string, required): Public domain, e.g. example.com

Output parameters:

- `domain` (string)
- `llmsTxt` (string): The draft, llmstxt.org format
- `notes` (array)
- `pages` (integer): Pages read

### `growthr_fix_order` (~103 tokens)

Order a site's fixes by effort

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.

Input parameters:

- `domain` (string, required): Public domain, e.g. example.com

Output parameters:

- `afternoon` (array)
- `blockers` (array): Check ids to fix before anything else
- `domain` (string)
- `other` (array)
- `score` (integer)
- `sprint` (array)

### `growthr_ai_visibility` (~188 tokens)

Check whether an AI answer names a brand

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.

Input parameters:

- `brand` (string, required): Brand name to look for, e.g. 'Growthr'
- `domain` (string): Optional brand domain, e.g. growthr.com, to detect citations
- `prompt` (string, required): The question a buyer would ask, e.g. 'best corporate event photographer in New York'

Output parameters:

- `against` (boolean)
- `cited` (boolean)
- `engine` (string)
- `mentioned` (boolean)
- `recommended` (boolean)
- `rung` (string)
- `shortlist` (array): Providers the answer put forward
- `shortlistSource` (string)
- `sources` (array): Source domains the answer was built from

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-growthr-seo-geo-mcp/mcp#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69

## Common questions

### What is the Growthr SEO + GEO MCP server?

Growthr SEO + GEO MCP is listed in the public MCP registry as com.growthr/seo-geo-mcp. SEO + GEO tools in your AI editor: scan as ChatGPT and Google crawlers see it, fix order, llms.txt. This page covers its hosted endpoint (https://mcp.growthr.com/mcp).

### Is the Growthr SEO + GEO MCP server safe to use?

Growthr SEO + GEO MCP scores 75 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 Growthr SEO + GEO MCP server expose?

Growthr SEO + GEO MCP exposes 4 tools: growthr_scan, growthr_llms_txt, growthr_fix_order, growthr_ai_visibility. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

### Does the Growthr SEO + GEO MCP server require authentication?

No. We connected to Growthr SEO + GEO MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Growthr SEO + GEO MCP server still maintained?

Growthr SEO + GEO MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.growthr.com/mcp
- Website: https://mcp.growthr.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-growthr-seo-geo-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-growthr-seo-geo-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-growthr-seo-geo-mcp/mcp