For agents
Serendipity is built to be queried by agents, not just people. A read-only MCP (Model Context Protocol) endpoint is live at https://aadhar.sh/serendipity/mcp. Point any MCP client at it (Streamable-HTTP transport, JSON-RPC over POST) and ask "what events are good, and who's going." Public data only: no auth, no writes, and never private contact details.
Tools
list_events (when, rsvp, q, limit)Events in the pool with a head count + an RSVP tier. By default returns only events a contributor actually RSVP'd to / hosts (the ones with rosters), plus a count of browsed-but-not-RSVP'd events hidden; rsvp:"all" includes those (first-class first), rsvp:"discovered" returns only them.
get_event (id)One event in full: description, hosts, the guest list (who's going), contributors.
search_people (q, limit)Find people by name; returns role/company/socials and their events split into going_to and been_to.
list_contributorsThe people feeding the pool: a label, an id prefix, and how many events each fed in.
contributor_events (contributor)One contributor's whole footprint (by cookie id, id prefix, or label), split into going_to and been_to.
frequent_people (when, limit)Who shows up across the most events (who you're seeing a lot), with an event count.
co_attendees (q, limit)Who one person crosses paths with most, with the shared event names. Pass your own name for "who am I seeing a lot".
connections (min_shared, limit)The tightest co-attendance pairs pool-wide (who's seeing who), with shared counts + event names.
shared_events (a, b)The events two named people both attended (did they cross paths, and where).
statsPool overview: event counts, distinct people, active contributors.
Connect
Add it to an MCP client config:
{
"mcpServers": {
"serendipity": { "url": "https://aadhar.sh/serendipity/mcp" }
}
}
It exposes exactly what the dashboard shows: event details and who's going, with names, roles, companies, and public social links. The email and phone columns behind the pool never leave the database.