search-rotation 0.4.5

Automated dependency maintenance.

Build, regression and package checks passed on fresh runners.

Install: brew install localfoundry/tap/search-rotation

Source commit: 235bd70d88b684e0b7e7926f20c359a9bc8cc96a. Built by Robin Bially · Distributed through LocalFoundry.

search-rotation 0.4.4

Automated dependency maintenance.

Build, regression and package checks passed on fresh runners.

Install: brew install localfoundry/tap/search-rotation

Source commit: 7928e2aac70c0f097c52b248c00a578e90359eb1. Built by Robin Bially · Distributed through LocalFoundry.

search-rotation 0.4.3

Automated dependency maintenance.

Build, regression and package checks passed on fresh runners.

Install: brew install localfoundry/tap/search-rotation

Source commit: 89bf0d0f7e25277b29f9e9ea712ce23ecf23b8e9. Built by Robin Bially · Distributed through LocalFoundry.

v0.4.2

v0.4.2 — Developer attribution and LocalFoundry branding

search-rotation lives on Robin Bially’s GitHub profile, alongside the rest of his portfolio. LocalFoundry remains the shared tool brand.

• README and package metadata link directly to the developer and canonical source repository.
• GitHub installation examples keep the neutral LocalFoundry URL, which redirects to the personal repository. Keep the old organization repository path unused to preserve that redirect.
• No runtime or configuration changes. Git author, committer and tagger metadata use GitHub noreply addresses.

npx -y --allow-git=all github:localfoundry/search-rotation#v0.4.2

Alternatively, install the prebuilt search-rotation-0.4.2.tgz release asset and verify it with SHA256SUMS.
Reconnect each MCP client after updating.

Full Changelog: v0.4.1...v0.4.2

v0.4.1

v0.4.1 — LocalFoundry distribution

search-rotation is now distributed under the LocalFoundry umbrella.

• GitHub installation commands, documentation and package links use localfoundry/search-rotation.
• The package author and copyright attribution use LocalFoundry.
• Dashboard setup snippets pin the running server version instead of installing an unversioned branch.
• The MCP server name, executable, tools and configuration directory remain search-rotation; existing keys and history do not need migration.

Install or update

npx -y --allow-git=all github:localfoundry/search-rotation#v0.4.1

Alternatively, install the prebuilt search-rotation-0.4.1.tgz release asset and verify it with SHA256SUMS.
Reconnect the MCP server in each client after updating. Distribution is through GitHub; no npm account is required.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

v0.4.0 — Search time filters and compatible-provider rotation

Limit web searches to a relative period or explicit dates. Rotation and failover now select providers that support the requested filter and configured access mode, without silently falling back to an unfiltered search.

Added

• web_search parameters: timeRange (day, week, month, year), startDate, and endDate (YYYY-MM-DD). Invalid calendar dates, reversed bounds, and mixing relative and explicit filters are rejected before provider requests.
• Native date mapping for Tavily, Firecrawl, and Exa's direct API with a key. One-sided bounds use Tavily or keyed Exa; incompatible providers and access modes are skipped.
• Separate rotation cursors for compatible provider pools, preserving quota priorities, cooldowns, strict-free rules, and failover.
• Publication dates in search output when available, and the requested period in history.
• Updated README and English/German dashboard tool help, with examples and the provider support matrix.

Date semantics

Relative windows resolve once per request into UTC dates, from 1/7/30/365 days ago through today. They have day precision, not rolling-hour precision. Provider semantics differ: Tavily can filter publication or update dates, Exa uses estimated publication dates, and Firecrawl uses its search index's date interpretation. Exact boundary inclusion follows the provider.

Install or update

npx -y --allow-git=all github:RobinBially/search-rotation#v0.4.0

Alternatively, install the prebuilt search-rotation-0.4.0.tgz release asset and verify it with SHA256SUMS. Distribution is through GitHub; no npm account is required.

Reconnect the MCP server in each client after updating to load the new tool schema. Existing configuration, credentials, and history are retained. Searches without time arguments continue to use all otherwise eligible providers.

Validation: 197 automated tests; TypeScript build; package installation and MCP handshake with all four tools; independent subagent review of the diff and official provider parameter documentation. Provider requests are covered by mocked wire tests; live filtering behavior and exact date boundaries remain to be validated against real results.

Full Changelog: v0.3.3...v0.4.0

v0.3.3

v0.3.3 — Configurable result counts and clearer tool discovery

Choose a custom search result count or let each provider use its own default. Discover all four MCP tools in the dashboard and get clearer engine status information.

Added

• Dashboard setting for a custom result count (1–20) or Provider default. Explicit numResults tool arguments take precedence. Existing and fresh configurations retain 8 until changed.
• Provider-default mode omits the result-count parameter from upstream requests. Result counts can vary across rotation and failover; DuckDuckGo returns the results parsed from its HTML page, and Parallel hosted MCP uses its own result set.
• English/German MCP Tools dashboard tab with parameter explanations and copyable examples.

Improved

• engine_status returns structured facts and equivalent JSON text. Configuration, per-capability key requirements, historical errors, local usage and provider account balances are clearly separated. This is not a live health check.
• Provider icons are bundled locally, so dashboard logos no longer depend on external image requests.
• README screenshots automatically follow light/dark mode and now display the real provider logos. The capture script checks that logos loaded successfully.
• Firecrawl's omitted-count cost estimate uses its documented 10-result default (estimated 2 credits); explicit counts above 10 are estimated at 4 credits. Anonymous provider balances remain unknown.

Install or update

npx -y --allow-git=all github:RobinBially/search-rotation#v0.3.3

