# DrinkedIn Night Out (remote · ai.drinkedin.net)

Plans walkable 2-4 stop nights out between officially validated venues. No sign-in.

- Trust score: 76/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ai.drinkedin.net`: 76/100 (this document), [markdown](https://verifymcp.io/servers/haim-barad-drinkedin-night-out/mcp-night-out.md), [page](https://verifymcp.io/servers/haim-barad-drinkedin-night-out/mcp-night-out)

## Channel facts

- Endpoint: `https://ai.drinkedin.net/mcp/night-out`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1542 tokens (~771/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DrinkedIn Night Out MCP server?

DrinkedIn Night Out is a hosted endpoint at https://ai.drinkedin.net/mcp/night-out, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http haim-barad-drinkedin-night-out 'https://ai.drinkedin.net/mcp/night-out'
```

### Cursor

```json
{
  "mcpServers": {
    "haim-barad-drinkedin-night-out": {
      "url": "https://ai.drinkedin.net/mcp/night-out"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "haim-barad-drinkedin-night-out": {
      "type": "http",
      "url": "https://ai.drinkedin.net/mcp/night-out"
    }
  }
}
```

### Codex

```toml
[mcp_servers.haim-barad-drinkedin-night-out]
url = "https://ai.drinkedin.net/mcp/night-out"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "haim-barad-drinkedin-night-out": {
      "type": "remote",
      "url": "https://ai.drinkedin.net/mcp/night-out",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add haim-barad-drinkedin-night-out --url 'https://ai.drinkedin.net/mcp/night-out' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  haim-barad-drinkedin-night-out:
    url: "https://ai.drinkedin.net/mcp/night-out"
```

### Netclaw

```json
{
  "McpServers": {
    "haim-barad-drinkedin-night-out": {
      "Transport": "http",
      "Url": "https://ai.drinkedin.net/mcp/night-out"
    }
  }
}
```

### Vellum

```bash
assistant mcp add haim-barad-drinkedin-night-out -t streamable-http -u 'https://ai.drinkedin.net/mcp/night-out'
```

### Other

```json
{
  "mcpServers": {
    "haim-barad-drinkedin-night-out": {
      "type": "http",
      "url": "https://ai.drinkedin.net/mcp/night-out"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 76, 0)

- [security] Tool “drinkedin_get_guide” rewrote its description, which is the text the model reads
- [security] Tool “drinkedin_plan_night_out” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-11-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 74, +4)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “drinkedin_get_guide” rewrote its description, which is the text the model reads
- [security] Tool “drinkedin_plan_night_out” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 499 → 743
- [functional improvement] Tool coverage: 71% → 100%
- [functional improvement] Tool “drinkedin_get_guide” now declares an output schema
- [functional improvement] Tool “drinkedin_plan_night_out” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “address”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “budget”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “city”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “language”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “latitude”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “longitude”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “max_walk_m”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “near”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “stops”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “style”

### 2026-10-28 (score 70, +3)

- [security improvement] HSTS header: fail → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “drinkedin_plan_night_out” rewrote its description, which is the text the model reads

### 2026-10-27 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 66, +1)

- [security] Tool “drinkedin_get_guide” rewrote its description, which is the text the model reads
- [security] Tool “drinkedin_plan_night_out” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 428 → 483
- [functional improvement] Tool coverage: 65% → 71%
- [functional] Schema quality: fair → good
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “budget”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “party_size”
- [cosmetic] “drinkedin_plan_night_out” reworded the description of “start_time”

### 2026-10-24 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (2)

### `drinkedin_plan_night_out` (~1189 tokens)

Plan a night out

Plans a walkable 2-4 stop night out around a place, using only venues DrinkedIn has validated against an official licence register or premises census, or the venue's own site, and books nothing. Free. Side effect: saves the planned route (public venue data only, 30 days) for its share link, returned as route.plan_url; the user's location is not saved. Input, most reliable first: a point as latitude and longitude; with no coordinates, a free-text street address or landmark in address, geocoded to one point and planned like coordinates (coordinates win if both are given); or a place name in city, with region or country, which plans only when it identifies one place. A typed address is sent to a public geocoding service (OpenStreetMap Nominatim), which ranks matches and does not confirm them; the reply's geocoded_as and geocoded_point say what it matched. A name several places share returns needs_input with labelled choices, each with a place_key for the next call; the tool does not pick between them. Optional: stops, max_walk_m, style, vibes (both listed by drinkedin_get_guide, which is not a required first call) and exclude_ids to swap a stop. Output: a status (planned, partial, needs_input or no_coverage), the ordered stops with name, address, kind of place and walking minutes, meaning and say_to_owner lines, next steps and notices. Walking times are estimates (straight line x 1.3). Opening hours and prices are not known and not asserted; each stop sets hours_verified and prices_verified, both false unless that stop names a verification source, and points to the venue for them (its own site when the stop has own_site). Plans are for adults of legal drinking age where they are. legal_drinking_age is the age on record for the venues' country, or null; no reply states an age as a number. A reply contains only the stops the tool returns, with no venues, details or place names from other sources.

Input parameters:

- `address` (string): Optional free text: a street address, a landmark or the name of an area, used only when no latitude and longitude are given. It is geocoded to one point and planned like coordinates. The address is s…
- `budget` (object): Accepted but ignored: not used to filter or sort the route; prices are not known. The reply adds the notice budget_not_verifiable.
- `city` (string): City name. With region or country it tells apart places that share the name.
- `country` (string): Country name or code; narrows a name several places share.
- `exclude_ids` (array): venue_id values to leave out, to swap a stop.
- `language` (string): Reply language code, such as 'en'. Replies are in English; any other code is accepted, and a reply that reaches the route search then carries the notice language_fallback_en.
- `latitude` (number): Latitude of the start point in decimal degrees, -90 to 90, sent with longitude. A point needs no lookup and wins over address, city and place_key. A value out of range, or a latitude without a longit…
- `longitude` (number): Longitude of the start point in decimal degrees, -180 to 180, sent with latitude. A value out of range, or a longitude without a latitude, returns needs_input.
- `max_walk_m` (integer): Longest walk allowed for each leg, in metres, the walk from the start to the first stop included; walking distance is estimated as the straight line x 1.3. 200 to 2000. Default 900, or the style's ow…
- `near` (string): A label for what the point stands for, e.g. 'near me' or an area name. Echoed back as the route's 'near_as_given'; it is the caller's label, not DrinkedIn's, and does not change the plan.
- `party_size` (integer): Informational only: does not change the route.
- `place_key` (string): From a needs_input answer: names exactly one of its choices.
- `region` (string): State or province, a name or a code such as a two-letter US state code; narrows a name several places share.
- `start_time` (string): Local HH:MM. Informational only: does not change the route.
- `stops` (integer): Number of stops wanted, 2 to 4. Default 3, or the style's own default when a style is given (listed by drinkedin_get_guide). A value outside the range is clamped to it. When too few validated venues…
- `style` (string): Optional route shape, from the styles in drinkedin_get_guide. It limits which kinds of place the route uses and sets the default stops and walking limit; explicit stops and max_walk_m win. It says no…
- `vibes` (array): From drinkedin_get_guide. Vibes we cannot verify yet are noted, not applied.

Output parameters:

- `choices` (array): On needs_input: labelled choices (places, styles or vibes).
- `coverage` (object): How many validated venues are around the start.
- `geocoded_as` (string): What a typed address matched.
- `geocoded_point` (object): The point a typed address was geocoded to.
- `hours_verified` (boolean): False unless a verification source is named on the reply. Opening hours are not verified.
- `largest_places` (array): Some places with validated venues; not a ranking.
- `legal_drinking_age` (integer|null): On a planned or partial reply: the age on record for the venues' country when every stop shares one known age, otherwise null. Spoken copy stays of legal drinking age where they are.
- `meaning` (string): What the result means, for the assistant.
- `meta` (object): Versions of the tool and of the drinkedin-night-out skill these replies suit, and the server's docs page.
- `needs` (array): On needs_input: what is missing.
- `next` (array): Ready follow-up calls: tool, why and args.
- `notices` (array): Notice codes, such as legal_drinking_age and hours_unverified.
- `prices_verified` (boolean): False unless a verification source is named on the reply. Prices are not verified.
- `retry_after_seconds` (number): On an error reply when the planner is busy: seconds to wait.
- `route` (object): On planned and partial: the ordered stops and the walks between them.
- `say_to_owner` (string): A plain sentence for the person.
- `status` (string): planned, partial (fewer stops than asked), needs_input, no_coverage, or error (a fault on DrinkedIn's side, flagged isError).
- `style_applied` (string): The style id the route follows.

### `drinkedin_get_guide` (~103 tokens)

Night-out guide

Returns reference data for the night-out planner: some places with validated venues (not a ranking and not a coverage claim; places, styles and vibes are built from the venues on record and the planner's style and vibe tables), supported vibes, route styles, notes on addresses and place names, and the relay rules this server publishes (validated venues only, no invented details, legal drinking age where they are). Not required before a plan. Read-only and free.

Output parameters:

- `address` (string)
- `largest_places` (array): Some places with validated venues, from the venue register; not a ranking and not a coverage claim. Same list as places.
- `meaning` (string): What the result means, for the assistant.
- `meta` (object): Versions of the tool and of the drinkedin-night-out skill these replies suit, and the server's docs page.
- `next` (array): Ready follow-up calls: tool, why and args.
- `notices` (array): Notice codes, such as legal_drinking_age and hours_unverified.
- `place_names` (string)
- `places` (array): The supported places: the same list as largest_places, built from the venues on record, not from a fixed example list.
- `retry_after_seconds` (number): On an error reply when the planner is busy: seconds to wait.
- `rules` (array): The rules this server publishes for relaying a plan.
- `say_to_owner` (string): A plain sentence for the person.
- `status` (string): ok, or error on a fault.
- `styles` (array): Route styles: id, label, summary, default stops and walking limit.
- `styles_note` (string)
- `vibes` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/haim-barad-drinkedin-night-out/mcp-night-out#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 67
- 2026-10-26: 66
- 2026-10-25: 66
- 2026-10-24: 65
- 2026-10-23: 64

## Common questions

### What is the DrinkedIn Night Out MCP server?

DrinkedIn Night Out is an MCP server listed in the public MCP registry as io.github.haim-barad/drinkedin-night-out. Plans walkable 2-4 stop nights out between officially validated venues. No sign-in. This page covers its hosted endpoint (https://ai.drinkedin.net/mcp/night-out).

### Is the DrinkedIn Night Out MCP server safe to use?

DrinkedIn Night Out scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DrinkedIn Night Out MCP server expose?

DrinkedIn Night Out exposes 2 tools: drinkedin_plan_night_out, drinkedin_get_guide. Their descriptions and schemas cost roughly 1,292 tokens of context every time the server is loaded.

### Does the DrinkedIn Night Out MCP server require authentication?

No. We connected to DrinkedIn Night Out without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DrinkedIn Night Out MCP server still maintained?

DrinkedIn Night Out is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ai.drinkedin.net/mcp/night-out
- Repository: https://github.com/haim-barad/drinkedin-night-out
- Website: https://drinkedin.net/docs/night-out
- Changelog RSS feed: https://verifymcp.io/servers/haim-barad-drinkedin-night-out/mcp-night-out.xml
- Changelog JSON feed: https://verifymcp.io/servers/haim-barad-drinkedin-night-out/mcp-night-out.json
- HTML version of this page: https://verifymcp.io/servers/haim-barad-drinkedin-night-out/mcp-night-out