portage-ucp-client

by tomtom87io.github.tomtom87/portage-portage-ucp-clientv0.7.0

Every other portage-ucp gem lets a Ruby program expose a commerce backend to agents (server side). This gem is the other direction: connect to somebody else's /.well-known/ucp manifest, or drive your own Adapter directly, and place an order as the client. Three transports behind one interface (loopback over an in-process Adapter, stdio, Streamable HTTP) — callers never know which they got. Depends only on portage-ucp, the mcp gem's client half, and faraday (the HTTP transport's backend); no adapter gem is a dependency.

No known advisories
MIT

Uptime

Not checked. It lists no endpoint our checks can reach: https on port 443 or 8443.

How we check

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-ucp-client (`io.github.tomtom87/portage-portage-ucp-client`)

Its page: https://plug.directory/servers/io.github.tomtom87/portage-portage-ucp-client

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