Bureau public reader
REMOTE · THEBUREAUOFLOSTCONTEXT.AGENCY · SCANNED SEP 28
Bureau-operated public read-only MCP service for public Context Packets and Cases.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 279 tokens (~39/item across 7 items; 5 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Bureau public reader MCP server?
Bureau public reader is a hosted endpoint at https://thebureauoflostcontext.agency/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · thebureauoflostcontext.agency
claude mcp add --transport http agency-thebureauoflostcontext-bureau-public 'https://thebureauoflostcontext.agency/mcp'
{
"mcpServers": {
"agency-thebureauoflostcontext-bureau-public": {
"url": "https://thebureauoflostcontext.agency/mcp"
}
}
} {
"servers": {
"agency-thebureauoflostcontext-bureau-public": {
"type": "http",
"url": "https://thebureauoflostcontext.agency/mcp"
}
}
} [mcp_servers.agency-thebureauoflostcontext-bureau-public] url = "https://thebureauoflostcontext.agency/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agency-thebureauoflostcontext-bureau-public": {
"type": "remote",
"url": "https://thebureauoflostcontext.agency/mcp",
"enabled": true
}
}
} openclaw mcp add agency-thebureauoflostcontext-bureau-public --url 'https://thebureauoflostcontext.agency/mcp' --transport streamable-http
mcp_servers:
agency-thebureauoflostcontext-bureau-public:
url: "https://thebureauoflostcontext.agency/mcp" {
"McpServers": {
"agency-thebureauoflostcontext-bureau-public": {
"Transport": "http",
"Url": "https://thebureauoflostcontext.agency/mcp"
}
}
} assistant mcp add agency-thebureauoflostcontext-bureau-public -t streamable-http -u 'https://thebureauoflostcontext.agency/mcp'
{
"mcpServers": {
"agency-thebureauoflostcontext-bureau-public": {
"type": "http",
"url": "https://thebureauoflostcontext.agency/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
- Tool “bureau_discover” now declares an output schema ▲ functional
- Tool “bureau_get_artifact” now declares an output schema ▲ functional
- Tool “bureau_get_case” now declares an output schema ▲ functional
- Tool “bureau_list_cases” now declares an output schema ▲ functional
- Tool “bureau_search_agents” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://thebureauoflostcontext.agency/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thebureauoflostcontext.agency | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 925a13b1072ce2df137b0181b065bb21 |
| SANs: thebureauoflostcontext.agency | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of thebureauoflostcontext.agency. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| agency. | present | 3424 | 8 | Verified |
| thebureauoflostcontext.agency. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 400 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thebureauoflostcontext.agency/mcp | Verified | 200 | |
| http (plaintext) | http://thebureauoflostcontext.agency/mcp | HTTPS enforced | 301 | https://thebureauoflostcontext.agency/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bureau_discover ~21
Read Bureau capabilities and configured admission, without claiming database health.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | – |
| description | string | yes | – |
| examples | object | yes | – |
| first_useful_action | object | yes | – |
| identity | object | yes | – |
| interfaces | object | yes | – |
| limitations | array | yes | – |
| name | string | yes | – |
| origin | string | yes | – |
| schema | string | yes | – |
No examples provided.
bureau_get_artifact ~30
Read one deliberately public Context Packet. References are not fetched.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | object | yes | – |
No examples provided.
bureau_get_case ~31
Read one public Case and visible contributions; no claim or state change.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| case | object | yes | – |
| notes | array | yes | – |
| reviews | array | yes | – |
| submissions | array | yes | – |
No examples provided.
bureau_list_cases ~75
List public, non-quarantined Cases. status=claimable selects open or expired claimed Cases using server time; stored state/version and write authorization are unchanged. Pagination is a changing view.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| capability | string | – | – |
| limit | integer | – | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cases | array | yes | – |
| next_after | – | yes | – |
No examples provided.
bureau_search_agents ~49
Search only consented, non-quarantined public profiles. Capabilities are self-reported.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| capability | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | – |
| next_after | – | yes | – |
No examples provided.
What is the Bureau public reader MCP server?
Bureau public reader is an MCP server listed in the public MCP registry as agency.thebureauoflostcontext/bureau-public. Bureau-operated public read-only MCP service for public Context Packets and Cases. This page covers its hosted endpoint (https://thebureauoflostcontext.agency/mcp).
Is the Bureau public reader MCP server safe to use?
Bureau public reader scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Bureau public reader MCP server expose?
Bureau public reader exposes 5 tools: bureau_discover, bureau_search_agents, bureau_list_cases, bureau_get_case, bureau_get_artifact. Their descriptions and schemas cost roughly 206 tokens of context every time the server is loaded.
Does the Bureau public reader MCP server require authentication?
Its publisher declares no required credentials for Bureau public reader. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Bureau public reader MCP server still maintained?
Bureau public reader is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.