search-rotation

Name: search-rotation
Author: robin-bially

by robin-biallyversion 0.6.0i★ –iRuns on your computer

Registry nameio.github.robin-bially/search-rotation

Install

Overview

Description from the maker (original English)

MCP server for web search and page extraction across the free tiers of several providers

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "search-rotation": {
      "command": "npx",
      "args": [
        "-y",
        "search-rotation"
      ]
    }
  }
}

Run this in your terminal

claude mcp add search-rotation -- npx -y search-rotation

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "search-rotation": {
      "command": "npx",
      "args": [
        "-y",
        "search-rotation"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "search-rotation": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "search-rotation"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account robin-bially, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7283 servers in this category
Published to the registry more recently than 97% of the other 7283 servers in this category
Basic checks equal to or better than 100% of the other 7283 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is search-rotation safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.6.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

One MCP server for web search and page extraction across multiple providers.

Built by Robin Bially.

Rotate across available quotas, automatically fail over when a provider is unavailable, and return consistent results to your AI assistant. A local dashboard lets you manage API keys, reorder engines, check quotas, and inspect request history.

*Actual dashboard UI, shown in English with illustrative demo data. Calls and provider budgets are displayed separately; activity bars offer time-window and per-engine details.*

Quick start

npm

npx -y search-rotation --http --open

Requires Node.js 20.3+. For MCP over stdio, configure your client to run npx -y search-rotation with no arguments. The server is also listed in the official MCP Registry as io.github.robin-bially/search-rotation.

Homebrew

brew install robin-bially/tap/search-rotation

search-rotation --http --open

Homebrew installs the required Node.js runtime. For MCP over stdio, configure your client to run search-rotation with no arguments. See the Homebrew tap for upgrades and details.

Pinned release from GitHub

npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.6.0

Use this when you want a fixed version instead of the current npm release.

Add your provider keys in the dashboard, then connect your assistant using the [MCP client setup guide](docs/clients.md) for Codex, Claude, Cursor, or OpenCode.

What you get

Search and fetch: independent rotation for web search and Markdown page extraction.
Automatic failover: quota-aware ordering, rate-limit cooldowns, and request timeouts.
Local dashboard: API keys, drag-and-drop engine order, per-engine calls and errors, separate quota balances, and interactive request history.
Local or remote: MCP over stdio or authenticated Streamable HTTP.

Providers: Tavily · Firecrawl · Parallel · Exa · You.com · Google PSE · Jina Reader · DuckDuckGo HTML. Keyless access and quota accounting vary by provider.

MCP tools

search_web · fetch_url · get_engine_status · update_engine_config · open_dashboard

Every name pairs an action with its target. update_engine_config covers what the dashboard's engine list does: enable and disable engines, set the search and fetch rotation order, and set monthly or daily limits per engine. API keys stay in the dashboard. If your client keeps an allowlist of tool names, replace the earlier web_search and engine_status entries there.

searchOrder and fetchOrder must list every search- or fetch-capable engine exactly once. After an upgrade that adds an engine, include its id; the tool names missing ids and writes nothing otherwise.

The dashboard's MCP Tools tab explains each tool, its parameters, and copyable example calls.

*Actual dashboard UI, shown in English.*

Search time filters

search_web accepts the following arguments:

Parameter	Meaning
`query`	Required search text.
`numResults`	Optional result count, 1–20; otherwise the dashboard setting applies.
`engine`	Preferred provider, subject to time-filter support and availability; failover stays enabled.
`timeRange`	`day`, `week`, `month`, or `year`: UTC date window starting 1, 7, 30, or 365 days ago, through today.
`startDate`	Optional lower date bound in `YYYY-MM-DD` format.
`endDate`	Optional upper date bound in `YYYY-MM-DD` format.

Use either timeRange or explicit dates. One-sided bounds and equal start/end dates are allowed; invalid calendar dates, reversed bounds, and mixing relative and explicit filters are rejected before any provider request.

{"name":"search_web","arguments":{"query":"AI inference research","timeRange":"week","numResults":5}}

{"name":"search_web","arguments":{"query":"AI inference research","startDate":"2026-08-01","endDate":"2026-08-31"}}

Relative windows are resolved once per request into UTC dates, including across failover. These are date filters, not exact rolling 24-hour windows; month and year mean 30 and 365 days, not calendar arithmetic. Exa receives the start of the first UTC day and the end of the last UTC day.

Provider support and rotation

Provider / access	Relative window	Two date bounds	One date bound
Tavily, with or without key	Yes	Yes	Yes
Firecrawl, with or without key	Yes	Yes	Skipped
Exa, direct API with key	Yes	Yes	Yes
Exa, hosted MCP without key	Skipped	Skipped	Skipped
You.com, with or without key	Yes	Yes	Skipped
Parallel, either access mode	Skipped	Skipped	Skipped
Google PSE / DuckDuckGo HTML	Skipped	Skipped	Skipped

This table describes implemented support in search-rotation, not every upstream feature. Tavily receives start_date / end_date, Firecrawl receives a custom tbs range, Exa receives startPublishedDate / endPublishedDate, and You.com receives a freshness range in YYYY-MM-DDtoYYYY-MM-DD form. Firecrawl and You.com are conservatively excluded for one-sided dates; the other skipped paths have no implemented date mapping.

The router excludes incompatible providers before quota checks and rotation, including when an incompatible engine is preferred. Each eligible provider pool has its own rotation cursor, so mixing filtered and unfiltered searches does not starve providers. Existing quota priorities, cooldowns, strict-free rules, and failover apply within that pool. If no compatible provider is available, the search fails explicitly; it never retries without the filter. Searches without time arguments retain access to all otherwise eligible providers.

Results show a publication date when supplied by the adapter, and request history includes the requested period. Provider date metadata can be estimated or missing: Tavily filters publication or update dates, Exa filters estimated publication dates, and Firecrawl uses its search index's date interpretation. Exact boundary inclusion follows the provider; this is not an independent verification of each page's publication date. See the Tavily, Firecrawl, and Exa references.

After updating, reconnect your MCP client to load the new tool schema.

Releasing

VERSION=0.4.10 ./scripts/release.sh --publish

The script checks the package (npm ci, build, tests, npm run smoke:package), bumps the version, points the document pins at it, commits and tags, packs the tarball with its checksum, creates the GitHub release, updates the formula in robin-bially/homebrew-tap and finally waits until the npm registry serves the new version. Without --publish it only prepares the artifacts in .build/releases; --dry-run checks the prerequisites, --draft creates a draft release and --force tolerates a dirty tree. The tap is cloned temporarily when TAP_DIR is not set, so a fresh checkout is enough.

Publishing to npm happens in .github/workflows/publish.yml through trusted publishing once the GitHub release is published, so the script itself needs no npm credentials. The workflow requires a trusted publisher for search-rotation on npmjs.com that points at this repository and publish.yml.

The same workflow registers the version in the official MCP Registry from server.json. Distribution & listings tracks every channel, who keeps it current, and what each one still needs.

Learn more

Client setup · Operations & configuration (DE) · Distribution & listings · Releases · CI · MIT license

search-rotation

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Quick start

npm

Homebrew

Pinned release from GitHub

What you get

MCP tools

Search time filters

Provider support and rotation

Releasing

Learn more