releasedapp

8 registries, one place to watch them.

Most teams don't live in one ecosystem. A Python service with a Rust binary, and a lockfile full of npm — all of it releases on its own schedule.

Language / ecosystemOfficial registryPackage manager

JavaScript / TypeScriptnpm registrynpm · pnpm · yarn

PythonPyPIpip · uv · poetry

Rustcrates.iocargo

C# / .NETNuGetdotnet · nuget

PHPPackagistcomposer

RubyRubyGemsgem · bundler

Dart / Flutterpub.devpub

Elixir / ErlangHex.pmmix · rebar3

Three minutes to set up, then it runs without you.

Connect the agent you already code with, or use the browser. Either way there is nothing to install inside your network and no token to paste anywhere.

Sign in with GitHub

That is the whole account. We keep your name and email, nothing else.

Hand over a manifest

Your agent sends the package.json, pyproject.toml or Cargo.toml it is already looking at — or you paste one. Direct dependencies only, with the versions you are on.

Ask what changed

The agent asks on your behalf, whenever you like. Want to be told without asking? Turn on the email digest in Settings — it only arrives on days something shipped.

Works with the agent you already use.

releasedapp is an MCP server. Add it once; the first time the agent connects it opens a tab where you sign in with GitHub and approve. From then on “what changed in my dependencies?” is a question it can answer.

Claude Code

one command

claude mcp add --transport http releasedapp https://releasedapp.org/mcp

Then /mcp in a session to finish the sign-in.

Cursor

mcp.json

{ "mcpServers": { "releasedapp": {
    "url": "https://releasedapp.org/mcp" } } }

Cursor shows “Needs login” on the server; click it.

Codex

two commands

codex mcp add releasedapp --url https://releasedapp.org/mcp
codex mcp login releasedapp

Or the same in ~/.codex/config.toml.

Antigravity

mcp_config.json

{ "mcpServers": { "releasedapp": {
    "serverUrl": "https://releasedapp.org/mcp" } } }

Manage MCP Servers → View raw config.

Anything else that speaks MCP over HTTP with OAuth works too. Setup for each, and what the agent can do →

The dashboard, for when a question isn't enough.

The agent tells you what changed. The board tells you what that means: which dependency has drifted two majors behind, which one hasn't shipped in eight months, which one is suddenly releasing every other day.

Nothing here needs an install, a token, or an agent inside your network. It is a web page behind your GitHub login.

releasedapp PackagesDigestSettings

27Watched

4Shipped today

2Majors behind

6Quiet 90d+

Package	Version	Last release
vitenpm	5.4.2 → 6.0.0	today
tokiocrates.io	1.38.0 → 1.39.0	today
railsrubygems	7.1.3 → 7.2.0	today
requestspypi	2.32.3 — current	241 days
momentnpm	2.29.4 — current	613 days

What this deliberately isn't.

Everything below is a decision, not a missing feature.

No email unless you askOff by default. Turn it on and it arrives once a day — and only on days something you watch shipped. An empty email is still an interruption.
No paid tierThere is one plan. You are on it. The code is MIT-licensed if you would rather run your own.
Nothing pings youNo push, no badges, no Slack bot. Your agent asks when you ask; the dashboard is there when you want it, or never.
No transitive dependency noiseWe watch what you listed, not the 800 packages underneath it.
Nothing to installNo scanner inside your network, no token to paste. Your coding agent connects over MCP with one line of config; the dashboard needs only a browser.
No repository accessSigning in with GitHub reads your name and email. We never ask for your code.

Start with one package.

Add more when you feel like it. Nothing breaks if you never come back.