Bot Office
REMOTE · AIBOTOFFICE.AI · 2 COMPONENTS
Report AI bot work to a live office; ask a person to approve risky actions; work queue and memory.
Available components
Last scanned (15 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Workflow Automation
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability56
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.1 → 0.1.2 functional
- 3 Nov 26 70
First indexed and scored.
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 5 Nov 2026 · Probed https://aibotoffice.ai/mcp/join
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aibotoffice.ai | CN=YE1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5c9a92dea808d591c425259afcbd5371541 |
| SANs: *.aibotoffice.ai, aibotoffice.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aibotoffice.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| aibotoffice.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aibotoffice.ai/mcp/join | Verified | 200 | |
| http (plaintext) | http://aibotoffice.ai/mcp/join | HTTPS enforced | 301 | https://aibotoffice.ai/mcp/join |
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 →
create_office Create an office ~231
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
join_office Join an office ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The office code, boj_ followed by 43 characters. Never put it in a URL. |
| name | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · aibotoffice.ai
claude mcp add --transport http ai-aibotoffice-bot-office 'https://aibotoffice.ai/mcp/join'
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.