INDIVIDUAL MCP TOOL

connections

The tightest co-attendance pairs in the whole pool (who's seeing who): pairs of people who keep turning up at the same events, with the shared count and the shared event names.

aadhar.shnone authenticationAvailability not checked

LIVE ENDPOINT

https://aadhar.sh/serendipity/mcp

No auth detected

Connect to this endpoint to inspect the live schema for connections and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

aadhar.sh

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.serendipity]
url = "https://aadhar.sh/serendipity/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "serendipity": {
      "type": "http",
      "url": "https://aadhar.sh/serendipity/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: serendipity
Remote MCP URL: https://aadhar.sh/serendipity/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "serendipity": {
      "url": "https://aadhar.sh/serendipity/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "serendipity": {
      "type": "http",
      "url": "https://aadhar.sh/serendipity/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "serendipity",
  "transport": "streamable-http",
  "url": "https://aadhar.sh/serendipity/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

list_events — List events in the Serendipity pool, each with a head count of who's going and an RSVP tier.
get_event — Full detail for one event by id: description, time, location, Luma link, hosts, the guest list (who's going, with role/company/socials when known), and which contributors added it.
search_people — Search people across all events by name.
list_contributors — List the contributors feeding the pool (the people who synced a Luma feed): their label, an 8-char id prefix, and how many events each has fed in.
contributor_events — Given a contributor (their cookie id / user_key, an id prefix, or their label), return every event they fed into the pool, split into going_to (upcoming) and been_to (past).
frequent_people — The people who show up across the most events in the pool (who you're seeing a lot), each with an event count.
co_attendees — Given a person by name, who they cross paths with most: the people most often at the same events, with a shared-event count and the names of those shared events.
shared_events — Given two people by name, the events they both attended (did these two cross paths, and where).