io.github.mmedum/google-chat-mcp
MCPB · GOOGLE-CHAT-MCP_6.1.0.MCPB
Google Chat as MCP tools: read, search and write to your spaces, direct messages and sidebar.
Available components
Last scanned (3 hours ago)
Scores higher than 98% of MCPB servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mmedum/google-chat-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8071 tokens (~164/item across 49 items; 49 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 Management84
- Stability check failed: the tool surface changed between 2.3.1 and 6.1.0: 5 tool removals, 0 breaking changes, 1 additions. See how to fix → Fail
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
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 50 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 24 Oct 26 +1
- Package version: 6.0.0 → 6.1.0 functional
- 23 Oct 26 −1
- Stability: 0.87 → fail ▼ security
- Schema quality: 9031 → 8071 ▲ functional
- Package version: 5.1.1 → 6.0.0 functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 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.
- 14 Oct 26 +41
- Injection markers: unverified → pass ▲ security
- Stability: unverified → 0.60 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Package version: 4.0.0 → 5.1.1 functional
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- Package version: 4.0.0 → 5.1.1 functional
- 12 Oct 26 +10
- Provenance: unverified → pass ▲ security
- The attested source repository moved: mmedum/google-chat-mcp security
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 24 Oct 2026 · Analysed mcpb/https://github.com/mmedum/google-chat-mcp/releases/download/v6.1.0/google-chat-mcp_6.1.0.mcpb@6.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | mcpb |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | mmedum/google-chat-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mmedum/google-chat-mcp/.github/workflows/release.yml@refs/tags/v6.1.0 |
| Rekor log index | 3429928998 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:210f2c43afe76892409291a082e7036ce39d1165164c1bd3e02c48982046df2e |
Background: How many MCP packages publish verified provenance →
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 →
update_message ~144
Replace the text of a message you sent. Text only: cards and attachments are left untouched, and editing them needs an identity this server does not have. An edit that newly mentions everyone in the space, <users/all>, is refused [blocked], since it notifies every member. Set dry_run to see the patch body without applying it. Needs the restricted-tier chat.messages scope.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | return the patch body without applying it |
| message_name | string | yes | the message to edit, spaces/{space}/messages/{message}; you must be its sender |
| text | string | yes | the replacement body, 1 to 4096 characters |
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | yes | true when nothing was changed |
| message_name | string | yes | the message that was edited |
| rendered_payload | null|object | yes | on a dry run, the exact patch body; null on a real edit |
| text | string | yes | the body it now has |
No examples provided.
update_space ~253
Rename a space, change its description, or make it private again. Pass at least one; an empty edit is refused. Editing the description keeps the space's guidelines: Google's mask covers both at once, so the server reads them and sends them back unchanged. audience private makes a space private; Google takes it only on its own, from a space manager. Opening a space to an audience is set_space_audience's. Set dry_run to see the patch body first. Needs the restricted-tier chat.spaces scope.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | private to make the space private again; omit it to leave access alone. Opening a space to a target audience is set_space_audience's, and anything else here is refused. Change it in a call of its own |
| description | null|string | – | a new description, up to 150 characters; omit to leave it alone. Pass an empty string to clear it |
| display_name | null|string | – | a new name, 1 to 128 characters; omit to leave it alone |
| dry_run | boolean | – | return the patch body and its mask without applying them |
| space_id | string | yes | the space to edit, spaces/{id} |
| Name | Type | Req | Description |
|---|---|---|---|
| audience | null|string | yes | the target audience that was set, private when the space was made private, or null when the call left it alone |
| description | null|string | yes | the description that was set, or null when the call left it alone |
| display_name | null|string | yes | the name that was set, or null when the call left it alone |
| dry_run | boolean | yes | true when nothing was changed |
| rendered_payload | null|object | yes | on a dry run, the exact patch body; null on a real edit |
| space_id | string | yes | the space that was edited |
| update_mask | null|string | yes | which top-level fields the patch targeted |
No examples provided.
update_space_notification_setting ~132
Change what Chat tells you about a space, or mute it. Pass either setting or both; whatever you leave out is left alone. Affects you and nobody else.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | return the request body without changing anything |
| mute_setting | string | – | MUTED or UNMUTED; omit to leave it alone. MUTED silences the space whatever the other setting says |
| notification_setting | string | – | ALL, MAIN_CONVERSATIONS, FOR_YOU or OFF; omit to leave it alone |
| space_id | string | yes | the space, spaces/{id} |
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | yes | true when nothing was changed |
| mute_setting | string | yes | MUTED silences the space whatever notification_setting says; UNMUTED respects it |
| name | string | yes | the setting's own resource name |
| notification_setting | string | yes | ALL for every new thread and mention, MAIN_CONVERSATIONS for the main conversation only, FOR_YOU for mentions and followed threads, OFF for none, or NOTIFICATION_SETTING_UNSPECIFIED for a value this… |
| rendered_payload | null|object | yes | on a dry run, the exact body that would have been sent; null on a real change |
No examples provided.
upload_attachment ~212
Upload a local file to a Chat space and get back the token that attaches it. Post it with send_message's attachment_upload_token, in the same space; nobody sees the file until then. The file has to be inside the server's local directory, and Google's limit is 200 MB. Set dry_run to check the file and see what would be sent. This needs the server to have been started with GCM_LOCAL_DIR.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | report the file and the request metadata without uploading; call again without it to upload |
| file_name | string | – | the name the file gets in Chat, with its extension. Omit to keep the name it has on disk |
| local_path | string | yes | the file to send, inside the server's local directory. A bare name is taken as being in that directory; a path outside it is refused |
| space_id | string | yes | the space the file is for, spaces/{id}. The token only works for this space |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | the file's size on disk |
| content_type | string | yes | the MIME type this server derived from the extension, or empty when it could not |
| dry_run | boolean | yes | true when nothing was uploaded |
| file_name | string | yes | the name the file has in Chat |
| rendered_payload | null|object | yes | on a dry run, the metadata that would go with the file; null on a real upload |
| upload_token | null|string | yes | pass this to send_message as attachment_upload_token. Null after a dry run, because nothing was uploaded |
No examples provided.
whoami ~55
Return the authenticated Google user's identity (subject id, email, display name). Useful as a first-call smoke test, and for resolving who "me" is before filtering messages by sender. Reads from the OpenID Connect userinfo endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| display_name | string | yes | the account's display name |
| string | yes | the account's email address | |
| picture_url | string | – | URL of the account's profile picture |
| user_sub | string | yes | the account's stable Google subject id |
No examples provided.
How do I install the io.github.mmedum/google-chat-mcp server?
io.github.mmedum/google-chat-mcp ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 210f2c43afe76892409291a082e7036ce39d1165164c1bd3e02c48982046df2e; the commands to do that are on this page. If it does not match, do not open it.
mcpb · google-chat-mcp_6.1.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
210f2c43afe76892409291a082e7036ce39d1165164c1bd3e02c48982046df2e
macOS / Linux
echo "210f2c43afe76892409291a082e7036ce39d1165164c1bd3e02c48982046df2e google-chat-mcp_6.1.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\google-chat-mcp_6.1.0.mcpb).Hash -eq "210f2c43afe76892409291a082e7036ce39d1165164c1bd3e02c48982046df2e"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the io.github.mmedum/google-chat-mcp server?
io.github.mmedum/google-chat-mcp is listed in the public MCP registry as io.github.mmedum/google-chat-mcp. Google Chat as MCP tools: read, search and write to your spaces, direct messages and sidebar. This page covers its MCPB bundle (https://github.com/mmedum/google-chat-mcp/releases/download/v6.1.0/google-chat-mcp_6.1.0.mcpb).
Is the io.github.mmedum/google-chat-mcp server safe to use?
io.github.mmedum/google-chat-mcp scores 63 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 io.github.mmedum/google-chat-mcp server expose?
io.github.mmedum/google-chat-mcp exposes 49 tools: add_member, add_reaction, create_custom_emoji, create_group_chat, create_section, and 44 more. Their descriptions and schemas cost roughly 7,863 tokens of context every time the server is loaded.
What licence is the io.github.mmedum/google-chat-mcp server under?
io.github.mmedum/google-chat-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.