Boardroom Revenue Control
REMOTE · CONTROL.BOARDROOM-AI.AE
Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution.
Available components
Last scanned (9 minutes ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1013 tokens (~77/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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
- 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 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.
- 21 Oct 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.
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://control.boardroom-ai.ae/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=control.boardroom-ai.ae | CN=YE1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a76ae83912a045d1ca6ba743609d1267cb |
| SANs: control.boardroom-ai.ae | ||||||
| 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 control.boardroom-ai.ae. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ae. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://control.boardroom-ai.ae/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://control.boardroom-ai.ae/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://control.boardroom-ai.ae/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://control.boardroom-ai.ae/mcp |
| Authorisation server | https://control.boardroom-ai.ae |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://control.boardroom-ai.ae/mcp | Verified | 200 | |
| http (plaintext) | http://control.boardroom-ai.ae/mcp | HTTPS enforced | 301 | https://control.boardroom-ai.ae/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 →
ad_attribution Ad attribution ~110
Which advertisement produced which conversation: ad id, creative, first-touch flag, and the lead it bound to. The per-click id is NOT returned — only whether one exists. An empty result means no ad-driven conversation has been recorded in the window, not that the tool failed. [scope: marketing:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rows to return. |
| since | string | – | today | week | month | 30d | ISO timestamp (Asia/Dubai days). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
agent_config AI-agent configuration ~102
How the AI agent is set up for this workspace: mode and persona, working hours, hand-over rules, follow-up cadence, trigger list, actions, voice scenarios, and the TITLES of its knowledge documents. Document text is not returned — the list answers what the agent knows about; reading one whole is a separate, narrower ask. No credential of any kind is reachable from here: an agent's instructions are not its keys. [scope: agent:read]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
agent_conversations AI-agent conversations ~77
Conversations the AI agent handled, with intent, language, message count and the deal they bound to. Contacts masked. [scope: agent:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rows to return. |
| since | string | – | today | week | month | 7d | ISO timestamp (Asia/Dubai days). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
agent_get_conversation One conversation transcript ~59
One conversation with its transcript — what the customer wrote and what the agent answered. [scope: agent:read]
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | UUID from agent_conversations. |
| limit | integer | – | Maximum number of rows to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
crm_get_lead Get one lead ~85
One lead — notes, events, stage history and open tasks. Phone, e-mail and messenger ids are MASKED unless this key also holds crm:read_pii, which the workspace owner grants separately. Scoped to this workspace: a lead id from elsewhere reads as not_found. [scope: crm:read]
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | UUID of the lead. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
crm_leads_without_task Leads without a follow-up task ~63
Open leads with no unfinished task against them — the follow-up leak. Sorted by idle time, longest first. Idle days are counted in Asia/Dubai. [scope: crm:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rows to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
crm_list_leads List leads ~169
Leads in this workspace, newest activity first. Phone and email are MASKED here — use crm_get_lead for one record when the full contact is genuinely needed. `total` is the count before paging, so it answers 'how many leads exist'. [scope: crm:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rows to return. |
| offset | integer | – | Rows to skip before the first returned row (for paging). |
| pipeline_id | string | – | UUID of one pipeline. Omit for all. |
| since | string | – | today | yesterday | week | month | 7d | 30d | ISO timestamp. Days are Asia/Dubai. |
| stage | string | – | Stage name, exact (case-insensitive). Omit for all stages. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
crm_pipeline_overview Pipeline overview ~35
Every pipeline and stage with its lead count and total value. The shape of the funnel. [scope: crm:read]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
dashboard_snapshot Dashboard snapshot ~34
The workspace's own KPI contract as the dashboard renders it, with the time it was built. [scope: crm:read]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
marketing_snapshot Marketing snapshot ~36
Advertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join. [scope: marketing:read]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
partner_overview Partner overview ~68
This partner's own cabinet: referral code and link, the clients who registered through it, the agreed commission rate, what has accrued so far, and which client workspaces this partner currently holds a grant for. Only answers for a token bound to a partner. [scope: partner:read]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
voice_calls Voice calls ~66
Calls with direction, disposition and talk time. Customer numbers masked. [scope: crm:read]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of rows to return. |
| since | string | – | today | week | month | 7d | ISO timestamp (Asia/Dubai days). |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
whoami Who am I (token and workspace) ~40
Who this token is, which workspace it can read, and which scopes it carries. Call this first: it tells you which of the other tools will work.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Machine-readable refusal code (a string), present only when ok is false. |
| message | – | – | Human-readable explanation of a refusal (a string). |
| ok | boolean | – | False when the call was refused or failed; see error. |
No examples provided.
How do I install the Boardroom Revenue Control MCP server?
Boardroom Revenue Control is a hosted endpoint at https://control.boardroom-ai.ae/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 · control.boardroom-ai.ae
claude mcp add --transport http boardroomgen-ai-ae-boro-ai 'https://control.boardroom-ai.ae/mcp'
What is the Boardroom Revenue Control MCP server?
Boardroom Revenue Control is an MCP server listed in the public MCP registry as io.github.boardroomgen-ai-ae/boro-ai. Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution. This page covers its hosted endpoint (https://control.boardroom-ai.ae/mcp).
Is the Boardroom Revenue Control MCP server safe to use?
Boardroom Revenue Control scores 90 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 Boardroom Revenue Control MCP server expose?
Boardroom Revenue Control exposes 13 tools: whoami, crm_list_leads, crm_get_lead, crm_pipeline_overview, crm_leads_without_task, and 8 more. Their descriptions and schemas cost roughly 944 tokens of context every time the server is loaded.
Does the Boardroom Revenue Control MCP server require authentication?
Yes. Boardroom Revenue Control asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Boardroom Revenue Control MCP server still maintained?
Boardroom Revenue Control 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.