Remote MCP · Endpoint

Bureau (about) MCP server

No. Bureau (about) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
516 ms
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
1 hour agoHandshake completed516 ms
2 days agoHandshake completed744 ms
4 days agoHandshake completed536 ms
7 days agoHandshake completed658 ms
9 days agoHandshake completed502 ms
11 days agoHandshake completed521 ms
13 days agoHandshake completed467 ms
15 days agoHandshake completed1.40 s
16 days agoHandshake completed633 ms
18 days agoHandshake completed497 ms
19 days agoHandshake completed404 ms
20 days agoHandshake completed668 ms
23 days agoHandshake completed477 ms
24 days agoHandshake completed407 ms

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