DrinkedIn Night Out
io.github.haim-barad/drinkedin-night-outhaim-baradstreamable-httpv1.0.0Scanned
Read-only planner for walkable 2-4 stop nights out between validated, licensed venues. No sign-in.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 1Claude Code: ask
drinkedin_plan_night_outPlan a walkable 2-4 stop night out around a place using only venues DrinkedIn has validated against the venue's own site or an official register.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Plan a walkable 2-4 stop night out around a place using only venues DrinkedIn has validated against the venue's own site or an official register. Read-only and free. The most reliable input is a point: give latitude and longitude. Choose it from the user's context, never from a default: 'near me' is the user's current location; an area the user names (a neighbourhood or district) is the centre of that area; for a trip the user is planning, look up the destination they name (use its country to pick the right place) and give its coordinates. If the context holds no location, ask the user. With no coordinates, a free-text address or landmark in address also works: it is geocoded to one point and planned like coordinates (coordinates win if both are given). The text is sent to a public geocoding service (OpenStreetMap Nominatim), which ranks matches and does not confirm them: the reply's geocoded_as says what it matched, so confirm that with the person when the text was ambiguous. A place name also works when it identifies one place, so give it with its country or region; a name several places share returns needs_input with labelled choices: pick the one that fits the user's context and call again with its place_key or coordinates. Never guess between choices. Walking times are estimates (straight line x 1.3). Hours and prices are never asserted: tell the user to check the venue's own site. Always include the legal drinking age notice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
- title: Plan a night out
Only reads 1Show 1 read-only tool
drinkedin_get_guideHow to use the night-out planner: the largest places, supported vibes, and the rules to follow when relaying a plan (validated venues only, no invented details, legal drinking age)…No findings
Why it is in this group
- The name "drinkedin_get_guide" says "get": a word for reading.
Description, as the server wrote it How to use the night-out planner: the largest places, supported vibes, and the rules to follow when relaying a plan (validated venues only, no invented details, legal drinking age). Read-only and free.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Night-out guide
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http drinkedin-night-out https://ai.drinkedin.net/mcp/night-outclaude mcp add --transport http drinkedin-night-out https://ai.drinkedin.net/mcp/night-outRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__drinkedin-night-out__drinkedin_get_guide"
],
"ask": [
"mcp__drinkedin-night-out__drinkedin_plan_night_out"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as drinkedin-night-out. Review it before you use it.
Capability tags behind 1 rule
- mcp__drinkedin-night-out__drinkedin_plan_night_out untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.haim-barad/drinkedin-night-out/verify?hash=169c4fec44723893bfd1e2793158b47f151912f3b48eb80db357d39fe32cfd4a" | jq -e '.changed == false'Pinned hash 169c4fec4472, from Oct 23, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.haim-barad/drinkedin-night-out/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.haim-barad/drinkedin-night-out)Source: MCP Registry · repository. Synced Oct 23, 2026, 08:17 UTC.