# find_meetup

Best meet-up airports for travellers from multiple origins, ranked by combined travel effort using the same scoring as the site. Origins can be weighted by traveller count. Scores are kilometre values, lower is better; optimize "score" and "total_distance" both rank by weighted total distance (the frontend default), "worst_case" by the longest single journey. Candidates everyone can reach always rank above candidates someone cannot. Route data only: no fares, no frequency or days-of-week data; non-scheduled legs are flagged with a kind field. The map link stores the query as an anonymous share code and reopens it in the site’s meet-up planner.

Agent View of the PolicyLayer registry record for `find_meetup`. HTML page: https://policylayer.com/tools/com-flywhereto-mcp/find-meetup

## Facts

- Tool: `find_meetup`
- Server: Fly Where To? (`https://flywhereto.com/api/mcp`) — https://policylayer.com/tools/com-flywhereto-mcp.md
- Homepage: https://github.com/https://flywhereto.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 7 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Candidates to return (default 5) |
| `origins` | array | yes | Where the travellers start; duplicates merge by summing travellers |
| `optimize` | string | no | Ranking objective (default "score") |
| `max_stops` | integer | no | Maximum stops per journey (default 0, nonstop only) |
| `allow_at_home` | boolean | no | Allow an origin airport as the meet-up point, that party stays home |
| `exclude_kinds` | array | no | Drop legs whose service kind is in this list, e.g. ["suspended"] |
| `same_alliance` | boolean | no | Require each journey to be flyable within one single airline alliance |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "find_meetup",
    "arguments": {
      "origins": []
    }
  }
}
```

## Why find_meetup is rated Low

Even though find_meetup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call find_meetup to retrieve information from Fly Where To? without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fly Where To?:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_meetup": {}
  }
}
```

## Other tools on Fly Where To? (7)

- `airline_routes` — Read — https://policylayer.com/tools/com-flywhereto-mcp/airline-routes.md
- `destinations_from` — Read — https://policylayer.com/tools/com-flywhereto-mcp/destinations-from.md
- `find_airport` — Read — https://policylayer.com/tools/com-flywhereto-mcp/find-airport.md
- `find_connections` — Read — https://policylayer.com/tools/com-flywhereto-mcp/find-connections.md
- `most_connected_airports` — Read — https://policylayer.com/tools/com-flywhereto-mcp/most-connected-airports.md
- `reachable_from` — Read — https://policylayer.com/tools/com-flywhereto-mcp/reachable-from.md
- `route_details` — Read — https://policylayer.com/tools/com-flywhereto-mcp/route-details.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-flywhereto-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-flywhereto-mcp