Clean, LLM-optimized Reddit MCP server. Browse posts, search content, analyze users. No fluff, just Reddit data.
Nothing to run from here
Site Search Opener is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
12
downloads a day
local
runs on your machine
586
downloads in 30d
What it does
SEO and competitor research from sitemaps and feeds, robots.txt respected, Google link fallback.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user site-search-opener-mcp '--' npx -y site-search-opener-mcp
# 2 — ask your agent for something these tools do
# list-recipes, check-urls, build-project-file and 4 more
Site Search Opener costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Site Search Opener as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user site-search-opener-mcp '--' npx -y site-search-opener-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SSO_OUTPUT_DIR (Folder where save-file writes files. Default: Documents/Site Search Opener in your home folder.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team | string | no | Only this team's recipes |
| all | boolean | no | Every recipe for every team |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | Domains like example.com, folders like example.com/blog/, or full URLs |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projects | array | yes | — |
| validate | boolean | no | Check every domain returns HTTP 200 before adding it |
| merge_with_json | string | no | An existing project file to add these projects to |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | array | no | One or more keywords. Several keywords become one OR group (or one link each for inurl:) |
| targets | array | no | Domains or folders, for example competitor.com or competitor.com/blog/ |
| recipe | string | no | Use a recipe's query instead of operator and filters |
| operator | string | no | — |
| exact | boolean | no | Wrap each keyword in quotes |
| exclude | array | no | Words to exclude |
| filetype | string | no | pdf, docx, xlsx and so on |
| after | string | no | YYYY-MM-DD |
| before | string | no | YYYY-MM-DD |
| own | array | no | Your own domain, used by recipes that exclude it |
| engine | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | A domain or folder, for example competitor.com or competitor.com/blog/ |
| keywords | array | no | Keep pages whose URL or title contains all words of any keyword |
| url_contains | array | no | Keep pages whose URL path contains any of these, for example /blog/ or case-stud |
| since | string | no | Keep pages modified on or after YYYY-MM-DD |
| older_than | string | no | Keep pages last modified before YYYY-MM-DD |
| subdomains | array | no | Also read these subdomains, for example docs or help |
| limit | integer | no | Rows to return |
| page_details | integer | no | For this many top rows, fetch the page for HTTP status, title and description |
| folders | boolean | no | Include a count of pages per top folder |
| format | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipe | string | yes | Recipe id from list-recipes |
| keywords | array | no | Keyword(s). Some recipes need one, semantic-depth needs two |
| targets | array | no | Domains or folders. Leave empty to use project_json |
| project_json | string | no | A project file from build-project-file or the web app export |
| project_name | string | no | Which project in the file. Default: the first one |
| since | string | no | Override the recipe's start date, YYYY-MM-DD |
| limit_per_domain | integer | no | — |
| page_details | integer | no | Per domain, fetch this many top pages for HTTP status, title and description |
| format | string | no | — |
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Site Search Opener or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 1.1.1 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 3 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digestf4861da93e0f4167b2a481d07eee8c922815b0a998bcd4691b51c5ae4a0eca8d
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list-recipes | no tags | |
| check-urls | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| build-project-file | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| google-links | no tags | |
| site-inventory | untrusted-input | untrusted-input: keyword "rss", declares openWorldHint: true (interacts with entities outside the server) |
| run-recipe | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| save-file | file-writestate-write | file-write: keyword "save_file" in tool name; state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf4861da93e0f4167
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.1. Pin a release below and the command asks for exactly that one.
1.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Site Search Opener can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.