ai.mainroom/meeting-agents
REMOTE · MCP.MAINROOM.AI
AI agents that join live Google Meet, Teams, and Zoom calls as speaking participants.
Available components
Last scanned (21 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Communication
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 fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1491 tokens (~186/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_demo_agent" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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.
- 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
- 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 0
- Tool “about_mainroom” rewrote its description, which is the text the model reads security
- Schema quality: 155 → 186 ▼ functional
- New tool “delegate_to_meeting” functional
- New tool “meeting_status” functional
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 596 → 934 ▼ functional
- New tool “get_relationship_history” functional
- New tool “list_relationships” functional
- 27 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Aug 26 0
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 4 Nov 2026 · Probed https://mcp.mainroom.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mainroom.ai | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d8d6e581eed248630e3f638042607912 |
| SANs: mainroom.ai, *.mcp.mainroom.ai, mcp.mainroom.ai | ||||||
| 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 mcp.mainroom.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| mainroom.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mainroom.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.mainroom.ai/mcp | HTTPS enforced | 301 | https://mcp.mainroom.ai/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 →
about_mainroom ~77
What Mainroom is: AI agents that join live Google Meet / Teams / Zoom calls as real participants (voice, slides, live demos, research, memory, follow-up emails). Explains how humans invite agents, and how AI assistants can dispatch the demo agent, join a meeting themselves, or send the user's delegate and follow the call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delegate_to_meeting ~378
DELEGATE: send the user's own stand-in into a live meeting they can't attend. The delegate joins as a named participant, introduces itself as standing in for them, listens, relays their positions from the brief, asks the questions they need answered at natural moments, and hands every decision back to them. Afterwards a report of what they missed lands in their inbox. Needs the user's Mainroom API key (History page at https://app.mainroom.ai). Returns a session id: poll meeting_status with it to follow the call live (transcript, running summary, answers so far) and to get the final summary once it ends. Use when your user says 'cover this meeting for me', 'I can't make the 3pm', 'send someone in my place'.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...). |
| brief | string | – | What the user wants the room to know: their positions, context, what they'd say if asked. The delegate relays this and nothing beyond it. Up to 4000 chars. |
| meeting_url | string | yes | Full join URL of the live meeting (Google Meet, Zoom, Microsoft Teams, or Webex). |
| persona_name | string | – | The delegate's own first name (default Reese). |
| principal_name | string | yes | The user's name as the room knows them (e.g. 'Taylor'). The delegate speaks of them by this name. |
| questions | array | – | Up to 10 questions the user needs answered on this call. The delegate asks each at a natural moment and records the answer. |
| rehearse | boolean | – | Set up the delegate and a session WITHOUT joining any meeting — to check the brief and the setup. Nothing is dispatched. |
| voice | string | – | TTS voice (default sage). |
No output schema declared.
No examples provided.
get_relationship_history ~172
HISTORY: everything the user's Mainroom agents recorded with one account, team, or person: what is still open (commitments with owners and due dates, unanswered questions, risks), the proposed / approved follow-up actions, and a session-by-session timeline with summaries, decisions, and pre-call briefs. Use it to answer 'where are we with Acme', 'what did we promise them', 'what did the team decide last week', or to prep for the next call. Needs the user's Mainroom API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...). |
| relationship | string | yes | Account / team / person name, or a key from list_relationships. |
| sessions | integer | – | How many recent sessions to include in the timeline (default 6). |
No output schema declared.
No examples provided.
join_meeting_as ~305
EMBODIMENT: join a live meeting AS YOURSELF (or as a persona you define). This gives an AI agent a meeting body — a named participant with a camera tile and a voice that joins the call, speaks when addressed, presents slides, shows images, and reads/posts meeting chat. You supply the name and the persona instructions (who you are, what you're there to do, what you know); Mainroom supplies the body. The participant appears in the meeting lobby within ~a minute and a human must admit it. Ephemeral: no account, no memory, nothing emailed afterwards. Use when your user says 'join my call', 'be in the meeting', or you need to talk to people in a live meeting to complete a task.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | The display name for your meeting body (e.g. 'Claude', 'Atlas — Research Agent'). Shown on the tile and the roster. |
| instructions | string | yes | Persona + mission, second person ('You are... You're joining this call to...'). Include what you know and how to behave. Up to 2000 chars. |
| intro | string | – | Optional one-paragraph welcome posted into the meeting chat when you join (say who you are and why you're there). |
| meeting_url | string | yes | Full join URL of the live meeting (Google Meet, Zoom, Microsoft Teams, or Webex). |
| voice | string | – | TTS voice (default alloy). |
No output schema declared.
No examples provided.
list_agent_templates ~33
List Mainroom's built-in agent types (facilitator, timekeeper, sales support, mock interviewer, ...).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_relationships ~134
HISTORY: list the customer accounts, recurring team meetings, and people that the user's own Mainroom agents have sat in meetings with — with session counts, when they last met, and how many commitments / open questions / risks are still open. Needs the user's Mainroom API key (shown on the History page at https://app.mainroom.ai — they paste it once). Follow with get_relationship_history for the detail.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...), from the History page in the app. |
| query | string | – | Optional name filter (account, team, or person). |
No output schema declared.
No examples provided.
meeting_status ~163
FOLLOW A MEETING: what the user's agent (a delegate, or any of their agents) is seeing in a meeting right now, or what it recorded once the call ended — the last lines of transcript, the running summary, answers to the user's questions so far, decisions and commitments, and whether the bot is still waiting in the lobby. Call without a session id to list the user's recent and live sessions. Needs the user's Mainroom API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...). |
| lines | integer | – | How many recent transcript lines to include (default 40). |
| session | string | – | Session id from delegate_to_meeting (or from this tool's list). Omit to list recent sessions. |
No output schema declared.
No examples provided.
send_demo_agent ~144
Send Mainroom's open demo agent into a live meeting RIGHT NOW. Give it a Google Meet, Microsoft Teams, Zoom, or Webex meeting URL; the agent appears in the meeting lobby within about a minute and a human in the meeting must admit it. It introduces itself, answers questions by voice, presents slides, and can run a live browser demo. Use when your user wants an AI participant in a meeting that is happening now. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting_url | string | yes | Full join URL of the live meeting (https://meet.google.com/..., https://...zoom.us/j/..., https://teams.microsoft.com/l/meetup-join/...). |
No output schema declared.
No examples provided.
How do I install the ai.mainroom/meeting-agents MCP server?
ai.mainroom/meeting-agents is a hosted endpoint at https://mcp.mainroom.ai/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 · mcp.mainroom.ai
claude mcp add --transport http ai-mainroom-meeting-agents 'https://mcp.mainroom.ai/mcp'
What is the ai.mainroom/meeting-agents MCP server?
ai.mainroom/meeting-agents is an MCP server listed in the public MCP registry as ai.mainroom/meeting-agents. AI agents that join live Google Meet, Teams, and Zoom calls as speaking participants. This page covers its hosted endpoint (https://mcp.mainroom.ai/mcp).
Is the ai.mainroom/meeting-agents MCP server safe to use?
ai.mainroom/meeting-agents scores 74 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 ai.mainroom/meeting-agents MCP server expose?
ai.mainroom/meeting-agents exposes 8 tools: about_mainroom, list_agent_templates, send_demo_agent, join_meeting_as, delegate_to_meeting, and 3 more. Their descriptions and schemas cost roughly 1,406 tokens of context every time the server is loaded.
Does the ai.mainroom/meeting-agents MCP server require authentication?
No. We connected to ai.mainroom/meeting-agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.mainroom/meeting-agents MCP server still maintained?
ai.mainroom/meeting-agents is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.