brewery-mcp

MCPcommunity
v1.0.2UnknownMITUpdated 3d agonpmGitHub

Open Brewery DB: search breweries, details, random. Keyless.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
8Downloads/wk
3d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.0.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv1.0.2 · todayHow well does this scan work?
EvalsNone
IndexedOct 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev1.0.2 · 10h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_breweriesSearch breweries on one specific field. Returns names, types, addresses, websites and ids.

Search breweries on one specific field. Returns names, types, addresses, websites and ids.

No input schema was published for this tool.

search_all_breweriesFree-text search across every brewery field — name, city, state, country, postal code and website — for when you do not know which field the text is in.

Free-text search across every brewery field — name, city, state, country, postal code and website — for when you do not know which field the text is in.

No input schema was published for this tool.

find_breweriesList breweries matching structured filters — city, state, country, type and postal code — optionally sorted by name, city, state or type. Use it for questions like 'micro breweries in Vermont'.

List breweries matching structured filters — city, state, country, type and postal code — optionally sorted by name, city, state or type. Use it for questions like 'micro breweries in Vermont'.

No input schema was published for this tool.

get_breweryFull details for one brewery by its id, including address, coordinates and contact info.

Full details for one brewery by its id, including address, coordinates and contact info.

No input schema was published for this tool.

random_breweryA random brewery from the directory, useful for discovery and examples.

A random brewery from the directory, useful for discovery and examples.

No input schema was published for this tool.

brewery_statsDirectory totals from Open Brewery DB broken down by country, brewery type and state/region. Good for market sizing and picking valid filter values.

Directory totals from Open Brewery DB broken down by country, brewery type and state/region. Good for market sizing and picking valid filter values.

No input schema was published for this tool.

autocomplete_breweriesType-ahead suggestions for a partial brewery name, with the id needed by get_brewery and the address fields.

Type-ahead suggestions for a partial brewery name, with the id needed by get_brewery and the address fields.

No input schema was published for this tool.

random_breweriesA batch of random breweries in one call, useful for sampling the directory or building a shortlist.

A batch of random breweries in one call, useful for sampling the directory or building a shortlist.

No input schema was published for this tool.

breweries_by_idsFetch up to 10 breweries by id in one call — the batch lookup for a list of ids collected from earlier results.

Fetch up to 10 breweries by id in one call — the batch lookup for a list of ids collected from earlier results.

No input schema was published for this tool.

nearest_breweriesBreweries closest to a latitude and longitude, ranked by great-circle distance. Open Brewery DB has no radius filter, so this scans a catalogue sample and reports how much it looked at.

Breweries closest to a latitude and longitude, ranked by great-circle distance. Open Brewery DB has no radius filter, so this scans a catalogue sample and reports how much it looked at.

No input schema was published for this tool.

record_coverageData-quality audit of the Open Brewery DB directory: how many records carry coordinates, phone, website, street address, city and type, and which countries have the weakest coordinate coverage.

Data-quality audit of the Open Brewery DB directory: how many records carry coordinates, phone, website, street address, city and type, and which countries have the weakest coordinate coverage.

No input schema was published for this tool.

types_by_regionWhich brewery types appear in which country, with counts and share, across a catalogue sample. Optionally filter to one country.

Which brewery types appear in which country, with counts and share, across a catalogue sample. Optionally filter to one country.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Open Brewery DB: search breweries, details, random. Keyless.

Keywords
mcpbeerbreweriescraft-beertravel
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-19 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in travel & booking