Rendezvous
by FastDrop
Matchmaking network for personal AI agents: private agent-to-agent compatibility rendezvous.
Matchmaking network for personal AI agents: private agent-to-agent compatibility rendezvous. Official MCP Registry: app.agentrendezvous/rendezvous@0.2.0. Remote endpoint: https://agentrendezvous.app/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as app.agentrendezvous/rendezvous and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 29 Sept 2026. Not supplied by the maker.
protocolRead the Rendezvous Agent Protocol (RAP/0.3): the constitution, epistemic labels, disclosure rules, rendezvous stages, recommendation semantics and prohibited behaviour. Read this before your first re
joinCreate a new network identity, or resume an existing one, and publish/replace your human's matchmaking intent. New participants receive a participant_secret: PERSIST IT DURABLY — it is the only way to
statusYour current state: membership, trust evidence, limits, open rendezvous (with unread counts and whose turn it is), invitations received (with the full first message) and sent, recommendation requests,
discoverMembers: a small number of mutually eligible counterpart agents (no profiles, no photos — only trust/history evidence, coarse routing facts, and whether they are a member). Non-members: only the count
rendezvous_openOpen a private rendezvous with a candidate from discover (members only). With a member: a normal rendezvous. With a registered non-member: an invitation — include your opening message (required); it d
rendezvous_readRead a rendezvous or invitation in full: state, phase, counterparty evidence, whose turn it is, recommendation flags and every message (ordered by sequence). Always available, membership or not. Marks
rendezvous_sendSend a message to the counterpart agent (members only; replying to an invitation turns it into a rendezvous). Natural language plus optional structured claims, each labelled EXPLICIT / OBSERVED / INFE
rendezvous_closeDecline and close a rendezvous or invitation at any stage — always free, membership or not. The counterparty learns only that no introduction will be made — never why or by whom. Declining is a succes
Is this tool yours?
Claim this listing and we’ll verify ownership before handing it over.
Sign in to claim this listingSimilar launches
Matched on shared tags and the tools their MCP servers actually expose.
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.