# EdGEO (npm · edgeo-mcp)

Local MCP for evidence-based SEO, GEO, Google AI Search, and Search Console.

- Trust score: 83/100 (high trust)
- Change this week: +16
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `edgeo-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/edgarcia-id-edgeo/edgeo-mcp.md), [page](https://verifymcp.io/servers/edgarcia-id-edgeo/edgeo-mcp)

## Channel facts

- Registry: `npm`
- Package: `edgeo-mcp`
- Version: `0.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 27 dependencies flagged as unhealthy (1 deprecated).
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to edgarcia-id/edgeo).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 4 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 878 tokens (~97/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 19% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "edgeo_query_model" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the EdGEO MCP server?

EdGEO runs locally as an npm package, launched with npx -y edgeo-mcp. 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 edgarcia-id-edgeo -- npx -y edgeo-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "edgarcia-id-edgeo": {
      "command": "npx",
      "args": [
        "-y",
        "edgeo-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "edgarcia-id-edgeo": {
      "command": "npx",
      "args": [
        "-y",
        "edgeo-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add edgarcia-id-edgeo -- npx -y edgeo-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "edgarcia-id-edgeo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "edgeo-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add edgarcia-id-edgeo --command npx --arg -y --arg edgeo-mcp
```

### Hermes

```yaml
mcp_servers:
  edgarcia-id-edgeo:
    command: "npx"
    args: ["-y", "edgeo-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "edgarcia-id-edgeo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "edgeo-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add edgarcia-id-edgeo -t stdio -c npx -a -y edgeo-mcp
```

### Other

```json
{
  "mcpServers": {
    "edgarcia-id-edgeo": {
      "command": "npx",
      "args": [
        "-y",
        "edgeo-mcp"
      ]
    }
  }
}
```

## 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-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +27)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.95

### 2026-10-31 (score 54, −13)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: edgarcia-id/edgeo
- [functional regression] Dependency health: 0.95 → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.1.2 → 0.1.4
- [functional] Package version: 0.1.2 → 0.1.3

### 2026-10-27 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 52)

First indexed and scored.

## MCP tools (9)

### `edgeo_audit_page` (~63 tokens)

Audit a public webpage

Fetch and audit one public HTTP/HTTPS HTML page for observable technical SEO and page-structure signals. Does not render JavaScript, measure Core Web Vitals, or verify search indexing.

Input parameters:

- `url` (string, required): Public HTTP or HTTPS page URL to inspect.

### `edgeo_crawl_site` (~143 tokens)

Crawl and audit a public site

Run a bounded same-host HTML crawl seeded from the start URL and same-host sitemap URLs. Defaults to 50 attempted URLs and accepts up to 200. Preserves trailing slashes when requesting URLs, reads robots.txt first, applies its rules and crawl-delay, separates non-HTML sitemap resources, and never renders JavaScript or follows links to other hosts. Reports known queued URL counts, not sitewide coverage.

Input parameters:

- `delayMs` (integer)
- `maxPages` (integer): Maximum URL fetch attempts, including non-HTML sitemap resources and URL variants that redirect to an already seen page.
- `url` (string, required): Public HTTP or HTTPS start URL.

### `edgeo_analyze_visibility` (~71 tokens)

Analyze supplied AI answers

Analyze caller-supplied answers with transparent brand alias and citation checks. Keeps prompt types and failures separate; does not call models or automatically label recommendations.

Input parameters:

- `aliases` (array)
- `brandDomain` (string)
- `brandName` (string, required)
- `observations` (array, required)

### `edgeo_compare_visibility_runs` (~96 tokens)

Compare two sets of supplied AI answers

Compare complete answers only when the normalized prompt and recorded source, provider, model, surface, locale, search mode, and prompt type match. Returns paired mention and citation changes with sample counts; does not infer causation or call AI providers.

Input parameters:

- `after` (array, required)
- `aliases` (array)
- `before` (array, required)
- `brandDomain` (string)
- `brandName` (string, required)

### `edgeo_summarize_search_console` (~64 tokens)

Summarize supplied Search Console rows

Summarize user-supplied Search Console rows by provided feature label, including clicks, impressions, CTR, and impression-weighted average position. Does not connect to Google or infer an AI feature from unlabeled data.

Input parameters:

- `rows` (array, required)

### `edgeo_import_search_console_csv` (~74 tokens)

Import a Search Console CSV locally

Parse a user-provided CSV or TSV export in memory, recognize common English and Indonesian Search Console headers, and return a transparent summary. The file contents are not uploaded or persisted by this tool.

Input parameters:

- `columnMap` (object)
- `csvText` (string, required)
- `delimiter` (string)

### `edgeo_query_model` (~144 tokens)

Collect one AI model answer

Send one prompt to a configured local Ollama model or, with explicit consent and GEMINI_API_KEY configured, Google Gemini API. Returns an observation ready for EdGEO visibility analysis. Provider API output is not equivalent to a consumer AI app or Google AI Search result; no citations are assumed.

Input parameters:

- `consentToExternalRequest` (boolean): Must be true to send a prompt to the external Gemini API. Not needed for Ollama loopback.
- `locale` (string, required)
- `maxOutputTokens` (integer)
- `model` (string, required)
- `prompt` (string, required)
- `promptType` (string, required)
- `provider` (string, required)

### `edgeo_search_console_sites` (~83 tokens)

List connected Search Console properties

List Google Search Console properties for the user's locally authorized Google account. Requires prior setup with `edgeo-mcp search-console connect`; uses a read-only OAuth scope and returns only properties the Google account can access. Optionally filter property URLs by a case-insensitive substring.

Input parameters:

- `siteUrlContains` (string): Optional case-insensitive substring to filter property URLs.

### `edgeo_search_console_query` (~140 tokens)

Query Google Search Console

Query the user's authorized Google Search Console property for web, image, video, news, Discover, or Google News performance rows. Requires `edgeo-mcp search-console connect`. Reads Search Console directly with OAuth read-only access; AI feature labels are never inferred from generic search rows.

Input parameters:

- `aggregationType` (string)
- `dimensions` (array)
- `endDate` (string, required)
- `rowLimit` (integer)
- `searchType` (string)
- `siteUrl` (string, required): Verified Search Console property, such as https://example.com/ or sc-domain:example.com.
- `startDate` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/edgarcia-id-edgeo/edgeo-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 54
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 52

## Common questions

### What is the EdGEO MCP server?

EdGEO is an MCP server listed in the public MCP registry as io.github.edgarcia-id/edgeo. Local MCP for evidence-based SEO, GEO, Google AI Search, and Search Console. This page covers its npm package (edgeo-mcp).

### Is the EdGEO MCP server safe to use?

EdGEO scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 EdGEO MCP server expose?

EdGEO exposes 9 tools: edgeo_audit_page, edgeo_crawl_site, edgeo_analyze_visibility, edgeo_compare_visibility_runs, edgeo_summarize_search_console, and 4 more. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.

### Is the EdGEO MCP server still maintained?

EdGEO is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the EdGEO MCP server under?

EdGEO declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/edgeo-mcp
- Socket report: https://socket.dev/npm/package/edgeo-mcp
- Repository: https://github.com/edgarcia-id/edgeo
- Changelog RSS feed: https://verifymcp.io/servers/edgarcia-id-edgeo/edgeo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/edgarcia-id-edgeo/edgeo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/edgarcia-id-edgeo/edgeo-mcp