# Bot Office (remote · aibotoffice.ai)

Report AI bot work to a live office; ask a person to approve risky actions; work queue and memory.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `aibotoffice.ai`: 75/100, [markdown](https://verifymcp.io/servers/ai-aibotoffice-bot-office/aibotoffice.md), [page](https://verifymcp.io/servers/ai-aibotoffice-bot-office/aibotoffice)
- remote · `aibotoffice.ai`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join.md), [page](https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join)

## Channel facts

- Endpoint: `https://aibotoffice.ai/mcp/join`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1357 tokens (~678/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Bot Office MCP server?

Bot Office is a hosted endpoint at https://aibotoffice.ai/mcp/join, 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.

### Claude

```bash
claude mcp add --transport http ai-aibotoffice-bot-office 'https://aibotoffice.ai/mcp/join'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-aibotoffice-bot-office": {
      "url": "https://aibotoffice.ai/mcp/join"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-aibotoffice-bot-office": {
      "type": "http",
      "url": "https://aibotoffice.ai/mcp/join"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-aibotoffice-bot-office]
url = "https://aibotoffice.ai/mcp/join"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-aibotoffice-bot-office": {
      "type": "remote",
      "url": "https://aibotoffice.ai/mcp/join",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-aibotoffice-bot-office --url 'https://aibotoffice.ai/mcp/join' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-aibotoffice-bot-office:
    url: "https://aibotoffice.ai/mcp/join"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-aibotoffice-bot-office": {
      "Transport": "http",
      "Url": "https://aibotoffice.ai/mcp/join"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-aibotoffice-bot-office -t streamable-http -u 'https://aibotoffice.ai/mcp/join'
```

### Other

```json
{
  "mcpServers": {
    "ai-aibotoffice-bot-office": {
      "type": "http",
      "url": "https://aibotoffice.ai/mcp/join"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.1 → 0.1.2

### 2026-11-03 (score 70)

First indexed and scored.

## MCP tools (2)

### `join_office` (~228 tokens)

Join an office

Ask to join a Bot Office with the office code your owner gave you (boj_...). Send your own name, the platform you run on and one line on what you do. Usually the owner must approve you first: the answer is status pending with a join_pass; POST /v1/join/status with Authorization: Bearer <join_pass> every 30 seconds until it says approved and carries your bot_token (shown once). Then add this MCP server again with that bot_token as Bearer (or /mcp/<bot_token>) to get report_to_office. The code only asks to join: it cannot read the office or send events.

Input parameters:

- `code` (string, required): The office code, boj_ followed by 43 characters. Never put it in a URL.
- `name` (string, required): Your display name, at most 40 characters (text only).
- `platform` (string): What runs you, one word (e.g. openai, claude, n8n).
- `purpose` (string): One line: what you do. No customer data.

### `create_office` (~231 tokens)

Create an office

Create a new Bot Office with no credential (same as POST /v1/workspaces; 10 per address per hour). The answer carries workspace_id, office_url and ingest_key: the office ACCESS CODE, shown once and never recoverable. Give the access code to your human (it manages the office); then mint your own bot link with it (mint_bot_links on /mcp with Authorization: Bearer <access code>, or POST /v1/workspaces/:id/tokens) and connect to /mcp with that bot link to report. Example: {"name":"Acme Dental","url":"https://acme-dental.example"} (url is optional: the office takes the site's name, colours and industry when given).

Input parameters:

- `kit` (string): Industry kit id when you know it (e.g. generic, dental, gov-cyber, msp). Optional.
- `name` (string): The organisation's name (shown on the office).
- `url` (string): The organisation's website, http(s). Optional: used for the name, colours and industry kit.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70

## Common questions

### What is the Bot Office MCP server?

Bot Office is an MCP server listed in the public MCP registry as ai.aibotoffice/bot-office. Report AI bot work to a live office; ask a person to approve risky actions; work queue and memory. This page covers its hosted endpoint (https://aibotoffice.ai/mcp/join).

### Is the Bot Office MCP server safe to use?

Bot Office scores 71 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 Bot Office MCP server expose?

Bot Office exposes 2 tools: join_office, create_office. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.

### Does the Bot Office MCP server require authentication?

No. We connected to Bot Office without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bot Office MCP server still maintained?

Bot Office is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Bot Office MCP server?

VerifyMCP ran 13 checks on Bot Office, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://aibotoffice.ai/mcp/join
- Website: https://aibotoffice.ai/for-bots
- Changelog RSS feed: https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join.json
- HTML version of this page: https://verifymcp.io/servers/ai-aibotoffice-bot-office/mcp-join