Dependency Freshness Mcp

io.github.ArmigerousPublished by GitHub account Armigerousv0.0.2Updated Oct 24, 2026

npm & PyPI freshness for AI agents: latest version, deprecations, dated breaking-change diffs.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that gives an assistant npm and PyPI package freshness data: latest versions, deprecations, and dated breaking-change diffs.

What you can do
Look up the latest published version of npm and PyPI packages for an assistant's dependency checks. Surface deprecation notices for those packages. Retrieve dated breaking-change diffs so version jumps can be assessed. The manifest lists no individual tools, so exact operations are not documented.
When to use it
Useful when an assistant is reviewing or upgrading JavaScript or Python dependencies and needs current version, deprecation, and breaking-change information rather than relying on training data.
Requirements
A remote streamable HTTP endpoint hosted on Apify; no local package or runtime is needed. Authentication is required via OAuth. No environment variables or headers are declared.
Before you install
Access requires OAuth sign-in, so an account and its authorization are involved. Package lookups are sent to the third-party Apify-hosted endpoint. The manifest lists no tools, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open Dependency Freshness Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Armigerous%2Fdependency-freshness-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dependency-freshness": {
      "type": "http",
      "url": "https://peppy-weekend--dependency-freshness-mcp.apify.actor/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.0.2LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.