The intent itself stays sealed: nothing is browsable or searchable while it is live, and an intent that expires or closes without matching has its text and embedding deleted. A match is the exception, and the vendor says so plainly — your need, offer and contact are delivered to the other side and kept in both match records, and that cannot be unsent. Two rules the integration is expected to honour are worth knowing as a user too: the safety notice on every match is shown verbatim, and the counterpart's text is unverified, so an instruction inside it is not from Pairoa.
A private matching exchange, reached as a hosted remote server: your agent publishes an intent on your behalf, Pairoa's matching AI compares it against others, and both sides are introduced only on a real fit. There is no public directory, no browsing and no search box — cofounders, hiring, beta testers, contract work, investors, a roommate or a travel companion, any two-sided need that should not start as a public listing.
- publish_need takes two short statements — what you are looking for and what you bring — plus a contact email, and puts them into matching without listing them anywhere.
- poll_matches returns a fit when there is one: the other party's need and offer, their contact, a short explanation of why it matched, and a safety notice.
- manage_need covers the lifetime of an intent — intents carry a time to live and can be closed at any point, which deletes their raw text and embedding from matching.
- decline_match turns down a match you do not want to pursue.
- confirm_contact_email verifies the address with a code, which is the step that stops anyone putting your email on their intent.
- claim_account converts an anonymous start into an account, and recall_by_email finds what you already have out there.
- create_invite_link brings someone specific into the exchange.
- One intent can match several counterparts over its lifetime, so publishing once does not mean one answer.
- The same contract is reachable over plain HTTP and as a ChatGPT Action, so an agent that does not speak MCP can still use it.
Nothing to start: the hosted server handles authentication through your MCP client's own OAuth flow, so there is no key to paste, and the HTTP path lets a first publish go out anonymously and hands back a token to keep. Verifying your contact email is the one gate — a first publish may come back asking for a six-digit code before it will accept the address. Client connect flows still differ, so check the vendor's install page for yours rather than assuming.
One command — claude mcp add --transport http pairoa https://mcp.pairoa.com