TeamMeet
REMOTE · TEAMMEET.AI
Start meetings and work with meeting transcripts, notes, recordings and follow-up tasks.
Available components
Last scanned (23 hours ago)
Scores higher than 44% 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 18 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1878 tokens (~104/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" 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 18 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
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 61
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://teammeet.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=teammeet.ai | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5eb277e0036804cc57ee963ecc36cdcf4d6 |
| SANs: teammeet.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 teammeet.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| teammeet.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://teammeet.ai/mcp | Verified | 200 | |
| http (plaintext) | http://teammeet.ai/mcp | HTTPS enforced | 301 | https://teammeet.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 →
draw ~59
Generate a picture from a description and put it in the meeting for everyone to see.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | diagram and infographic render legible labels; visual and meme are for imagery. |
| meeting | string | yes | – |
| prompt | string | yes | – |
No output schema declared.
No examples provided.
get_notes ~63
What the room has read out of the conversation so far — decisions, open questions, actions and live disagreements. Every item carries a verbatim quote from the transcript; anything that failed that check is marked unverified rather than presented as fact.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | – |
No output schema declared.
No examples provided.
get_task ~72
One task handed to you from a call, in full: the words the person asked in, who they are, the lines of the call just before (each with the microphone it came in on), and any TeamMeet fix request it is about.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | The task id, tmt_… |
No output schema declared.
No examples provided.
get_transcript ~87
The full transcript of a meeting, with who said each line. Speaker attribution here is not a guess from a mixed audio stream — each microphone is transcribed separately, so the name on a line is the connection the words arrived on.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | The meeting code, like abc-defg-hij. |
| since | number | – | Only lines after this epoch-ms timestamp. |
No output schema declared.
No examples provided.
hand_off ~88
Hand a task to another person's agent, from the call you are in — they see it in the call and send it to their Claude with one press. Name the person as they appear in the call.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | – |
| task | string | yes | What their agent should do, in plain words. |
| to | string | yes | The person's name as it shows in the call. |
No output schema declared.
No examples provided.
import_transcript ~195
Bring a meeting transcript or a chat log from another tool into the dashboard of the account this key was minted by — .vtt/.srt captions (Zoom, Google Meet, Teams, Fireflies, Grain), Otter-style text, Read AI JSON, any JSON list of turns with names and times, or the chats: Google Meet's chat log, Zoom's meeting_saved_chat.txt, a WhatsApp export. Speaker labels are kept exactly as written; a chat is filed as a chat. Returns the meeting id and link.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The file name, with its extension — it says what format this is and often carries the date. |
| started_at | string | – | ISO 8601 start time, if the file does not say. |
| text | string | yes | The whole file as text. |
| title | string | – | A title for the meeting, if the file name is not one. |
No output schema declared.
No examples provided.
join_meeting ~97
Join a TeamMeet call you are in, as your own agent — "<your name>'s Claude" appears in the call, announced in its chat, and anyone in it can remove you. Then call listen to hear it. You can only join a call the person this connector belongs to is in (signed in) or started.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | The meeting code, like abc-defg-hij, or its link. |
No output schema declared.
No examples provided.
list_meetings ~29
List the meetings this key started that are still running, with how many people are in each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recordings ~31
Recordings this key can see, newest first, with their share links.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | – | – |
No output schema declared.
No examples provided.
listen ~144
Wait for what happens next in a call you joined: new transcript lines with who said each (ground truth — every microphone is transcribed on its own), new chat messages, and tasks handed to you. Returns as soon as there is something, or after wait_seconds. Pass back the "next" value as since. Keep calling it to stay in the call; you leave after 90 seconds without one.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | – |
| since | number | – | The "next" value from the last listen. Omit for the last few minutes. |
| wait_seconds | number | – | How long to wait for something new, up to 45. Default 25. |
No output schema declared.
No examples provided.
my_tasks ~73
What your calls have handed to you — the person this TeamMeet connector belongs to — to do: who asked, what they asked for, which call, and where each one has got to. Open ones first. Use get_task for the whole of one.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include finished and declined ones too. |
No output schema declared.
No examples provided.
send_feedback ~200
File something you noticed about Team Meet — a bug, a confusing moment, an idea. It goes on the list the product is built from; repeats are counted and move the item up. Be specific: the page, what you expected, what happened. Set fix=true when the person wants the platform itself changed: it becomes a fix request, an AI engineer turns it into a pull request, and a person reviews it before it ships. The reply carries a link to follow it.
| Name | Type | Req | Description |
|---|---|---|---|
| actual | string | – | – |
| expected | string | – | – |
| fix | boolean | – | true = the person wants this FIXED in the platform; it becomes a pull request. |
| kind | string | – | – |
| page | string | – | The URL or path where you noticed it. |
| severity | integer | – | 5 = blocks the task, 1 = polish |
| text | string | yes | What you noticed, in one or a few sentences. |
No output schema declared.
No examples provided.
send_message ~46
Post a message into the meeting chat, from this agent, under its own name. Everyone in the room sees it.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
send_notetaker ~145
Send the TeamMeet notetaker to a Zoom, Google Meet, Microsoft Teams or Webex meeting you did not host. It joins as a participant, records, and when the call ends the transcript, recap and action items land in the dashboard of the account this key was minted by. Needs a key minted while signed in. Metered in minutes per month by plan.
| Name | Type | Req | Description |
|---|---|---|---|
| join_at | string | – | ISO 8601 time to join, for a meeting later today. Omit to join now. |
| name | string | – | What the bot is called in the call. Default "TeamMeet notetaker". |
| url | string | yes | The meeting link. |
No output schema declared.
No examples provided.
speak ~78
Say something out loud in the meeting. It is spoken through the room's speakers and joins the transcript, so it is on the record like anything else that was said. Use sparingly — this interrupts people.
| Name | Type | Req | Description |
|---|---|---|---|
| meeting | string | yes | – |
| text | string | yes | Keep it to a sentence or two. Nobody wants to be read a paragraph. |
No output schema declared.
No examples provided.
start_meeting ~151
Start a new meeting and get its code and link. The link works in any browser with no account and no download. Nobody can join a meeting that was not started this way.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | What the AI in the room should do with what is said. "meet" keeps live notes; "agenda" tracks topics you supply; "brainstorm" draws pictures from the conversation; "align" runs a decision protocol; "… |
| topics | array | – | Agenda topics, if mode is agenda. |
No output schema declared.
No examples provided.
submit_fix ~207
Open a pull request against Team Meet: a unified diff (`git diff` output) you wrote against its source, for a fix request. Give feedback_id to attach it to an existing request (see send_feedback, or GET /api/fixes for the open ones), or give text to file the request and attach the fix in one step. Nothing is applied automatically — a person reviews and merges. Run the tests your change touches first (AGENTS.md says which) and report them.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | What changed and why, and how you checked it. |
| diff | string | yes | Unified diff against the source, with diff --git headers. |
| feedback_id | string | – | The fix request this resolves. |
| page | string | – | – |
| tests | object | – | – |
| text | string | – | If there is no feedback_id: what is being fixed, as a person would report it. |
| title | string | – | One line, like a commit subject. |
No output schema declared.
No examples provided.
update_task ~113
Say where a task has got to. The call it came from sees it in its chat: "working" when you start, "done" with a short note and the link to what you made (a pull request, a document), or "blocked" with what you need from a person.
| Name | Type | Req | Description |
|---|---|---|---|
| links | array | – | Links to what you made. |
| note | string | – | Two plain sentences at most. |
| status | string | yes | – |
| task | string | yes | The task id, tmt_… |
No output schema declared.
No examples provided.
How do I install the TeamMeet MCP server?
TeamMeet is a hosted endpoint at https://teammeet.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 · teammeet.ai
claude mcp add --transport http theguysaccount-teammeet 'https://teammeet.ai/mcp'
What is the TeamMeet MCP server?
TeamMeet is an MCP server listed in the public MCP registry as io.github.theguysaccount/teammeet. Start meetings and work with meeting transcripts, notes, recordings and follow-up tasks. This page covers its hosted endpoint (https://teammeet.ai/mcp).
Is the TeamMeet MCP server safe to use?
TeamMeet scores 63 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 TeamMeet MCP server expose?
TeamMeet exposes 18 tools: start_meeting, list_meetings, get_transcript, get_notes, send_message, and 13 more. Their descriptions and schemas cost roughly 1,878 tokens of context every time the server is loaded.
Does the TeamMeet MCP server require authentication?
No. We connected to TeamMeet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TeamMeet MCP server still maintained?
TeamMeet 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.