search-rotation
NPM · SEARCH-ROTATION
MCP server for web search and page extraction across the free tiers of several providers
Available components
Last scanned (19 hours ago)
Scores higher than 93% of npm servers
Category Search and Retrieval
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to localfoundry/search-rotation-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 383 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 21 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/search-rotation@0.4.10
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | localfoundry/search-rotation-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/localfoundry/search-rotation-mcp/.github/workflows/publish.yml@refs/tags/v0.4.10 |
| Rekor log index | 2968548883 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c66be7f593ed7137f6fb0a1983880199aadc129e5579e161178188f2436c3b29a72f3a33bf4d7c96738b8fb86b89a52689d369d37f23283ae18365797 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
engine_status Engine Status ~49
Read engine configuration, per-capability authentication requirements, local usage and quota sources. This is not a live health check. Historical errors do not prove a current failure; disabled engines are not necessarily missing credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fetch_url Fetch URL ~54
Fetch a web page and return its content as markdown. Rotates across extraction providers (Jina Reader, Firecrawl, Parallel, Tavily, Exa) with failover.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL to fetch |
No output schema declared.
No examples provided.
open_dashboard Open Dashboard ~42
Open the local dashboard (API keys, engine order and toggles, quota view) in a web browser. Use when the user wants to configure engines or check quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
web_search Web Search ~238
Web search with automatic round-robin across multiple free search APIs (Tavily, Firecrawl, Parallel, Exa, Google PSE, DuckDuckGo) including transparent failover. Returns numbered results with title, URL, snippet and publication date when available. Time filters restrict rotation and failover to compatible providers; never silently dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date YYYY-MM-DD (through this date, subject to provider boundary semantics). Cannot combine with timeRange. |
| engine | string | – | Preferred engine id; failover to the other engines stays active |
| numResults | integer | – | Optional result count (1–20). Omit to use the dashboard setting: a custom count or the provider default. |
| query | string | yes | Search query |
| startDate | string | – | Start date YYYY-MM-DD. May be used alone or with endDate; cannot combine with timeRange. |
| timeRange | string | – | Relative UTC date window: day=1, week=7, month=30, year=365 days through today. Cannot combine with startDate/endDate; day precision, not rolling hours. |
No output schema declared.
No examples provided.
How do I install the search-rotation MCP server?
search-rotation runs locally as an npm package, launched with npx -y search-rotation. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · search-rotation
claude mcp add localfoundry-search-rotation -- npx -y search-rotation
What is the search-rotation MCP server?
search-rotation is an MCP server listed in the public MCP registry as io.github.localfoundry/search-rotation. MCP server for web search and page extraction across the free tiers of several providers. This page covers its npm package (search-rotation).
Is the search-rotation MCP server safe to use?
search-rotation scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 search-rotation MCP server expose?
search-rotation exposes 4 tools: web_search, fetch_url, engine_status, open_dashboard. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Is the search-rotation MCP server still maintained?
search-rotation is still listed as active in the MCP registry. We last reached this channel on 4 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 search-rotation MCP server under?
search-rotation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.