search-rotation 0.4.10 → 0.4.11

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Robin Bially (LocalFoundry)
+Copyright (c) 2026 Robin Bially
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -5,7 +5,7 @@
 
 **One MCP server for web search and page extraction across multiple providers.**
 
-Built by [Robin Bially](https://github.com/localfoundry) under the LocalFoundry label.
+Built by [Robin Bially](https://github.com/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.
 
@@ -25,23 +25,25 @@ 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.
+`npx -y search-rotation` with no arguments. The server is also listed in the
+[official MCP Registry](https://registry.modelcontextprotocol.io/?q=io.github.robin-bially%2Fsearch-rotation)
+as `io.github.robin-bially/search-rotation`.
 
 ### Homebrew
 
 ```sh
-brew install localfoundry/tap/search-rotation
+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
-[LocalFoundry tap](https://github.com/localfoundry/homebrew-tap) for upgrades and details.
+[Homebrew tap](https://github.com/robin-bially/homebrew-tap) for upgrades and details.
 
 ### Pinned release from GitHub
 
 ```sh
-npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.10
+npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.11
 ```
 
 Use this when you want a fixed version instead of the current npm release.
@@ -117,13 +119,15 @@ After updating, reconnect your MCP client to load the new tool schema.
 ## Releasing
 
 ```sh
-VERSION=0.4.9 ./scripts/release.sh --publish
+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 `localfoundry/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.
+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`](.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](docs/distribution.md) tracks every channel, who keeps it current, and what each one still needs.
+
 ## Learn more
 
-[Client setup](docs/clients.md) · [Operations & configuration (DE)](docs/operations.md) · [Releases](https://github.com/localfoundry/search-rotation-mcp/releases) · [CI](https://github.com/localfoundry/search-rotation-mcp/actions/workflows/ci.yml) · [MIT license](LICENSE)
+[Client setup](docs/clients.md) · [Operations & configuration (DE)](docs/operations.md) · [Distribution & listings](docs/distribution.md) · [Releases](https://github.com/robin-bially/search-rotation-mcp/releases) · [CI](https://github.com/robin-bially/search-rotation-mcp/actions/workflows/ci.yml) · [MIT license](LICENSE)

package/docs/clients.md

@@ -5,7 +5,7 @@
 ## Homebrew installation
 
 ```sh
-brew install localfoundry/tap/search-rotation
+brew install robin-bially/tap/search-rotation
 ```
 
 Homebrew installs Node.js automatically. Set your MCP client's command to
@@ -74,14 +74,14 @@ Add this entry under `mcp.servers`:
 
 ## Local install or release archive
 
-If installed locally, use `search-rotation` as the command. A prebuilt archive is also available under [GitHub Releases](https://github.com/localfoundry/search-rotation-mcp/releases/latest):
+If installed locally, use `search-rotation` as the command. A prebuilt archive is also available under [GitHub Releases](https://github.com/robin-bially/search-rotation-mcp/releases/latest):
 
 ```sh
-npm install -g ./search-rotation-0.4.10.tgz
+npm install -g ./search-rotation-0.4.11.tgz
 ```
 
 npx installs the package from the npm registry, so no Git access is required. The pinned
-`github:localfoundry/search-rotation-mcp#vX` form from the README needs `--allow-git=all`
+`github:robin-bially/search-rotation-mcp#vX` form from the README needs `--allow-git=all`
 instead, because npm 12 resolves Git dependencies only when explicitly allowed.
 
 For remote HTTP access, authentication and advanced settings, see the [operations guide (German)](operations.md).

package/docs/distribution.md

@@ -0,0 +1,53 @@
+# Distribution and listings
+
+Where search-rotation is published or listed, who keeps each channel current, and
+what still needs attention. Snapshot: 2026-09-26, after the account rename from `localfoundry` to `robin-bially` and the 0.4.11 release.
+
+## Channels
+
+| Channel | Entry | Kept current by | State |
+| --- | --- | --- | --- |
+| npm | `search-rotation` | release workflow, trusted publishing | 0.4.10; 0.4.11 blocked by the stale trusted publisher, see below |
+| Homebrew | `brew install robin-bially/tap/search-rotation` | release script writes the formula | 0.4.11 |
+| Official MCP Registry | `io.github.robin-bially/search-rotation` | release workflow, GitHub OIDC | blocked: the registry verifies the npm package, so it needs 0.4.11 on npm first; `io.github.localfoundry/search-rotation` stays live at 0.4.10 because the registry has no unpublish |
+| GitHub releases | tag, tarball and checksum | release script | v0.4.11 |
+| Glama | [directory entry](https://glama.ai/mcp/servers/robin-bially/search-rotation-mcp), rated A | Glama indexes the repository on its own | listed; the account rename is pending a re-crawl |
+| mcpservers.org | [submission](https://mcpservers.org/de/submit) from 2026-09-26 | reviewed by the site | in review, up to two weeks |
+| PulseMCP | — | ingests the official registry | submissions paused, not listed yet |
+| [punkpeye/awesome-mcp-servers](https://github.com/punkpeye/awesome-mcp-servers/pull/15171) | Search & Data Extraction | maintainers | pull request open, listing checks done |
+| [YuzeHao2023/Awesome-MCP-Servers](https://github.com/YuzeHao2023/Awesome-MCP-Servers/pull/550) | Search & Web | maintainers | pull request open |
+| [ever-works/awesome-mcp-servers](https://github.com/ever-works/awesome-mcp-servers/pull/188) | Web Search | maintainers | pull request open |
+
+Channels that build on the official registry follow a release by themselves, so a
+release needs no manual work for them.
+
+## What a release updates
+
+`VERSION=x.y.z ./scripts/release.sh --publish` runs the checks, bumps the version,
+commits and tags, creates the GitHub release, packs the tarball with its checksum,
+writes the formula in `robin-bially/homebrew-tap`, and waits until npm serves the
+new version. The published release triggers
+[`.github/workflows/publish.yml`](../.github/workflows/publish.yml), which pushes
+the package to npm with provenance and then registers the same version in the
+official MCP Registry from `server.json` and the `mcpName` field of
+`package.json`.
+
+Four details are easy to forget:
+
+- `server.json` and `mcpName` must name the same server; `test/registry-manifest.test.ts` fails when they drift apart.
+- The registry limits `description` to 100 characters.
+- The registry verifies ownership through the published npm package, so a manifest can only be registered once that version exists on npm. The workflow skips an already published version, which makes a re-run safe.
+- npm trusted publishing is bound to one repository. The entry for `search-rotation` still named `localfoundry/search-rotation-mcp`, so the 0.4.11 publish failed with `404 Not Found - PUT https://registry.npmjs.org/search-rotation`. Repair with `npm trust github search-rotation --file publish.yml --repo robin-bially/search-rotation-mcp --allow-publish`, then revoke the stale entry (`npm trust list search-rotation`, `npm trust revoke search-rotation --id=<id>`) and re-run the publish workflow. Both commands ask for a one-time password in the browser. The old owner name is free again, so the stale entry also lets a stranger publish to this package.
+
+## Recurring checks
+
+- After a release: `npm view search-rotation version` and the [registry entry](https://registry.modelcontextprotocol.io/?q=io.github.robin-bially%2Fsearch-rotation) should both show the new version. The release script already waits for npm, but a failed publish workflow leaves the release and the tap ahead of npm, as with 0.4.11.
+- Dependency and tap maintenance runs outside this repository on a biweekly schedule.
+- The GitHub account moved from `localfoundry` to `robin-bially` on 2026-09-26. The registry has no unpublish, so the entry `io.github.localfoundry/search-rotation` stays frozen at 0.4.10 while the next release adds `io.github.robin-bially/search-rotation`. The old handle is free again, so anything still pointing there can end up at a different account.
+- Open externally: mcpservers.org reviews the submission, PulseMCP is paused, the three list pull requests wait for their maintainers, and Glama re-crawls repositories at its own pace.
+
+## Deliberately not used
+
+Directories that require a new account before a submission (Glama's own form,
+mcp.so) are skipped. The Glama listing exists because Glama indexes public GitHub
+repositories without a submission; it picked up the repository rename by itself.

package/docs/release-notes.md

@@ -1,3 +1,22 @@
+## v0.4.11 — Distribution under the robin-bially account
+
+The GitHub account moved from `localfoundry` to `robin-bially`, so every distribution
+path follows: the Homebrew tap is `robin-bially/tap`, the official MCP Registry
+namespace becomes `io.github.robin-bially/search-rotation`, and the npm metadata now
+points at the renamed repository. The package itself is unchanged, so there is no
+behaviour change and no configuration migration.
+
+```sh
+brew update && brew upgrade robin-bially/tap/search-rotation
+```
+
+Or run the pinned GitHub version:
+
+```sh
+npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.11
+```
+
+
 ## v0.4.10 — npm distribution and MCP Registry metadata
 
 The package now ships through npm as well, so `npx -y search-rotation` installs the
@@ -6,13 +25,13 @@ trusted publishing, and `mcpName` plus `server.json` carry the metadata for the
 official MCP Registry.
 
 ```sh
-brew update && brew upgrade localfoundry/tap/search-rotation
+brew update && brew upgrade robin-bially/tap/search-rotation
 ```
 
 Or run the pinned GitHub version:
 
 ```sh
-npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.10
+npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.10
 ```
 
 
@@ -21,13 +40,13 @@ npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.10
 Routine maintenance release: the Node type definitions move to 26.6.3. No behaviour change and no configuration migration. The GitHub release page now shows only the notes for the current version instead of the whole changelog.
 
 ```sh
-brew update && brew upgrade localfoundry/tap/search-rotation
+brew update && brew upgrade robin-bially/tap/search-rotation
 ```
 
 Or run the pinned GitHub version:
 
 ```sh
-npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.9
+npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.9
 ```
 
 
@@ -36,13 +55,13 @@ npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.9
 Routine maintenance release: the MCP SDK moves to 1.30.1, Hono to 4.13.9, Zod to 4.6.5, tsx to 4.23.15 and the Node type definitions to 26.6.2, together with the matching transitive updates (jose, proxy-addr, ip-address, fast-uri, undici-types). No behaviour change and no configuration migration.
 
 ```sh
-brew update && brew upgrade localfoundry/tap/search-rotation
+brew update && brew upgrade robin-bially/tap/search-rotation
 ```
 
 Or run the pinned GitHub version:
 
 ```sh
-npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.8
+npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.8
 ```
 
 
@@ -60,11 +79,11 @@ Engine call counts are now visible with or without an API key. Search, fetch, an
 No configuration migration is required. Reconnect MCP clients after updating.
 
 ```sh
-brew update && brew upgrade localfoundry/tap/search-rotation
+brew update && brew upgrade robin-bially/tap/search-rotation
 ```
 
 Or run the pinned GitHub version:
 
 ```sh
-npx -y --allow-git=all github:localfoundry/search-rotation-mcp#v0.4.7
+npx -y --allow-git=all github:robin-bially/search-rotation-mcp#v0.4.7
 ```

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "search-rotation",
-  "version": "0.4.10",
-  "mcpName": "io.github.localfoundry/search-rotation",
+  "version": "0.4.11",
+  "mcpName": "io.github.robin-bially/search-rotation",
   "description": "Round-robin web search over the free tiers of multiple search APIs (Tavily, Firecrawl, Parallel, Exa, Google PSE, Jina, DuckDuckGo) as an MCP server — with a local dashboard for API keys, engine order/toggles and live quota status.",
   "type": "module",
   "license": "MIT",
   "author": {
     "name": "Robin Bially",
-    "url": "https://github.com/localfoundry"
+    "url": "https://github.com/robin-bially"
   },
   "bin": {
     "search-rotation": "dist/index.js"
@@ -57,10 +57,10 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/localfoundry/search-rotation-mcp.git"
+    "url": "git+https://github.com/robin-bially/search-rotation-mcp.git"
   },
-  "homepage": "https://github.com/localfoundry/search-rotation-mcp#readme",
+  "homepage": "https://github.com/robin-bially/search-rotation-mcp#readme",
   "bugs": {
-    "url": "https://github.com/localfoundry/search-rotation-mcp/issues"
+    "url": "https://github.com/robin-bially/search-rotation-mcp/issues"
   }
 }

package/static/index.html

@@ -3,7 +3,7 @@
 <head>
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width, initial-scale=1">
-  <title>search-rotation · LocalFoundry</title>
+  <title>search-rotation</title>
   <meta name="theme-color" content="#0a0c12">
   <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Cdefs%3E%3ClinearGradient id='g' x1='0' y1='0' x2='1' y2='1'%3E%3Cstop offset='0' stop-color='%238b7cf7'/%3E%3Cstop offset='1' stop-color='%234dd8e6'/%3E%3C/linearGradient%3E%3C/defs%3E%3Ccircle cx='16' cy='16' r='14' fill='none' stroke='url(%23g)' stroke-width='3.5' stroke-dasharray='66 22' stroke-linecap='round'/%3E%3Ccircle cx='16' cy='16' r='4.5' fill='url(%23g)'/%3E%3C/svg%3E">
   <link rel="stylesheet" href="/style.css">
@@ -83,7 +83,7 @@
   <main class="view" id="view" aria-live="polite"></main>
 
   <footer class="footer">
-    <span><strong>LocalFoundry</strong> · <span data-i18n="footer.text"></span></span>
+    <span><strong>Robin Bially</strong> · <span data-i18n="footer.text"></span></span>
     <span class="footer-meta"><code id="configpath"></code></span>
   </footer>