Repology Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Repology: package versions across many software repositories.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that connects an assistant to Repology, the service tracking package versions across many software repositories.

What you can do
Gives an assistant access to Repology data on package versions across many software repositories, so it can look up how a package is versioned in different repositories. The manifest lists no tools, so the exact operations are not documented here. It runs as a local process on the user's machine over stdio.
When to use it
Useful when you need to compare package versions across distributions or repositories, for example to check whether a package is up to date in a given repository.
Requirements
A local runtime able to run the npm package repology-mcp (Node.js) and a desktop MCP client, since it is stdio-only and not web-executable. No authentication, environment variables or headers are declared.
Before you install
No credentials, write actions or third-party data sharing are shown in the input. The tool list is undocumented, so confirm what it queries before relying on it.

Installation

In SourceWeft

  1. Open Repology Mcp in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.