Skip to content

Remove retired servers and fix Octocode provenance - #1071

Merged
JAORMX merged 3 commits into
mainfrom
remove-retired-mcp-servers
Oct 8, 2026
Merged

JAORMX merged 3 commits into
mainfrom
remove-retired-mcp-servers

Conversation

@danbarr

@danbarr danbarr commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Remove seven MCP server packages that upstream has retired or superseded, so Dockyard stops building and publishing new images for them. Also correct Octocode packaging metadata and record its published source commit.

Also remove Browserbase's package-specific security notes and replace its Taskfile scan examples with Playwright.

For Octocode, correct the stale image comment from 12.0.0 to the packaged 19.1.0, update the repository URL to bgauryy/octocode, and replace mutable main with npm 19.1.0's published gitHead (24ada10033de01215be62f53cd9293fbf36ca72a). The installed amd64 image package was verified as 19.1.0. This resolves the repository-mismatch warning and records a stable source reference; upstream still advertises registry signatures rather than SLSA build provenance. Remove the now-redundant minimatch and protobufjs overrides: a fresh npm dependency resolution of octocode-mcp@19.1.0 without overrides selects minimatch@10.2.6 and contains no protobufjs.

Keep Notion: its local implementation still accepts changes despite the README's unsupported status. AWS skill packaging is tracked separately in #481. No replacement server specs are added: most replacements are hosted or IDE-integrated; Hex-Rays requires IDA 9.4+ with idalib and needs a separate integration assessment.

Validation: git diff --check passed. dockhand verify-provenance -c npx/octocode-mcp/spec.yaml -v passed without a repository-mismatch warning (status: SIGNATURES). Confirmed the source package version at the recorded commit is 19.1.0 and that npm metadata names that commit as its gitHead. Confirmed the container workflow discovers existing spec files dynamically. Dockerfile generation passed after removing the overrides, and a fresh lockfile-only npm resolution was checked with lifecycle scripts disabled. No runtime code changed, and no container builds or scans were run. Existing published images are not deleted by this PR.

Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
@toolhive-release-app

toolhive-release-app Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

🔒 MCP Security Scan Results

✅ octocode-mcp

  • Status: Passed
  • Tools scanned: 9
  • Result: No security issues detected

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
@danbarr danbarr changed the title Remove retired and superseded MCP servers Remove retired servers and fix Octocode provenance Oct 7, 2026
@toolhive-release-app

This comment was marked as outdated.

Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
@JAORMX
JAORMX merged commit f28823a into main Oct 8, 2026
15 checks passed
@JAORMX
JAORMX deleted the remove-retired-mcp-servers branch October 8, 2026 04:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants