io.github.tschoonj/repology-mcp-server
OCI · GHCR.IO/TSCHOONJ/REPOLOGY-MCP-SERVER:0.1.1 · 2 COMPONENTS · SCANNED AUG 3
MCP server that provides access to Repology package repository data
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency-health data not yet available.Unverified
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 317 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 594 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
oci · ghcr.io/tschoonj/repology-mcp-server:0.1.1
claude mcp add tschoonj-repology-mcp-server -- docker run --rm -i ghcr.io/tschoonj/repology-mcp-server:0.1.1
codex mcp add tschoonj-repology-mcp-server -- docker run --rm -i ghcr.io/tschoonj/repology-mcp-server:0.1.1
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tschoonj-repology-mcp-server": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/tschoonj/repology-mcp-server:0.1.1"
],
"enabled": true
}
}
} mcp_servers:
tschoonj-repology-mcp-server:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/tschoonj/repology-mcp-server:0.1.1"] {
"mcpServers": {
"tschoonj-repology-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/tschoonj/repology-mcp-server:0.1.1"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 31 Jul 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +23
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Schema quality: pass functional
- 26 Jul 26 11
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed oci/ghcr.io/tschoonj/repology-mcp-server:0.1.1
Provenance none
Ecosystem: oci · Outcome: none
Reason: no_attestation
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_maintainer_problems ~91
Get problems reported for packages maintained by a specific person. Args: maintainer: Maintainer email address repository: Optional repository to limit results to start_from: Project name to start from for pagination Returns: JSON formatted list of problems for the maintainer
| Name | Type | Req | Description |
|---|---|---|---|
| maintainer | string | yes | — |
| repository | — | — | — |
| start_from | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_project ~72
Get detailed information about a specific project. Args: project_name: Exact name of the project to retrieve repository: Optional repository filter to show only packages from that repository Returns: JSON formatted list of packages for the project
| Name | Type | Req | Description |
|---|---|---|---|
| project_name | string | yes | — |
| repository | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
get_repository_problems ~77
Get problems reported for a specific repository. Args: repository: Repository name (e.g., "freebsd", "debian") start_from: Project name to start from for pagination Returns: JSON formatted list of problems for the repository
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | — |
| start_from | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
list_projects ~218
List projects with optional filtering. Args: start_from: Project name to start listing from limit: Maximum number of results (default: 10, max: 200) maintainer: Filter by maintainer email category: Filter by category inrepo: Filter by repository presence notinrepo: Filter by repository absence repos: Filter by number of repositories (e.g., "1", "5-", "-5", "2-7") families: Filter by number of repository families newest: Show only newest projects outdated: Show only outdated projects problematic: Show only problematic projects Returns: JSON formatted dictionary of projects and their packages
| Name | Type | Req | Description |
|---|---|---|---|
| category | — | — | — |
| families | — | — | — |
| inrepo | — | — | — |
| limit | integer | — | — |
| maintainer | — | — | — |
| newest | — | — | — |
| notinrepo | — | — | — |
| outdated | — | — | — |
| problematic | — | — | — |
| repos | — | — | — |
| start_from | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.
search_projects ~136
Search for projects by name substring. Args: query: Search term to match against project names limit: Maximum number of results (default: 10, max: 100) maintainer: Optional maintainer email filter category: Optional category filter inrepo: Optional repository presence filter notinrepo: Optional repository absence filter Returns: JSON formatted list of matching projects with their packages
| Name | Type | Req | Description |
|---|---|---|---|
| category | — | — | — |
| inrepo | — | — | — |
| limit | integer | — | — |
| maintainer | — | — | — |
| notinrepo | — | — | — |
| query | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | — |
No examples provided.