Skip to content

MCP servers › io.github.puneetindersingh › open-seo-crawler

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.puneetindersingh/open-seo-crawler

Self-hosted SEO crawler: run site audits and AI crawler checks, then read the issues and pages. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23version 1.0.0Pythonstandard input/output13 tools

Summary

io.github.puneetindersingh/open-seo-crawler is a local MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 13 tools, 0 resources and 1 prompt.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • #963 of 22,952 repositories by GitHub stars, tied with 8 others

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
local package
Transport
standard input/output
Package
MCP bundle
Repository
public
Tools
13
Described as changing data
3 of 13 toolsAI-classified
Mainly works on
files and code on the machine it runs onAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 3 tools are described as changing something (start_crawl, stop_crawl, export_xlsx): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-16 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-16).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
13tools
0resources
1prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

3 of 13 tools are described as changing something (creating, editing, deleting, sending or running).

  • start_crawlon 1 other serverdescribed as changing data

    “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 cra…”

    Publisher declares: read-only no · destructive no · open-world yes

    18 inputs, 1 required
    • urlstringrequired“Start URL, e.g.”
    • max_pagesinteger“Page cap (default 1500; 5000 or more means no cap).”
    • max_depthinteger“Click depth limit (default 10).”
    • max_workersinteger“Parallel fetches (default 5).”
    • crawl_delaynumber“Seconds between requests to one host (default 0.4).”
    • render_jsboolean“Render pages in a headless browser (for JS sites; 3 to 5 times slower).”
    • compare_no_jsboolean“With render_js: also fetch plain HTML and report what only appears with JS.”
    • ignore_robotsboolean“Crawl URLs robots.txt disallows.”
    • ignore_noindexboolean“Follow links on noindex pages too.”
    • include_patternsstring“Only crawl matching URLs, one robots.txt-style pattern per line (* any text, $ end).”
    • exclude_patternsstring“Skip matching URLs, one robots.txt-style pattern per line.”
    • user_agentstring“Blank for Chrome, a preset (chrome-mobile, googlebot, googlebot-mobile, bingbot, firefox, safari) or a full user-agent string.”
    • solve_challengesboolean“Open a browser window to pass a bot challenge if one appears (default true).”
    • sitemapboolean“Compare the crawl with the XML sitemap afterwards (default true).”
    • near_dupboolean“Find near-duplicate pages afterwards (default true).”
    • near_dup_thresholdnumber“Similarity percent for near duplicates (default 90).”
    • bot_checkboolean“Run the AI and search crawler readability check afterwards (default true).”
    • bot_sampleinteger“Pages in the readability sample (default 10).”
  • crawl_statuson 2 other serversreads or searches

    “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.”

    Publisher declares: read-only yes

    1 input
    • jobstring“Job id from start_crawl (default: the latest).”
  • stop_crawldescribed as changing data

    “Stop a running crawl like the Stop button.”

    Publisher declares: read-only no · destructive no

    1 input
    • jobstring“Job id (default: the latest).”
  • list_crawlson 2 other serversreads or searches

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

    Publisher declares: read-only yes

    2 inputs
    • sitestring“Only crawls whose start URL or name contains this.”
    • limitinteger“Default 20.”
  • crawl_summaryreads or searches

    “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 ga…”

    Publisher declares: read-only yes

    2 inputs
    • crawlstring“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_urlsinteger“Sample URLs per issue (default 5).”
  • get_pageson 11 other serversreads or searches

    “Rows of a saved crawl, filtered and paged.”

    Publisher declares: read-only yes

    10 inputs
    • crawlstring“Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.”
    • issuestring
    • severitystring
    • statusstring“A code such as 404, or a class such as 3xx.”
    • url_containsstring
    • indexableboolean
    • fieldsstring“Comma-separated field names, or "all".”
    • limitinteger“Default 50.”
    • offsetinteger
    • sortstring“Default: most issues first.”
  • get_pageon 100 other serversreads or searches

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

    Publisher declares: read-only yes

    2 inputs, 1 required
    • crawlstring“Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.”
    • urlstringrequired
  • get_briefon 20 other serversreads or searches

    “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.”

    Publisher declares: read-only yes

    3 inputs
    • crawlstring“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_tableboolean“Include the page table (default true).”
    • page_limitinteger“Rows in the page table (default 200).”
  • compare_crawlsreads or searches

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

    Publisher declares: read-only yes

    2 inputs, 2 required
    • beforestringrequired“The older crawl (same forms as crawl elsewhere).”
    • afterstringrequired“The newer crawl.”
  • bot_checkreads or searches

    “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.”

    Publisher declares: read-only yes · open-world yes

    3 inputs, 1 required
    • urlsarrayrequired
    • delaynumber“Seconds between requests (default 0.4).”
    • renderboolean“Also render the browser baseline with JS (default true).”
  • check_robotson 2 other serversreads or searches

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

    Publisher declares: read-only yes · open-world yes

    1 input, 1 required
    • urlstringrequired
  • detect_cmsreads or searches

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

    Publisher declares: read-only yes · open-world yes

    1 input, 1 required
    • urlstringrequired
Show 1 more tool
  • export_xlsxon 1 other servercreates or changes datadescribed as changing data

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

    Publisher declares: read-only no · destructive no

    2 inputs, 1 required
    • crawlstring“Which saved crawl: "latest" (default), a crawl file name from list_crawls, a job id from start_crawl, or part of the site name.”
    • pathstringrequired“Where to write the .xlsx file.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 13 tools
Says what it returns
83% of 12 tools
States limits, defaults or errors
36% of 11 tools
Says when to use it
15% of 13 tools
Items covered per tool
2.4 of 4 on average

Counted from the listing

Parameters with a description
81% of 48
Tools with a description
100% of 13
Typical description length
181 characters

The tool set

Counted from the listing

Tools
13
Size of the list
about 2,437 tokens for an agent to load (characters ÷ 4)
Naming
13 of 13 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 13 of 13 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry
  • No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Repository github.com/puneetindersingh/open-seo-crawlerOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.puneetindersingh
GitHub owner
a personal account (puneetindersingh)
Repository
github.com/puneetindersingh/open-seo-crawler
Stars
70
Repository age
181–365 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • #963 of 22,952 repositories by GitHub stars, tied with 8 others
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.puneetindersingh/open-seo-crawler

Answered from the data above

Is io.github.puneetindersingh/open-seo-crawler safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 3 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.puneetindersingh/open-seo-crawler been security tested?

Partly. 2 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.puneetindersingh/open-seo-crawler do?

It lists 13 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.puneetindersingh/open-seo-crawler change or delete data?

3 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.puneetindersingh/open-seo-crawler publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.puneetindersingh/open-seo-crawler?

In github.com/puneetindersingh/open-seo-crawler, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised11 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
Does not apply to this server · 5
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 317 msConnected after 0 redirects.
  3. Read the inventory: 13 tools, 0 resources, 1 prompt.
  4. 1,087 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
no value
No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.
Pricing modelAI-classified
no value
The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 181–365 days · stars: 10–99
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.puneetindersingh/open-seo-crawler: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.puneetindersingh/open-seo-crawler

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.puneetindersingh/open-seo-crawler)](https://protocolprobe.com/mcp/servers/io.github.puneetindersingh/open-seo-crawler)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology