packagecloud MCP by usefulapi
REMOTE · PACKAGECLOUD.USEFULAPI.IO
Read packagecloud repos, packages, versions and download stats; create repos, promote and delete.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CI/CD and DevOps
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
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 17 Oct 2026 · Probed https://packagecloud.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of packagecloud.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://packagecloud.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://packagecloud.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://packagecloud.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://packagecloud.usefulapi.io/mcp |
| Authorisation server | https://packagecloud.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://packagecloud.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/packagecloud/ |
| http (plaintext) | http://packagecloud.usefulapi.io/mcp | Inconclusive | 302 | http://packagecloud.usefulapi.io/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
packagecloud_append_readme Append to repository README ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Markdown to append to the README. |
| repository | string | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_create_readme Create repository README ~82
WRITE: create the Markdown README of a repository. Use append_readme to add to an existing one. POST /repos/{user}/{repo}/readme.json.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The README, as Markdown. |
| repository | string | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_create_repository Create repository ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The new repository name. |
| private | boolean | – | Create a private repository (default true) or a public one. |
No output schema declared.
No examples provided.
packagecloud_delete_package Delete (yank) package ~177
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_filename | string | yes | The package file name, exactly as in the last segment of destroy_url (the 'filename' field of the package). |
| destroy_url | string | yes | 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. |
No output schema declared.
No examples provided.
packagecloud_get_gpg_key Get GPG key ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key_name | string | yes | The GPG key name. |
| repository | string | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_get_package Get package ~86
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| package_url | string | yes | The package_url of a package object, exactly as returned by the API (a /api/v1/repos/... path). |
No output schema declared.
No examples provided.
packagecloud_get_package_downloads Get package download stats ~320
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
packagecloud_get_readme Get repository README ~56
The Markdown README of a repository. GET /repos/{user}/{repo}/readme.json.
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_get_repository Get repository ~62
One repository: name, fqname, url, privacy, package count and last push. GET /repos/{user}/{repo}.
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_get_repository_installs Get repository install stats ~348
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
packagecloud_list_distributions List distributions ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
packagecloud_list_gpg_keys List GPG keys ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_list_package_groups List package names by type ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
| type | string | yes | Package type: deb, rpm, gem, python, node, java, helm, alpine ... |
| version | string | – | Distribution version name, for example jammy or 7. |
No output schema declared.
No examples provided.
packagecloud_list_package_versions List package versions ~142
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The versions_url of a package object, exactly as returned by the API (a /api/v1/repos/... path). |
No output schema declared.
No examples provided.
packagecloud_list_packages List all packages ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
packagecloud_list_repositories List repositories ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
packagecloud_promote_package Promote (move) package ~147
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The destination repository as "user/repo" (it must already exist). |
| promote_url | string | yes | 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. |
No output schema declared.
No examples provided.
packagecloud_search_packages Search packages ~261
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The repository as "user/repo" (the fqname returned by packagecloud_list_repositories). |
No output schema declared.
No examples provided.
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.
remote · packagecloud.usefulapi.io
claude mcp add --transport http io-usefulapi-packagecloud 'https://packagecloud.usefulapi.io/mcp'
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.