portage-cli
by tomtom87io.github.tomtom87/portage-portage-cliv0.15.0
Ships the `portage` executable. `portage buy <url>` tries native UCP discovery first (zero credentials, works on any store that's opted in), falls back to a portage-ucp-* platform adapter only when this process already has that platform's own credentials in env (i.e. it's your own store or one you're integrated with), and otherwise says so plainly — never scrapes or session-hijacks as an anonymous shopper. `portage find` covers the no-URL case: ask an allowlist, DuckDuckGo, Brave, or a Google Programmable Search engine which stores might sell something, keep the ones answering /.well-known/ucp, and search their catalogs — documented APIs only, no SERP scraping. Depends on portage-ucp (for platform detection via Resolver), portage-ucp-client (for the actual buy calls), and portage-ucp-journal (for `portage-console`'s read-only view of local purchase/transaction/order state); no single adapter gem is a hard dependency. Ranking, escalation and the spend-policy check use portage-ucp core's rules; portage-ucp-decision is optional and only the opt-in confidence gate needs it.
- No known advisories
- MIT
Uptime
Not checked. It lists no endpoint our checks can reach: https on port 443 or 8443.
This server lists no remote endpoint or package we can write a config for yet.
For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server portage-cli (`io.github.tomtom87/portage-portage-cli`)
Its page: https://plug.directory/servers/io.github.tomtom87/portage-portage-cli
plug.directory has no install config for this server: its listing names no remote endpoint and no package that starts over stdio from npm, PyPI or an OCI registry. Read the install steps in its own repository instead.
Known advisories
None known for its packages.
Checked 2026-10-28 against OSV.dev and deps.dev.
From RubyGems. Report a problem