Growthr SEO + GEO MCP
REMOTE · MCP.GROWTHR.COM · SCANNED SEP 20
SEO + GEO tools in your AI editor: scan as ChatGPT and Google crawlers see it, fix order, llms.txt.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · mcp.growthr.com
claude mcp add --transport http com-growthr-seo-geo-mcp 'https://mcp.growthr.com/mcp'
{
"mcpServers": {
"com-growthr-seo-geo-mcp": {
"url": "https://mcp.growthr.com/mcp"
}
}
} {
"servers": {
"com-growthr-seo-geo-mcp": {
"type": "http",
"url": "https://mcp.growthr.com/mcp"
}
}
} [mcp_servers.com-growthr-seo-geo-mcp] url = "https://mcp.growthr.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-growthr-seo-geo-mcp": {
"type": "remote",
"url": "https://mcp.growthr.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-growthr-seo-geo-mcp --url 'https://mcp.growthr.com/mcp' --transport streamable-http
mcp_servers:
com-growthr-seo-geo-mcp:
url: "https://mcp.growthr.com/mcp" {
"McpServers": {
"com-growthr-seo-geo-mcp": {
"Transport": "http",
"Url": "https://mcp.growthr.com/mcp"
}
}
} assistant mcp add com-growthr-seo-geo-mcp -t streamable-http -u 'https://mcp.growthr.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- 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 security
- Server version: 1.2.0 → 1.3.0 functional
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.growthr.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=growthr.com | CN=WE1,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7de90a266834eb18139cc82f44e49f16 |
| SANs: growthr.com, mcp.growthr.com, *.mcp.growthr.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.growthr.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| growthr.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.growthr.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.growthr.com/mcp | HTTPS enforced | 301 | https://mcp.growthr.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
growthr_ai_visibility Check whether an AI answer names a brand ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name to look for, e.g. 'Growthr' |
| domain | string | – | Optional brand domain, e.g. growthr.com, to detect citations |
| prompt | string | yes | The question a buyer would ask, e.g. 'best corporate event photographer in New York' |
| Name | Type | Req | Description |
|---|---|---|---|
| against | boolean | – | – |
| cited | boolean | – | – |
| engine | string | yes | – |
| mentioned | boolean | – | – |
| recommended | boolean | – | – |
| rung | string | yes | – |
| shortlist | array | yes | Providers the answer put forward |
| shortlistSource | string | – | – |
| sources | array | yes | Source domains the answer was built from |
No examples provided.
growthr_fix_order Order a site's fixes by effort ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain, e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| afternoon | array | yes | – |
| blockers | array | yes | Check ids to fix before anything else |
| domain | string | yes | – |
| other | array | – | – |
| score | integer | yes | – |
| sprint | array | yes | – |
No examples provided.
growthr_llms_txt Draft an llms.txt for a site ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain, e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| llmsTxt | string | yes | The draft, llmstxt.org format |
| notes | array | – | – |
| pages | integer | – | Pages read |
No examples provided.
growthr_scan Scan a site for SEO and AI readability ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain, e.g. example.com (no path) |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| domain | string | yes | – |
| score | integer | yes | 0-100 |
| throttledCount | integer | – | Requests the site answered with HTTP 429 |
No examples provided.
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.