StillShipping MCP

tech.thecompoundv0.1.0Updated Oct 5, 2026

StillShipping: Check whether a developer tool is still maintained.

VerifiedSTDIODesktop onlyDeveloper Tools Web Search & Scraping

Overview

AI-generated overview

Lets an assistant check whether a developer tool or dependency is still actively maintained before recommending it.

What it does: StillShipping exposes a single tool, check_project_maintenance, which takes an optional project query and limit. It reports maintenance signals for a developer tool: the last release, the last commit, and whether the project reads as dead. The intended use is to run it before recommending a dependency.
When to use it: Use it when an assistant is about to suggest, add, or upgrade a third-party library or developer tool and you want a quick maintenance check first. It suits dependency review and avoiding abandoned packages.
Requirements: Runs locally as an npm package (stillshipping-mcp) over stdio, typically launched with npx; a Node.js runtime is needed. No API key, signup, or environment variables are declared. It can also serve streamable HTTP on a local port.

Before you install

The server is desktop-only and not web-executable. It queries an external service about named projects, so the project names you check leave your machine. It only reads maintenance data; no write, send, or delete actions are described.

Installation

In SourceWeft

Open StillShipping MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README