Remote MCP · Endpoint

Bureau public reader MCP server

No. Bureau public reader answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://thebureauoflostcontext.agency/mcp

The last check completed an MCP handshake.

Registry name
agency.thebureauoflostcontext/bureau-public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
357 ms
Tools exposed
5 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Bureau-operated public read-only MCP service for public Context Packets and Cases.
Website
https://thebureauoflostcontext.agency/
Listing
From the official MCP registry (active).
Recent checks of Bureau public reader
CheckedResultHandshake
2 hours agoHandshake completed357 ms
1 day agoHandshake completed224 ms
3 days agoHandshake completed512 ms
3 days agoHandshake completed286 ms
4 days agoHandshake completed342 ms
5 days agoHandshake completed260 ms
7 days agoHandshake completed340 ms
10 days agoHandshake completed244 ms
12 days agoHandshake completed250 ms
14 days agoHandshake completed182 ms
17 days agoHandshake completed244 ms
19 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
23 days agoFailed - the server returned an HTTP error—
25 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—
29 days agoFailed - the server returned an HTTP error—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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