# Site Search Opener (npm · site-search-opener-mcp)

SEO and competitor research from sitemaps and feeds, robots.txt respected, Google link fallback.

- Trust score: 70/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `site-search-opener-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/albertalbs-site-search-opener-mcp/site-search-opener-mcp.md), [page](https://verifymcp.io/servers/albertalbs-site-search-opener-mcp/site-search-opener-mcp)

## Channel facts

- Registry: `npm`
- Package: `site-search-opener-mcp`
- Version: `1.1.1`
- 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**: 98/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.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 75/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 1279 tokens (~182/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 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 Site Search Opener MCP server?

Site Search Opener runs locally as an npm package, launched with npx -y site-search-opener-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 albertalbs-site-search-opener-mcp -- npx -y site-search-opener-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "albertalbs-site-search-opener-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "site-search-opener-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "albertalbs-site-search-opener-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "site-search-opener-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add albertalbs-site-search-opener-mcp -- npx -y site-search-opener-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "albertalbs-site-search-opener-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "site-search-opener-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add albertalbs-site-search-opener-mcp --command npx --arg -y --arg site-search-opener-mcp
```

### Hermes

```yaml
mcp_servers:
  albertalbs-site-search-opener-mcp:
    command: "npx"
    args: ["-y", "site-search-opener-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "albertalbs-site-search-opener-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "site-search-opener-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add albertalbs-site-search-opener-mcp -t stdio -c npx -a -y site-search-opener-mcp
```

### Other

```json
{
  "mcpServers": {
    "albertalbs-site-search-opener-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "site-search-opener-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-10-28 (score 70, +25)

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

### 2026-10-27 (score 45)

First indexed and scored.

## MCP tools (7)

### `list-recipes` (~95 tokens)

List research recipes

Lists ready-made research recipes. With no options it shows a short start-here list (one per team) and how many more each team has. Pass a team for that team's full list, or all for every recipe. Each recipe says what it finds and whether it reads sitemaps or gives Google links.

Input parameters:

- `all` (boolean): Every recipe for every team
- `team` (string): Only this team's recipes

### `check-urls` (~63 tokens)

Check that URLs work

Checks domains, folders or full URLs and reports the HTTP status (200 means it works), redirects and the final address. Use it before adding domains to a project.

Input parameters:

- `urls` (array, required): Domains like example.com, folders like example.com/blog/, or full URLs

### `build-project-file` (~112 tokens)

Build a project file

Builds a project file (JSON) with own and competitor domains for one or more projects. Domains are checked first and only working ones are kept. The file imports straight into the Site Search Opener web app (Settings > Export/Import Projects > Import) and can be passed back to run-recipe.

Input parameters:

- `merge_with_json` (string): An existing project file to add these projects to
- `projects` (array, required)
- `validate` (boolean): Check every domain returns HTTP 200 before adding it

### `google-links` (~211 tokens)

Make Google search links

Builds Google (or Bing) site: search links for a keyword and a list of domains, or for a recipe. The links are for the user to click; they open in the user's own browser. This tool does not search or read results.

Input parameters:

- `after` (string): YYYY-MM-DD
- `before` (string): YYYY-MM-DD
- `engine` (string)
- `exact` (boolean): Wrap each keyword in quotes
- `exclude` (array): Words to exclude
- `filetype` (string): pdf, docx, xlsx and so on
- `keywords` (array): One or more keywords. Several keywords become one OR group (or one link each for inurl:)
- `operator` (string)
- `own` (array): Your own domain, used by recipes that exclude it
- `recipe` (string): Use a recipe's query instead of operator and filters
- `targets` (array): Domains or folders, for example competitor.com or competitor.com/blog/

### `site-inventory` (~243 tokens)

List a site's pages from its sitemap

Reads one domain's own sitemap.xml and RSS or Atom feeds (robots.txt respected) and returns its pages as a table with URL, title, description, last modified date and HTTP status. Filter by keyword, URL text or date. If the site has no usable sitemap, it returns Google links instead.

Input parameters:

- `folders` (boolean): Include a count of pages per top folder
- `format` (string)
- `keywords` (array): Keep pages whose URL or title contains all words of any keyword
- `limit` (integer): Rows to return
- `older_than` (string): Keep pages last modified before YYYY-MM-DD
- `page_details` (integer): For this many top rows, fetch the page for HTTP status, title and description
- `since` (string): Keep pages modified on or after YYYY-MM-DD
- `subdomains` (array): Also read these subdomains, for example docs or help
- `target` (string, required): A domain or folder, for example competitor.com or competitor.com/blog/
- `url_contains` (array): Keep pages whose URL path contains any of these, for example /blog/ or case-stud

### `run-recipe` (~208 tokens)

Run a research recipe

Runs a team recipe across many domains. Sitemap recipes read each site's own sitemap and feeds (robots.txt respected) and return one combined table; sites without usable sitemaps get Google links instead. Google-only recipes return links. Domains come from targets or from a project file.

Input parameters:

- `format` (string)
- `keywords` (array): Keyword(s). Some recipes need one, semantic-depth needs two
- `limit_per_domain` (integer)
- `page_details` (integer): Per domain, fetch this many top pages for HTTP status, title and description
- `project_json` (string): A project file from build-project-file or the web app export
- `project_name` (string): Which project in the file. Default: the first one
- `recipe` (string, required): Recipe id from list-recipes
- `since` (string): Override the recipe's start date, YYYY-MM-DD
- `targets` (array): Domains or folders. Leave empty to use project_json

### `save-file` (~66 tokens)

Save a file

Saves a project file, CSV or Markdown table to your computer, in /tmp/Documents/Site Search Opener. Existing files are never overwritten; a number is added instead.

Input parameters:

- `content` (string, required)
- `file_name` (string, required): For example competitor-pages.csv or projects.json

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/albertalbs-site-search-opener-mcp/site-search-opener-mcp#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 45

## Common questions

### What is the Site Search Opener MCP server?

Site Search Opener is an MCP server listed in the public MCP registry as io.github.albertalbs/site-search-opener-mcp. SEO and competitor research from sitemaps and feeds, robots.txt respected, Google link fallback. This page covers its npm package (site-search-opener-mcp).

### Is the Site Search Opener MCP server safe to use?

Site Search Opener scores 70 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. 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 Site Search Opener MCP server expose?

Site Search Opener exposes 7 tools: list-recipes, check-urls, build-project-file, google-links, site-inventory, and 2 more. Their descriptions and schemas cost roughly 998 tokens of context every time the server is loaded.

### Is the Site Search Opener MCP server still maintained?

Site Search Opener 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 Site Search Opener MCP server under?

Site Search Opener 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/site-search-opener-mcp
- Socket report: https://socket.dev/npm/package/site-search-opener-mcp
- Repository: https://github.com/albertalbs/site-search-opener-mcp
- Website: https://bestseo.tips/tools/site-search-opener/
- Changelog RSS feed: https://verifymcp.io/servers/albertalbs-site-search-opener-mcp/site-search-opener-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/albertalbs-site-search-opener-mcp/site-search-opener-mcp.json
- HTML version of this page: https://verifymcp.io/servers/albertalbs-site-search-opener-mcp/site-search-opener-mcp