# GEO Optimizer — AI Search & Crawler Readiness Audit (remote · geooptimizer.tech)

Audit any URL for GEO readiness, JSON-LD schemas, and AI crawler robots.txt permissions.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `geooptimizer.tech`: 58/100 (this document), [markdown](https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp.md), [page](https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp)

## Channel facts

- Endpoint: `https://geooptimizer.tech/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 137 tokens (~68/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the GEO Optimizer — AI Search & Crawler Readiness Audit MCP server?

GEO Optimizer — AI Search & Crawler Readiness Audit is a hosted endpoint at https://geooptimizer.tech/api/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 tech-geooptimizer-geo-audit 'https://geooptimizer.tech/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-geooptimizer-geo-audit": {
      "url": "https://geooptimizer.tech/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-geooptimizer-geo-audit": {
      "type": "http",
      "url": "https://geooptimizer.tech/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-geooptimizer-geo-audit]
url = "https://geooptimizer.tech/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-geooptimizer-geo-audit": {
      "type": "remote",
      "url": "https://geooptimizer.tech/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-geooptimizer-geo-audit --url 'https://geooptimizer.tech/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-geooptimizer-geo-audit:
    url: "https://geooptimizer.tech/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-geooptimizer-geo-audit": {
      "Transport": "http",
      "Url": "https://geooptimizer.tech/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-geooptimizer-geo-audit -t streamable-http -u 'https://geooptimizer.tech/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-geooptimizer-geo-audit": {
      "type": "http",
      "url": "https://geooptimizer.tech/api/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-11-21 (score 58)

First indexed and scored.

## MCP tools (2)

### `audit_url_geo` (~80 tokens)

Run a live Generative Engine Optimization (GEO) audit on any URL: checks HTTPS, response time, JSON-LD schemas, headings, and AI crawler robots.txt permissions (GPTBot, ClaudeBot, PerplexityBot, Google-Extended).

Input parameters:

- `url` (string, required): Full URL to audit (e.g. "https://example.com").

### `check_ai_crawler_access` (~57 tokens)

Inspect a domain robots.txt policy for major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot).

Input parameters:

- `domain` (string, required): Domain name (e.g. "example.com").

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp#diagnostics

## Score history

- 2026-11-21: 58

## Common questions

### What is the GEO Optimizer — AI Search & Crawler Readiness Audit MCP server?

GEO Optimizer — AI Search & Crawler Readiness Audit is an MCP server listed in the public MCP registry as tech.geooptimizer/geo-audit. Audit any URL for GEO readiness, JSON-LD schemas, and AI crawler robots.txt permissions. This page covers its hosted endpoint (https://geooptimizer.tech/api/mcp).

### Is the GEO Optimizer — AI Search & Crawler Readiness Audit MCP server safe to use?

GEO Optimizer — AI Search & Crawler Readiness Audit scores 58 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 GEO Optimizer — AI Search & Crawler Readiness Audit MCP server expose?

GEO Optimizer — AI Search & Crawler Readiness Audit exposes 2 tools: audit_url_geo, check_ai_crawler_access. Their descriptions and schemas cost roughly 137 tokens of context every time the server is loaded.

### Does the GEO Optimizer — AI Search & Crawler Readiness Audit MCP server require authentication?

No. We connected to GEO Optimizer — AI Search & Crawler Readiness Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GEO Optimizer — AI Search & Crawler Readiness Audit MCP server still maintained?

GEO Optimizer — AI Search & Crawler Readiness Audit is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the GEO Optimizer — AI Search & Crawler Readiness Audit MCP server?

VerifyMCP ran 11 checks on GEO Optimizer — AI Search & Crawler Readiness Audit, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 7 more. 2 items could not be completed, a gap on our side rather than a finding about GEO Optimizer — AI Search & Crawler Readiness Audit: Authorization and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://geooptimizer.tech/api/mcp
- Website: https://geooptimizer.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tech-geooptimizer-geo-audit/api-mcp
