Remote MCP · Endpoint

BriefMe MCP server

No. BriefMe answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://briefme.us/mcp

The last check completed an MCP handshake.

Registry name
us.briefme/agenda-timer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
547 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
Listing
From the official MCP registry (active).
Recent checks of BriefMe
CheckedResultHandshake
1 hour agoHandshake completed547 ms
2 days agoHandshake completed164 ms
4 days agoHandshake completed490 ms
5 days agoHandshake completed486 ms
7 days agoHandshake completed492 ms
8 days agoHandshake completed554 ms
9 days agoHandshake completed553 ms
12 days agoHandshake completed459 ms
13 days agoHandshake completed492 ms
15 days agoHandshake completed501 ms
17 days agoHandshake completed487 ms
18 days agoHandshake completed467 ms
19 days agoHandshake completed459 ms
20 days agoHandshake completed485 ms
21 days agoHandshake completed476 ms
21 days agoHandshake completed463 ms
23 days agoHandshake completed453 ms

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

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