Remote MCP · Endpoint

agent-bev MCP server

No. agent-bev answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.bev-buyer.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.agent-bev/bev-door
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
The world's largest agentic B2B hub for beer, wine and spirits. Powered by CUVEE. Trade only.
Listing
From the official MCP registry (active).
Recent checks of agent-bev
CheckedResultHandshake
1 hour agoHandshake completed82 ms
2 days agoHandshake completed114 ms
4 days agoHandshake completed359 ms
6 days agoHandshake completed85 ms
8 days agoHandshake completed133 ms
10 days agoHandshake completed59 ms
11 days agoHandshake completed192 ms
13 days agoHandshake completed75 ms
14 days agoHandshake completed282 ms
15 days agoHandshake completed56 ms
18 days agoHandshake completed92 ms
19 days agoHandshake completed51 ms
21 days agoHandshake completed53 ms
22 days agoHandshake completed45 ms
23 days agoHandshake completed109 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with agent-bev and makes no claim about it beyond what these checks measured.