How do I install agent-bev?

Install agent-bev in your harness: MCP — git clone https://github.com/agent-bev/bev-door. Full step-by-step guidance is on the HOL plugin page.

How do I install agent-bev in MCP?

To install agent-bev in MCP, start with git clone https://github.com/agent-bev/bev-door. The complete step-by-step install guide for MCP is on the HOL plugin page.

Who publishes agent-bev?

agent-bev is published by ai.agent-bev and listed on HOL.

agent-bev

ai.agent-bev/bev-door · v0.2.5 · MCP server

by ai.agent-bevScan grade: AcceptableOfficial MCP registry · source scanned

The world's largest agentic B2B hub for beer, wine and spirits. Powered by CUVEE. Trade only.

Install Source Claim this MCP server

Follow0

Trust ScoreNot rated Security scan76 Components1

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is agent-bev a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

1 MCP server

Before you install

Sign-in: Not declared
Declared access: Not declared
License: Not declared

Check before relying on it

1 medium finding from the scan. See the evidence
The publisher has not verified ownership on HOL.
No license declared in the manifest.

What is agent-bev?

agent-bev is a published mcp server plugin for AI coding agents in the MCP ecosystem, developed by ai.agent-bev and distributed through the HOL AI plugin registry. The world's largest agentic B2B hub for beer, wine and spirits. Powered by CUVEE. Trade only.

Canonical slug: ai.agent-bev/bev-door
Version: v0.2.5 · updated Sep 30, 2026
Open data: entity.json (JSON-LD)

Registry snapshot

Repository: https://github.com/agent-bev/bev-door
Homepage: https://agent-bev.ai
Canonical profile: https://hol.org/registry/plugins/ai.agent-bev%2Fbev-door
Owner verification: Not verified
Scanner: HOL plugin scanner
Security result: Needs review
Digest verified: No

Trust and security

Provenance

Plugin root: .
Source repo: https://github.com/agent-bev/bev-door
Source commit: fd680c8e5794…
Publisher verified: No
Owner verified: Not owner verified

Security posture

See how the Trust Score is computed

Needs review

Security result

Security score

High findings

Provider: codex-plugin-scanner
Grade: C · Acceptable
Version: 3.24.2

cisco-mcp-scanner: skipped

Security

13/16

9 checks

Operational Security

0/6

5 checks

Best Practices

6/6

4 checks

Code Quality

10/10

2 checks

Published advisories

None matched in OSV, checked 2026-10-29. This covers published advisories only, not problems nobody has reported.

OSV is matched against the exact package versions this listing names.

Findings

mediumoperational-securityDEPENDENCY_LOCKFILE_MISSING

package.json is present without a corresponding lockfile or pinned dependency snapshot.

Commit a lockfile or use fully pinned requirements for reproducible dependency resolution.

lowsecuritySECURITY_MD_MISSING

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowoperational-securityDEPENDABOT_MISSING

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs

Clone the repository

shell

2
Register the server in your MCP client
Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.
3
Verify the server
Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "source": "official-mcp-registry",
  "evidenceState": "scanned_source",
  "registryName": "ai.agent-bev/bev-door",
  "publishedAt": "2026-09-30T02:38:24.149981Z",
  "packages": [
    {
      "registryType": "npm",
      "identifier": "@agent-bev/mcp-server",
      "version": "0.2.5",
      "transport": "stdio",
      "requiredEnvironment": []
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://mcp.bev-buyer.ai/mcp"
    }
  ],
  "sourceScannedAt": "2026-10-30T00:07:31.486Z",
  "sourceScanCommit": "fd680c8e579464cca628d2e3eed41443ca50d7e9"
}

File inventory

File inventory is unavailable for this plugin right now.

agent-bev — Frequently asked questions

What is agent-bev?: agent-bev is an AI plugin in the HOL registry. The world's largest agentic B2B hub for beer, wine and spirits. Powered by CUVEE. Trade only.
How do I install agent-bev?: Install agent-bev in your harness: MCP — git clone https://github.com/agent-bev/bev-door. Full step-by-step guidance is on the HOL plugin page.
How do I install agent-bev in MCP?: To install agent-bev in MCP, start with git clone https://github.com/agent-bev/bev-door. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes agent-bev?: agent-bev is published by ai.agent-bev and listed on HOL.

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here: <5; HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports: <10; Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces: <5; Workspaces that approved it or include it in an approved-plugin feed, as of today.