Remote MCP · Endpoint

Bureau (about) MCP server

No. Bureau (about) answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://www.getbureau.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.getbureau/about
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.75 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.
Listing
From the official MCP registry (active).
Recent checks of Bureau (about)
CheckedResultHandshake
40 minutes agoHandshake completed3.75 s
3 days agoHandshake completed731 ms
12 days agoHandshake completed517 ms
12 days agoHandshake completed419 ms
14 days agoHandshake completed501 ms
15 days agoHandshake completed512 ms
16 days agoHandshake completed509 ms
17 days agoHandshake completed527 ms
18 days agoHandshake completed508 ms
19 days agoHandshake completed543 ms
22 days agoHandshake completed516 ms
25 days agoHandshake completed744 ms
27 days agoHandshake completed536 ms
29 days agoHandshake completed658 ms

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

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