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.
Available components
Last scanned (18 hours ago)
Scores higher than 81% of MCPB servers
Category Marketing and SEO
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- 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).Unverified
- Install-script risk not yet assessed.Unverified
- 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).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)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 scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)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).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 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.
- 25 Oct 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.
- 23 Oct 26 +3
- Stability: unverified → 0.23 ▲ functional
- 16 Oct 26 41
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 5 Nov 2026 · Analysed mcpb/https://github.com/puneetindersingh/open-seo-crawler/releases/download/mcp-v1.0.0/open-seo-crawler-mcp.mcpb@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
bot_check AI and search crawler readability ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| delay | number | – | Seconds between requests (default 0.4). |
| render | boolean | – | Also render the browser baseline with JS (default true). |
| urls | array | yes | – |
No output schema declared.
No examples provided.
check_robots robots.txt ~40
Fetch and parse a site's robots.txt: rules, sitemaps, and which search and AI crawlers it blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
compare_crawls Compare two crawls ~59
Diff two saved crawls of a site: pages added, removed and changed, and how the issue counts moved.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | yes | The newer crawl. |
| before | string | yes | The older crawl (same forms as crawl elsewhere). |
No output schema declared.
No examples provided.
crawl_status Crawl progress ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | – | Job id from start_crawl (default: the latest). |
No output schema declared.
No examples provided.
crawl_summary Crawl summary ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
detect_cms Detect the CMS ~36
Identify the CMS behind a URL, with the crawl settings and exclude patterns the app suggests for it.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
export_xlsx Export to Excel ~84
Write a saved crawl to an .xlsx file on this computer (All Pages and Issues Summary sheets).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Where to write the .xlsx file. |
No output schema declared.
No examples provided.
get_brief Crawl brief (Markdown) ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_page One page in detail ~91
Everything the crawl holds for one URL (meta, headings, canonical, hreflang, schema types, links, images, issues) plus the internal links pointing at it.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
get_pages Pages from a crawl ~244
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
list_crawls Saved crawls ~60
Saved crawls from the last 30 days, newest first (crawls from the app and from here).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 20. |
| site | string | – | Only crawls whose start URL or name contains this. |
No output schema declared.
No examples provided.
start_crawl Start a crawl ~482
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
stop_crawl Stop a crawl ~43
Stop a running crawl like the Stop button. Pages fetched so far are kept, checked and saved.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | – | Job id (default: the latest). |
No output schema declared.
No examples provided.
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.
mcpb · open-seo-crawler-mcp.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3
macOS / Linux
echo "b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3 open-seo-crawler-mcp.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\open-seo-crawler-mcp.mcpb).Hash -eq "b858e554bd585e919f3eefe4e74dfb37324dba9ddc29c37fbcf86d6e25c836e3"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.