Remote MCP · Endpoint

Buzzterms MCP server

No. Buzzterms answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://buzzterms.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.buzzterms/buzzterms
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
971 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only glossary of technology and business terms, with explanations and learning paths.
Listing
From the official MCP registry (active).
Recent checks of Buzzterms
CheckedResultHandshake
5 hours agoHandshake completed971 ms
9 days agoHandshake completed1.13 s
10 days agoHandshake completed192 ms
11 days agoHandshake completed187 ms
12 days agoHandshake completed1.00 s
14 days agoHandshake completed185 ms
14 days agoHandshake completed1.05 s
15 days agoHandshake completed215 ms
17 days agoHandshake completed1.10 s
19 days agoHandshake completed974 ms
21 days agoHandshake completed195 ms
24 days agoHandshake completed1.00 s
26 days agoHandshake completed897 ms

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.

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