Skip to content

Boardroom Revenue Control MCP server

io.github.boardroomgen-ai-ae/boro-aiboardroomgen-ai-aestreamable-httpv1.0.0Scanned

Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution.

13 tools: 7 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 7 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Boardroom Revenue Control MCP server can do

The Boardroom Revenue Control MCP server is published by the GitHub account boardroomgen-ai-ae. It has 13 tools. It can create or change data (7 tools: crm_pipeline_overview, crm_leads_without_task, ad_attribution, agent_conversations and 3 more), but cannot delete data. 6 tools only read.

2 tools read private data (crm_get_lead and agent_get_conversation); 1 tool brings in text other people can write (agent_get_conversation).

The fixed checks matched 3 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 7Claude Code: ask
  • ad_attributionWhich advertisement produced which conversation: ad id, creative, first-touch flag, and the lead it bound to.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • title: Ad attribution
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • agent_configHow 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 kn…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...e whole is a separate, narrower ask. No credential of any kind is reachable from here: an..."

      What this check looks for
    Description, as the server wrote it
    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]

    Annotations the server declares

    • title: AI-agent configuration
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • agent_conversationsConversations the AI agent handled, with intent, language, message count and the deal they bound to.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Conversations the AI agent handled, with intent, language, message count and the deal they bound to. Contacts masked. [scope: agent:read]

    Annotations the server declares

    • title: AI-agent conversations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • crm_leads_without_taskOpen leads with no unfinished task against them — the follow-up leak.1 finding

    Why it is in this group

    • The description's first verb is "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "crm_leads_without_task" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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]

    Annotations the server declares

    • title: Leads without a follow-up task
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • crm_pipeline_overviewEvery pipeline and stage with its lead count and total value.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Every pipeline and stage with its lead count and total value. The shape of the funnel. [scope: crm:read]

    Annotations the server declares

    • title: Pipeline overview
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • partner_overviewThis 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 par…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • title: Partner overview
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • voice_callsCalls with direction, disposition and talk time.1 finding

    Why it is in this group

    • The name "voice_calls" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "voice_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "voice_calls" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Calls with direction, disposition and talk time. Customer numbers masked. [scope: crm:read]

    Annotations the server declares

    • title: Voice calls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • agent_get_conversationOne conversation with its transcript — what the customer wrote and what the agent answered.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "agent_get_conversation" says "get": a word for reading.

    What it can reach

    • private-dataThe name "agent_get_conversation" says "get" and "conversation": it reads messages.
    • private-dataThe description's first sentence says "conversation": it reads messages.
    • untrusted-inputThe name "agent_get_conversation" says "get" and "conversation": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    One conversation with its transcript — what the customer wrote and what the agent answered. [scope: agent:read]

    Annotations the server declares

    • title: One conversation transcript
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • crm_get_leadOne lead — notes, events, stage history and open tasks.Reads private dataNo findings

    Why it is in this group

    • The name "crm_get_lead" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • title: Get one lead
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • crm_list_leadsLeads in this workspace, newest activity first.No findings

    Why it is in this group

    • The name "crm_list_leads" says "list": a word for reading.
    Description, as the server wrote it
    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]

    Annotations the server declares

    • title: List leads
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • dashboard_snapshotThe workspace's own KPI contract as the dashboard renders it, with the time it was built.No findings

    Why it is in this group

    • The name "dashboard_snapshot" says "snapshot": a word for reading.
    Description, as the server wrote it
    The workspace's own KPI contract as the dashboard renders it, with the time it was built. [scope: crm:read]

    Annotations the server declares

    • title: Dashboard snapshot
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • marketing_snapshotAdvertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join.No findings

    Why it is in this group

    • The name "marketing_snapshot" says "snapshot": a word for reading.
    Description, as the server wrote it
    Advertising performance: spend, reach, clicks, cost per lead, per campaign, plus the CRM join. [scope: marketing:read]

    Annotations the server declares

    • title: Marketing snapshot
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • whoamiWho this token is, which workspace it can read, and which scopes it carries.No findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Who am I (token and workspace)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://control.boardroom-ai.ae/.well-known/oauth-protected-resource/mcp
Authorization servers
https://control.boardroom-ai.ae
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://control.boardroom-ai.ae/mcp: tools/list returned 13 tools to an anonymous client, including crm_pipeline_overview (write), crm_leads_without_task (write), ad_attribution (write), agent_conversations (write), agent_config (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "crm_leads_without_task" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

    What this check looks for
  • The server marks "voice_calls" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "voice_calls" says "call": a word for a change.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...e whole is a separate, narrower ask. No credential of any kind is reachable from here: an..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http boro-ai https://control.boardroom-ai.ae/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http boro-ai https://control.boardroom-ai.ae/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__boro-ai__whoami",
      "mcp__boro-ai__crm_list_leads",
      "mcp__boro-ai__crm_get_lead",
      "mcp__boro-ai__agent_get_conversation",
      "mcp__boro-ai__dashboard_snapshot",
      "mcp__boro-ai__marketing_snapshot"
    ],
    "ask": [
      "mcp__boro-ai__crm_pipeline_overview",
      "mcp__boro-ai__crm_leads_without_task",
      "mcp__boro-ai__ad_attribution",
      "mcp__boro-ai__agent_conversations",
      "mcp__boro-ai__agent_config",
      "mcp__boro-ai__partner_overview",
      "mcp__boro-ai__voice_calls"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as boro-ai. Review it before you use it.

Capability tags behind 2 rules
  • mcp__boro-ai__crm_get_lead private-data
  • mcp__boro-ai__agent_get_conversation private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.boardroomgen-ai-ae/boro-ai/verify?hash=9af3022e5750dfc6eceaf7dd83cda0fcc84a957cca76b544e0810acca26c8801" | jq -e '.changed == false'

Pinned hash 9af3022e5750, from Nov 16, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.boardroomgen-ai-ae/boro-ai/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.boardroomgen-ai-ae/boro-ai
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.boardroomgen-ai-ae/boro-ai.svg)](https://radar.anlyon.com/servers/io.github.boardroomgen-ai-ae/boro-ai)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:24 UTC.

Boardroom Revenue Control MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Boardroom Revenue Control MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 7 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Boardroom Revenue Control MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Boardroom Revenue Control MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Boardroom Revenue Control MCP server have?

13 tools: 7 write, 6 read. crm_pipeline_overview, crm_leads_without_task, ad_attribution, agent_conversations, agent_config, partner_overview, voice_calls, whoami and 5 more.

Does the Boardroom Revenue Control MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Boardroom Revenue Control MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Boardroom Revenue Control MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.