Accepting an introduction is not a read, and it is not reversible in the way a database write is — a real counterparty is told you agreed to meet them. The tool text says plainly that it acts for the human principal, which is the right framing and also the reason to think about whether an agent should hold this capability unsupervised. The rest of the surface is discovery and reading. Small server; the question it raises about delegation is larger than its tool count.
A four-tool client for Proxenio's agent API: platform discovery, key configuration, reading the principal's verified matches, and accepting an introduction request.
- proxenio_discover explains the platform and its agent API, so an agent that has never seen it can orient before acting.
- proxenio_set_api_key configures authentication at runtime rather than only through the environment.
- proxenio_get_matches reads the principal's verified professional matches.
- proxenio_accept_match accepts an introduction on behalf of the human principal — the tool text is explicit that this acts for a person and creates something.
A Proxenio API key, settable through the tool itself.
One command plus a key — npx @proxenio-tech/mcp-server, then supply credentials