Remote MCP · Endpoint

Buzz Dealer AI MCP server

No. Buzz Dealer AI answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.buzzdealer.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.buzzdealer-ai/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
640 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Press release distribution, digital PR, and brand and personal reputation checks for your AI.
Listing
From the official MCP registry (active).
Recent checks of Buzz Dealer AI
CheckedResultHandshake
34 minutes agoHandshake completed640 ms
9 days agoHandshake completed487 ms
10 days agoHandshake completed500 ms
11 days agoHandshake completed477 ms
12 days agoHandshake completed647 ms
14 days agoHandshake completed462 ms
14 days agoHandshake completed518 ms
15 days agoHandshake completed351 ms
17 days agoHandshake completed630 ms
19 days agoHandshake completed461 ms
21 days agoHandshake completed440 ms
24 days agoHandshake completed458 ms
26 days agoHandshake completed497 ms
28 days agoCredentials required—

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

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 Buzz Dealer AI and makes no claim about it beyond what these checks measured.