Skip to content

PourWire MCP server

com.pourwire/pourwirepourwire.comstreamable-httpv1.0.4Scanned

Restaurants and bars about to open in 22 US metros, from new liquor license filings. No key needed.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the PourWire MCP server can do

The PourWire MCP server is published by pourwire.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: metro_stats), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (search_openings and metro_stats).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.4.

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
  • metro_statsSummary stats for a metro: tracked venues, new this week, sources.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
    Summary stats for a metro: tracked venues, new this week, sources.

    Annotations the server declares

    • title: Metro opening stats
    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • search_openingsSearch upcoming restaurant/bar openings in a metro (pre-opening signals from liquor license & permit filings).Reads text others writeNo findings

    Why it is in this group

    • The name "search_openings" says "search": a word for reading.

    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
    Search upcoming restaurant/bar openings in a metro (pre-opening signals from liquor license & permit filings). Returns venues with estimated opening window, owner and evidence trail. Without an API key: the public tier (every filing, block-level address, no owner contacts), each with a link to its page.

    Annotations the server declares

    • title: Search upcoming restaurant and bar openings
    • readOnlyHint: true
    • openWorldHint: true

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 write2
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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Oct 23, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pourwire.com/mcp: tools/list returned 2 tools to an anonymous client, including metro_stats (write)

    What this check looks for

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.

  1. Tools2 changed.~2 changedView diff
  2. Tools2 changed.~2 changedView diff
  3. Tools2 changed.~2 changedView diff
  4. Tools2 changed.~2 changedView diff
    • Changed:metro_statsChanges thingstitleinputSchemaannotations
    • Changed:search_openingsOnly readstitledescriptioninputSchemaannotations

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http pourwire https://pourwire.com/mcp
claude mcp add --transport http pourwire https://pourwire.com/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pourwire__search_openings"
    ],
    "ask": [
      "mcp__pourwire__metro_stats"
    ],
    "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 pourwire. Review it before you use it.

Capability tags behind 2 rules
  • mcp__pourwire__search_openings untrusted-input
  • mcp__pourwire__metro_stats 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://radar.anlyon.com/api/v1/servers/com.pourwire/pourwire/verify?hash=94d7693ce56cfee57e551427251aedfb386c59ffbdb3a29d9c2daf5aa3167449" | jq -e '.changed == false'

Pinned hash 94d7693ce56c, from Nov 20, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.pourwire/pourwire/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.pourwire/pourwire
[![Anlyon Radar](https://radar.anlyon.com/badge/com.pourwire/pourwire.svg)](https://radar.anlyon.com/servers/com.pourwire/pourwire)

Source: MCP Registry. Synced Nov 6, 2026, 18:17 UTC.

PourWire MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the PourWire MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the PourWire MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PourWire MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the PourWire MCP server have?

2 tools: 1 write, 1 read. metro_stats and search_openings.

Does the PourWire MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the PourWire MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the PourWire MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.