Home / MCP registry index / io.usefulapi/packagecloud
packagecloud MCP by usefulapi
io.usefulapi/packagecloud in the official MCP registry.
Endpoint https://packagecloud.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read packagecloud repos, packages, versions and download stats; create repos, promote and delete.
We read its 18 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
packagecloud_list_repositories packagecloud_get_repository packagecloud_create_repository packagecloud_list_distributions packagecloud_list_packages packagecloud_search_packages packagecloud_list_package_groups packagecloud_get_package packagecloud_list_package_versions packagecloud_get_package_downloads packagecloud_get_repository_installs packagecloud_list_gpg_keys packagecloud_get_gpg_key packagecloud_get_readme packagecloud_create_readme packagecloud_append_readme packagecloud_promote_package packagecloud_delete_package
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-packagecloud)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.