# Open SEO Crawler (mcpb · open-seo-crawler-mcp.mcpb)

Self-hosted SEO crawler: run site audits and AI crawler checks, then read the issues and pages.

- Trust score: 50/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `open-seo-crawler-mcp.mcpb`: 50/100 (this document), [markdown](https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp.md), [page](https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/puneetindersingh/open-seo-crawler/releases/download/mcp-v1.0.0/open-seo-crawler-mcp.mcpb`
- Version: `1.0.0`
- Transport: `stdio`
- SHA-256: `b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3`

## 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**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/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).
  - Context-footprint check failed: tool/resource definitions use about 1675 tokens (~128/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Open SEO Crawler MCP server?

Open SEO Crawler ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/puneetindersingh/open-seo-crawler/releases/download/mcp-v1.0.0/open-seo-crawler-mcp.mcpb`
- SHA-256: `b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3`

### Verify on macOS / Linux

```bash
echo "b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3  open-seo-crawler-mcp.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\open-seo-crawler-mcp.mcpb).Hash -eq "b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3"
```

## 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 50, +1)

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

### 2026-11-02 (score 49, +1)

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

### 2026-10-31 (score 48, +1)

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

### 2026-10-29 (score 47, +1)

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

### 2026-10-27 (score 46, +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-10-25 (score 45, +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-10-23 (score 44, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-10-16 (score 41)

First indexed and scored.

## MCP tools (13)

### `start_crawl` (~482 tokens)

Start a crawl

Crawl a website with the same engine and defaults as the app (1500 pages, 5 workers, 0.4 s delay per host, depth 10, robots.txt respected; then sitemap analysis, near-duplicate content and the AI crawler readability check). Returns a job id at once; poll crawl_status. Set max_pages low (20 to 100) for a quick look. The finished crawl is saved and also shows under Load in the app.

Input parameters:

- `bot_check` (boolean): Run the AI and search crawler readability check afterwards (default true).
- `bot_sample` (integer): Pages in the readability sample (default 10).
- `compare_no_js` (boolean): With render_js: also fetch plain HTML and report what only appears with JS.
- `crawl_delay` (number): Seconds between requests to one host (default 0.4).
- `exclude_patterns` (string): Skip matching URLs, one robots.txt-style pattern per line.
- `ignore_noindex` (boolean): Follow links on noindex pages too.
- `ignore_robots` (boolean): Crawl URLs robots.txt disallows. Only on sites you own or may crawl.
- `include_patterns` (string): Only crawl matching URLs, one robots.txt-style pattern per line (* any text, $ end).
- `max_depth` (integer): Click depth limit (default 10).
- `max_pages` (integer): Page cap (default 1500; 5000 or more means no cap).
- `max_workers` (integer): Parallel fetches (default 5).
- `near_dup` (boolean): Find near-duplicate pages afterwards (default true).
- `near_dup_threshold` (number): Similarity percent for near duplicates (default 90).
- `render_js` (boolean): Render pages in a headless browser (for JS sites; 3 to 5 times slower).
- `sitemap` (boolean): Compare the crawl with the XML sitemap afterwards (default true).
- `solve_challenges` (boolean): Open a browser window to pass a bot challenge if one appears (default true).
- `url` (string, required): Start URL, e.g. https://example.com/
- `user_agent` (string): Blank for Chrome, a preset (chrome-mobile, googlebot, googlebot-mobile, bingbot, firefox, safari) or a full user-agent string.

### `crawl_status` (~71 tokens)

Crawl progress

Progress of a crawl started in this session: state (crawling, sitemap, near_dup, bot_check, saving, done, stopped, error), pages so far, queue, and the saved crawl name once done.

Input parameters:

- `job` (string): Job id from start_crawl (default: the latest).

### `stop_crawl` (~43 tokens)

Stop a crawl

Stop a running crawl like the Stop button. Pages fetched so far are kept, checked and saved.

Input parameters:

- `job` (string): Job id (default: the latest).

### `list_crawls` (~60 tokens)

Saved crawls

Saved crawls from the last 30 days, newest first (crawls from the app and from here).

Input parameters:

- `limit` (integer): Default 20.
- `site` (string): Only crawls whose start URL or name contains this.

### `crawl_summary` (~115 tokens)

Crawl summary

What the Summary tab shows, as data: pages, status codes, indexable pages, every issue grouped into errors, warnings and info with page counts and sample URLs, duplicates, redirect chains, sitemap gaps, near duplicates and the bot readability results.

Input parameters:

- `crawl` (string): Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.
- `sample_urls` (integer): Sample URLs per issue (default 5).

### `get_pages` (~244 tokens)

Pages from a crawl

Rows of a saved crawl, filtered and paged. Filter by issue (a Summary heading such as "Missing H1", or any text from the issue), severity, status (404, 3xx), URL text or indexability. Default fields: url, status_code, title, title_len, meta_description, meta_len, h1, word_count, depth, indexable, canonical, canonical_kind, response_time, issues. fields="all" returns every field (large).

Input parameters:

- `crawl` (string): Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.
- `fields` (string): Comma-separated field names, or "all".
- `indexable` (boolean)
- `issue` (string)
- `limit` (integer): Default 50.
- `offset` (integer)
- `severity` (string)
- `sort` (string): Default: most issues first.
- `status` (string): A code such as 404, or a class such as 3xx.
- `url_contains` (string)

### `get_page` (~91 tokens)

One page in detail

Everything the crawl holds for one URL (meta, headings, canonical, hreflang, schema types, links, images, issues) plus the internal links pointing at it.

Input parameters:

- `crawl` (string): Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.
- `url` (string, required)

### `get_brief` (~120 tokens)

Crawl brief (Markdown)

The app's AI brief for a crawl: a Markdown report grouped by severity with capped URL lists and a page table, under an audit prompt. Good as one read of a whole crawl.

Input parameters:

- `crawl` (string): Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.
- `page_limit` (integer): Rows in the page table (default 200).
- `page_table` (boolean): Include the page table (default true).

### `compare_crawls` (~59 tokens)

Compare two crawls

Diff two saved crawls of a site: pages added, removed and changed, and how the issue counts moved.

Input parameters:

- `after` (string, required): The newer crawl.
- `before` (string, required): The older crawl (same forms as crawl elsewhere).

### `bot_check` (~102 tokens)

AI and search crawler readability

Fetch pages as Googlebot, Bingbot, AI search, AI assistant and training crawlers and compare each with what a browser gets: blocked, CDN challenge, noindex, redirected, thinner or different content. Requests come from this computer with each crawler's user agent.

Input parameters:

- `delay` (number): Seconds between requests (default 0.4).
- `render` (boolean): Also render the browser baseline with JS (default true).
- `urls` (array, required)

### `check_robots` (~40 tokens)

robots.txt

Fetch and parse a site's robots.txt: rules, sitemaps, and which search and AI crawlers it blocks.

Input parameters:

- `url` (string, required)

### `detect_cms` (~36 tokens)

Detect the CMS

Identify the CMS behind a URL, with the crawl settings and exclude patterns the app suggests for it.

Input parameters:

- `url` (string, required)

### `export_xlsx` (~84 tokens)

Export to Excel

Write a saved crawl to an .xlsx file on this computer (All Pages and Issues Summary sheets).

Input parameters:

- `crawl` (string): Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.
- `path` (string, required): Where to write the .xlsx file.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp#diagnostics

## Score history

- 2026-11-05: 50
- 2026-11-04: 49
- 2026-11-03: 49
- 2026-11-02: 49
- 2026-11-01: 48
- 2026-10-31: 48
- 2026-10-30: 47
- 2026-10-29: 47
- 2026-10-28: 46
- 2026-10-27: 46
- 2026-10-26: 45
- 2026-10-25: 45
- 2026-10-24: 44
- 2026-10-23: 44
- 2026-10-22: 41
- 2026-10-21: 41
- 2026-10-20: 41
- 2026-10-19: 41
- 2026-10-18: 41
- 2026-10-17: 41
- 2026-10-16: 41

## Common questions

### What is the Open SEO Crawler MCP server?

Open SEO Crawler is an MCP server listed in the public MCP registry as io.github.puneetindersingh/open-seo-crawler. Self-hosted SEO crawler: run site audits and AI crawler checks, then read the issues and pages. This page covers its MCPB bundle (https://github.com/puneetindersingh/open-seo-crawler/releases/download/mcp-v1.0.0/open-seo-crawler-mcp.mcpb).

### Is the Open SEO Crawler MCP server safe to use?

Open SEO Crawler scores 50 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 Open SEO Crawler MCP server expose?

Open SEO Crawler exposes 13 tools: start_crawl, crawl_status, stop_crawl, list_crawls, crawl_summary, and 8 more. Their descriptions and schemas cost roughly 1,547 tokens of context every time the server is loaded.

### What licence is the Open SEO Crawler MCP server under?

Open SEO Crawler declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Open SEO Crawler MCP server?

VerifyMCP ran 12 checks on Open SEO Crawler, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Open SEO Crawler: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/puneetindersingh/open-seo-crawler
- Changelog RSS feed: https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp.json
- HTML version of this page: https://verifymcp.io/servers/puneetindersingh-open-seo-crawler/open-seo-crawler-mcp