Remote MCP · Endpoint

BeevR MCP server

No. BeevR answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://beevr.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.beevr/beevr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.05 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only access to BeevR's services, fixed-price MVP packages, case studies and articles (EN/VI).
Website
https://beevr.ai/
Listing
From the official MCP registry (active).
Recent checks of BeevR
CheckedResultHandshake
1 hour agoHandshake completed1.05 s
1 day agoHandshake completed1.07 s
4 days agoHandshake completed328 ms
6 days agoHandshake completed1.01 s
9 days agoHandshake completed305 ms
11 days agoHandshake completed311 ms
13 days agoHandshake completed929 ms
15 days agoHandshake completed1.18 s
17 days agoHandshake completed304 ms
19 days agoHandshake completed317 ms
21 days agoHandshake completed309 ms
22 days agoHandshake completed301 ms
23 days agoHandshake completed1.16 s

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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