# packagecloud MCP by usefulapi (remote · packagecloud.usefulapi.io)

Read packagecloud repos, packages, versions and download stats; create repos, promote and delete.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `packagecloud.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-packagecloud/packagecloud.md), [page](https://verifymcp.io/servers/io-usefulapi-packagecloud/packagecloud)

## Channel facts

- Endpoint: `https://packagecloud.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2843 tokens (~157/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the packagecloud MCP by usefulapi server?

packagecloud MCP by usefulapi is a hosted endpoint at https://packagecloud.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-packagecloud 'https://packagecloud.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-packagecloud": {
      "url": "https://packagecloud.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-packagecloud": {
      "type": "http",
      "url": "https://packagecloud.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-packagecloud]
url = "https://packagecloud.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-packagecloud": {
      "type": "remote",
      "url": "https://packagecloud.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-packagecloud --url 'https://packagecloud.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-packagecloud:
    url: "https://packagecloud.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-packagecloud": {
      "Transport": "http",
      "Url": "https://packagecloud.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-packagecloud -t streamable-http -u 'https://packagecloud.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-packagecloud": {
      "type": "http",
      "url": "https://packagecloud.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (18)

### `packagecloud_list_repositories` (~132 tokens)

List repositories

List the package repositories of this account: name, fqname (user/repo, used by every other tool), privacy, package count and last push. include_collaborations adds repositories you collaborate on. GET /repos.

Input parameters:

- `include_collaborations` (boolean): Also list repositories that belong to other accounts but that you collaborate on.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).

### `packagecloud_get_repository` (~62 tokens)

Get repository

One repository: name, fqname, url, privacy, package count and last push. GET /repos/{user}/{repo}.

Input parameters:

- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_create_repository` (~73 tokens)

Create repository

WRITE: create a new, empty package repository in this account (the plan limits how many private ones). Returns the URL of the new repository. POST /repos.

Input parameters:

- `name` (string, required): The new repository name.
- `private` (boolean): Create a private repository (default true) or a public one.

### `packagecloud_list_distributions` (~50 tokens)

List distributions

The Linux distributions and versions packagecloud supports for deb, dsc and rpm packages, with their index_name (for example ubuntu / jammy) and numeric version ids. GET /distributions.

### `packagecloud_list_packages` (~158 tokens)

List all packages

List every package file in a repository (not grouped), newest data first as the server orders it. Each item carries ready-made URLs: package_url, versions_url, downloads_*_url, promote_url, destroy_url and download_url; pass those to the other package tools. Paged. GET /repos/{user}/{repo}/packages.json.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_search_packages` (~261 tokens)

Search packages

Search a repository by package file name. An empty q returns every package. filter limits by type (rpms, debs, dscs, gem, python, node); dist (for example ubuntu or el/6) overrides filter; arch applies to Alpine/RPM/Debian only. Items carry the same ready-made URLs as list_packages. Paged. GET /repos/{user}/{repo}/search.json.

Input parameters:

- `arch` (string): Architecture, for example x86_64, arm64 or amd64.
- `dist` (string): Distribution, for example ubuntu or el/6.
- `filter` (string): Package type: rpms, debs, dscs, gem, python or node. Ignored when dist is given.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).
- `q` (string): Part of the package file name; empty returns all packages.
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_list_package_groups` (~262 tokens)

List package names by type

List the packages of one type, grouped by name with a versions_count and a versions_url (pass that to packagecloud_list_package_versions). Narrow by distro, then version, then arch (each needs the previous one; '*' matches any). Examples: type rpm; type deb + distro ubuntu + version jammy + arch amd64; type gem. GET /repos/{user}/{repo}/packages/{type}[/{distro}[/{version}[/{arch}]]].json.

Input parameters:

- `arch` (string): Architecture, for example amd64 or x86_64.
- `distro` (string): Distribution name, for example ubuntu or el.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).
- `type` (string, required): Package type: deb, rpm, gem, python, node, java, helm, alpine ...
- `version` (string): Distribution version name, for example jammy or 7.

### `packagecloud_get_package` (~86 tokens)

Get package

Details of one package file (size, checksums, dependencies, licenses, download counts and its other URLs). Pass the package_url of an item from list_packages, search_packages or list_package_versions. GET {package_url}.

Input parameters:

- `package_url` (string, required): The package_url of a package object, exactly as returned by the API (a /api/v1/repos/... path).

### `packagecloud_list_package_versions` (~142 tokens)

List package versions

All versions of one package name (for deb/rpm: per distro, version and architecture). Pass the versions_url of an item from list_package_groups, or derive it from a package object. Paged. GET {versions_url}.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).
- `versions_url` (string, required): The versions_url of a package object, exactly as returned by the API (a /api/v1/repos/... path).

### `packagecloud_get_package_downloads` (~320 tokens)

Get package download stats

Download statistics of one package version: a count, a time series, or (repository owners only) the detail of each download. Default range is the last 7 days; pass start_date=19700101Z for all time. Pass the package_url of the package; Java and generic files have no download stats. GET {package_url minus .json}/stats/downloads/{count|detail|series/<interval>}.json.

Input parameters:

- `end_date` (string): An ISO 8601 date, for example 20260101Z or 2026-01-01.
- `interval` (string): Series interval, "daily" (default) or "weekly".
- `kind` (string): count = total, series = per interval, detail = one record per download (owners only).
- `package_url` (string, required): The package_url of a package object, exactly as returned by the API (a /api/v1/repos/... path).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).
- `source` (string): Only downloads from the "web" or the "cli".
- `start_date` (string): An ISO 8601 date, for example 20260101Z or 2026-01-01.
- `user_agent` (string): Only downloads whose user agent equals this.

### `packagecloud_get_repository_installs` (~348 tokens)

Get repository install stats

How often a repository was installed (set up on a machine): a count, a time series, or (owners only) the detail of each install, optionally for one distro or distro+version. Default range is the last 7 days; pass start_date=19700101Z for all time. GET /repos/{user}/{repo}/stats/installs[/{distro}[/{version}]]/{count|detail|series/<interval>}.json.

Input parameters:

- `distro` (string): Only installs on this distribution, for example ubuntu.
- `end_date` (string): An ISO 8601 date, for example 20260101Z or 2026-01-01.
- `interval` (string): Series interval, "daily" (default) or "weekly".
- `kind` (string): count = total, series = per interval, detail = one record per install (owners only; includes host names and IP addresses).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page (default 30; the server caps it at its own Max-Per-Page).
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).
- `start_date` (string): An ISO 8601 date, for example 20260101Z or 2026-01-01.
- `user_agent` (string): Only downloads whose user agent equals this.
- `version` (string): Only installs on this distribution version, for example jammy (needs distro).

### `packagecloud_list_gpg_keys` (~79 tokens)

List GPG keys

The GPG keys of a repository (repository signing keys and package signing keys): name, fingerprint, type and the public key download URL. GET /repos/{user}/{repo}/gpg_keys.json.

Input parameters:

- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_get_gpg_key` (~107 tokens)

Get GPG key

One GPG key of a repository by its key name (as returned by list_gpg_keys, for example user-repo-85D7FBF915DFCBC6.pub.gpg). GET /repos/{user}/{repo}/gpg_keys/{keyname}.json.

Input parameters:

- `key_name` (string, required): The GPG key name.
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_get_readme` (~56 tokens)

Get repository README

The Markdown README of a repository. GET /repos/{user}/{repo}/readme.json.

Input parameters:

- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_create_readme` (~82 tokens)

Create repository README

WRITE: create the Markdown README of a repository. Use append_readme to add to an existing one. POST /repos/{user}/{repo}/readme.json.

Input parameters:

- `body` (string, required): The README, as Markdown.
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_append_readme` (~91 tokens)

Append to repository README

WRITE: append Markdown to the existing README of a repository (existing text is kept). Not idempotent: calling it twice appends twice. PATCH /repos/{user}/{repo}/readme.json.

Input parameters:

- `body` (string, required): Markdown to append to the README.
- `repository` (string, required): The repository as "user/repo" (the fqname returned by packagecloud_list_repositories).

### `packagecloud_promote_package` (~147 tokens)

Promote (move) package

WRITE, DESTRUCTIVE: MOVE a package file to another repository (for example staging -> production). It no longer exists in the source repository afterwards, and its download statistics are cleared. Pass the promote_url of the package object and the destination as user/repo. POST {promote_url}.

Input parameters:

- `destination` (string, required): The destination repository as "user/repo" (it must already exist).
- `promote_url` (string, required): The promote_url of a package object, exactly as returned by the API (a /api/v1/repos/... path).
- `scope` (string): Only for a scoped Node.js package: the scope including the @, for example @example.

### `packagecloud_delete_package` (~177 tokens)

Delete (yank) package

WRITE, DESTRUCTIVE AND IRREVERSIBLE: delete one package file from its repository (a gem is yanked). Clients that depend on it will break. Pass the destroy_url of the package object and repeat its file name (the last path segment, for example jake-1.0-2.el6.x86_64.rpm) as confirm_filename. DELETE {destroy_url}.

Input parameters:

- `confirm_filename` (string, required): The package file name, exactly as in the last segment of destroy_url (the 'filename' field of the package).
- `destroy_url` (string, required): The destroy_url of a package object, exactly as returned by the API (a /api/v1/repos/... path).
- `scope` (string): Only for a scoped Node.js package: the scope including the @, for example @example.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-packagecloud/packagecloud#diagnostics

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the packagecloud MCP by usefulapi server?

packagecloud MCP by usefulapi is listed in the public MCP registry as io.usefulapi/packagecloud. Read packagecloud repos, packages, versions and download stats; create repos, promote and delete. This page covers its hosted endpoint (https://packagecloud.usefulapi.io/mcp).

### Is the packagecloud MCP by usefulapi server safe to use?

packagecloud MCP by usefulapi scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the packagecloud MCP by usefulapi server expose?

packagecloud MCP by usefulapi exposes 18 tools: packagecloud_list_repositories, packagecloud_get_repository, packagecloud_create_repository, packagecloud_list_distributions, packagecloud_list_packages, and 13 more. Their descriptions and schemas cost roughly 2,633 tokens of context every time the server is loaded.

### Does the packagecloud MCP by usefulapi server require authentication?

Yes. packagecloud MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the packagecloud MCP by usefulapi server still maintained?

packagecloud MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://packagecloud.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/packagecloud/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-packagecloud/packagecloud.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-packagecloud/packagecloud.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-packagecloud/packagecloud