Alternatively, install the prebuilt search-rotation-0.3.3.tgz release asset and verify it with SHA256SUMS. Distribution is through GitHub; no npm account is required.

Reconnect the MCP server in each harness after updating. Configuration, credentials and history are retained. The status tool's text format has changed to JSON; integrations parsing the previous human-readable lines should use structuredContent or the new JSON text.

Validation: 186 automated tests; TypeScript build; package installation and MCP handshake; browser checks of settings persistence, provider/custom modes, and desktop/mobile layouts; regenerated light/dark screenshots.

Full Changelog: v0.3.2...v0.3.3

v0.3.2

v0.3.2 — Dashboard identity and MCP icons

This hotfix uses the existing dashboard logo consistently in the README and MCP server metadata.

• Added self-contained, theme-specific PNG icons to MCP initialization metadata. Icons work without a dashboard connection or external image host; display depends on client support.
• Added SVG and PNG logo assets, light/dark wordmarks, and a monochrome variant based on the original dashboard symbol.
• Updated the README branding and pinned installation examples to v0.3.2.

Install or update

npx -y --allow-git=all github:RobinBially/search-rotation#v0.3.2

Alternatively, install the prebuilt search-rotation-0.3.2.tgz release asset. Verify it with the included SHA256SUMS. No npm account is needed.

Reconnect the MCP server in each harness after updating to load the new version and icon metadata. Saved configuration, credentials, and history are retained.

Validation: 175 automated tests, TypeScript build, visual inspection of logo exports, and package installation with an MCP handshake and all four tools.

Full Changelog: v0.3.1...v0.3.2

v0.3.1

v0.3.1 — Keyless search and dashboard fixes

Tavily and Parallel now work without API keys for web search. Quota displays distinguish locally counted calls from provider balances, and dashboard layout and drag-and-drop bugs are fixed.

Added

• Tavily keyless search via its anonymous-access header, using our own client identity.
• Parallel keyless search through its hosted MCP endpoint, with cancellation and normalized results.
• Search-only capability reporting for anonymous Tavily/Parallel access. Fetch uses their direct APIs when a key is configured.
• Engine configuration reloads across harness processes sharing the same configuration directory.

Fixed

• Unknown quotas show local successful calls without invented caps or misleading 100% progress rings. Removed Exa's assumed 1,400-request allowance.
• Firecrawl's key badge reflects the configured credentials; remote balances are labeled as account balances rather than calendar-month quotas.
• Key-required engines without credentials are disabled. DuckDuckGo HTML is now opt-in.
• Responsive quota layouts, native drag-and-drop, readable disabled-engine forms, history empty states, and language/theme labels.
• English is now the default UI language; saved language preferences are preserved.
• Updated English README, actual dashboard screenshot, provider-access documentation and multi-harness/update guidance.

Install or update

npx -y --allow-git=all github:RobinBially/search-rotation#v0.3.1

Alternatively, install the prebuilt search-rotation-0.3.1.tgz asset. The release includes SHA256SUMS. Distribution is through GitHub; no npm account is required.

Reconnect the MCP server in each harness after updating. Existing processes keep running their previous code. Saved credentials and history are retained; explicitly disabled engines stay disabled, so enable Tavily/Parallel in the dashboard if an older configuration disabled them.

Validation: 174 automated tests, package installation/MCP handshake, live anonymous searches through both new adapters, and browser checks of dashboard interactions on desktop, tablet and mobile. Local page extraction is not included in this release.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

v0.3.0 — verlässliche Rotation und GitHub-Releases

Dieses Release korrigiert die Kontingent-Priorisierung und macht parallele MCP-Instanzen, den Token-Betrieb und die Fehlerbehandlung robuster.

Neu

• Getrennte Such-/Fetch-Rotation, Cooldowns mit Retry-After und Gesamtzeitlimit mit Abbruchweitergabe.
• Optionaler strikter Gratis-Modus mit Reservierung laufender Einheiten innerhalb eines Routers.
• Tages-/Monats-/Credit-/IP-Kontingente mit sichtbarer Quelle und Schätzstatus.
• GitHub Actions für Tests unter Node 20/22/24 sowie GitHub-Releases mit fertigem Paket und SHA-256-Prüfsumme. Kein npm-Konto nötig.

Behoben

• Erschöpfte Engines umgehen nicht mehr die Quota-Priorität.
• Prozessübergreifende Sperren verhindern verlorene Verbrauchszähler und Verlaufseinträge.
• Dashboard-Login mit Session-Cookie; keine langlebigen Tokens in URLs oder Logs. Host-/Origin-Schutz für die HTTP-Schnittstellen.
• Korrekte DDG-Snippets, zuverlässiges Drag-and-drop und getrennte Search-/Fetch-Tests im Dashboard.
• Alle Regressionstests sind Teil des Standard-Testlaufs; keine übersprungenen Bugtests.

Installation

npx -y --allow-git=all github:RobinBially/search-rotation#v0.3.0

Alternativ das fertig gebaute search-rotation-0.3.0.tgz aus diesem Release installieren. npm/npx dienen nur als Paketwerkzeuge; ein npm-Account und npm-Publish sind nicht erforderlich.

Update-Hinweise

Vorhandene Config- und Verlaufsdateien bleiben erhalten. Alte Serverprozesse vor dem Update beenden, damit alle Instanzen die neuen Dateisperren verwenden. Im Token-Betrieb erfolgt die Browser-Anmeldung nun über /login; ?token=… entfällt. Token- und Portänderungen erfordern einen Neustart. Details und Grenzen des Gratis-Modus stehen in der README und in docs/operations.md.

Full Changelog: v0.2.0...v0.3.0