goog.workspace-developer/developer-tools
REMOTE · WORKSPACE-DEVELOPER.GOOG · SCANNED SEP 24
Provides tools for searching Google Workspace documentation and much more.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 129 tokens (~64/item across 2 items; 2 tools + 0 resources), lean.Pass
- 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
- Structured output schemas are declared (50% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the goog.workspace-developer/developer-tools MCP server?
goog.workspace-developer/developer-tools is a hosted endpoint at https://workspace-developer.goog/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 · workspace-developer.goog
claude mcp add --transport http goog-workspace-developer-developer-tools 'https://workspace-developer.goog/mcp'
{
"mcpServers": {
"goog-workspace-developer-developer-tools": {
"url": "https://workspace-developer.goog/mcp"
}
}
} {
"servers": {
"goog-workspace-developer-developer-tools": {
"type": "http",
"url": "https://workspace-developer.goog/mcp"
}
}
} [mcp_servers.goog-workspace-developer-developer-tools] url = "https://workspace-developer.goog/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"goog-workspace-developer-developer-tools": {
"type": "remote",
"url": "https://workspace-developer.goog/mcp",
"enabled": true
}
}
} openclaw mcp add goog-workspace-developer-developer-tools --url 'https://workspace-developer.goog/mcp' --transport streamable-http
mcp_servers:
goog-workspace-developer-developer-tools:
url: "https://workspace-developer.goog/mcp" {
"McpServers": {
"goog-workspace-developer-developer-tools": {
"Transport": "http",
"Url": "https://workspace-developer.goog/mcp"
}
}
} assistant mcp add goog-workspace-developer-developer-tools -t streamable-http -u 'https://workspace-developer.goog/mcp'
{
"mcpServers": {
"goog-workspace-developer-developer-tools": {
"type": "http",
"url": "https://workspace-developer.goog/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 +51
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 16 Sept 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 6 Aug 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: 39 → 64 ▼ functional
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 50 functional
- First check of Tool coverage: 100 functional
- Schema quality: poor → good functional
- New tool “fetch_workspace_docs” functional
- New tool “search_workspace_docs” functional
- 31 Jul 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
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 Sept 2026 · Probed https://workspace-developer.goog/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=workspace-developer.goog | CN=WR3,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | RSA 2048 | SHA256-RSA | 326b6a74e09ab1331006cfc990a8cffc |
| SANs: workspace-developer.goog | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of workspace-developer.goog. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| goog. | present | 8029 | 8 | Verified |
| workspace-developer.goog. | 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://workspace-developer.goog/mcp | Verified | 200 | |
| http (plaintext) | http://workspace-developer.goog/mcp | Inconclusive | 406 |
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 →
fetch_workspace_docs Fetch Google Workspace documentation page ~49
Fetches the content of a Google Workspace documentation page such as those returned by the `search_workspace_docs` tool.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the Google Workspace documentation page to fetch. |
No output schema declared.
No examples provided.
search_workspace_docs Search Google Workspace Documentation ~41
Searches the latest official Google Workspace documentation, including API references, conceptual guides, tutorials, and code examples.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The query to search. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | The search results. |
| summary | string | yes | The summary of the search results. |
No examples provided.
What is the goog.workspace-developer/developer-tools MCP server?
goog.workspace-developer/developer-tools is an MCP server listed in the public MCP registry as goog.workspace-developer/developer-tools. Provides tools for searching Google Workspace documentation and much more. This page covers its hosted endpoint (https://workspace-developer.goog/mcp).
Is the goog.workspace-developer/developer-tools MCP server safe to use?
goog.workspace-developer/developer-tools scores 79 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 goog.workspace-developer/developer-tools MCP server expose?
goog.workspace-developer/developer-tools exposes 2 tools: search_workspace_docs, fetch_workspace_docs. Their descriptions and schemas cost roughly 90 tokens of context every time the server is loaded.
Does the goog.workspace-developer/developer-tools MCP server require authentication?
No. We connected to goog.workspace-developer/developer-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the goog.workspace-developer/developer-tools MCP server still maintained?
goog.workspace-developer/developer-tools is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.