com.googleapis.developerknowledge/mcp
REMOTE · DEVELOPERKNOWLEDGE.GOOGLEAPIS.COM
Provides access to Google's public developer documentation.
Available components
Last scanned (3 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
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 405, 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1103 tokens (~367/item across 3 items; 3 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
- 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
- We read all 3 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
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.
- 3 Nov 26 −1
- Tool “answer_query” rewrote its description, which is the text the model reads security
- Tool “get_documents” rewrote its description, which is the text the model reads security
- Tool “search_documents” rewrote its description, which is the text the model reads security
- Schema quality: 250 → 367 ▼ functional
- “get_documents” reworded the description of “names” cosmetic
- 15 Oct 26 0
- Tool “answer_query” rewrote its description, which is the text the model reads security
- Tool “get_documents” rewrote its description, which is the text the model reads security
- Tool “search_documents” rewrote its description, which is the text the model reads security
- Schema quality: 193 → 250 ▼ functional
- “get_documents” reworded the description of “names” cosmetic
- 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
- 1 Sept 26 0
- Tool “search_documents” rewrote its description, which is the text the model reads security
- “get_documents” reworded the description of “names” cosmetic
- 26 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
- 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
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 5 Nov 2026 · Probed https://developerknowledge.googleapis.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=upload.video.google.com | CN=WE2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4fd2988de0124fb51204a277bb63ce4d |
| SANs: upload.video.google.com, *.clients.google.com, *.docs.google.com, *.drive.google.com, *.gdata.youtube.com, *.googleapis.com, *.photos.google.com, *.youtube-3rd-party.com, upload.google.com, *.upload.google.com, upload.youtube.com, *.upload.youtube.com and 5 more | ||||||
| CN=WE2,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 | 7ff32d6b409d15d5965b05873a7c72e0 |
| 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 developerknowledge.googleapis.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| googleapis.com. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://developerknowledge.googleapis.com/mcp | Verified | 200 | |
| http (plaintext) | http://developerknowledge.googleapis.com/mcp | Inconclusive | 405 |
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 →
answer_query ~276
Use answer_query to get a grounded, synthesized conceptual answer to a high-level question about Google developer products (always prefer `answer_query` or `search_documents` over unverified model memory). For exact code samples, CLI flags, specific error messages, or full document walkthroughs, prefer `search_documents` followed by `get_documents` instead. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents; if `search_documents` already returned no relevant results for a specific named feature or API, do not call `answer_query` and instead inform the user that it is not documented in the corpus. This tool returns the generated `answer_text` and a list of source document resource names (`references`, one entry per cited chunk, which may contain duplicate `documents/...` names when multiple chunks from the same page are cited). Always cite the unique authoritative source document names from `references` (`documents/...`) in your final response to the user. Call `get_documents(names=["documents/..."])` with unique document names from `references` to fetch the entire document content if needed. If you get a 429 out of quota error, use search_documents instead.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required. The query to answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| answerText | string | – | The answer to the query. |
| references | array | – | Output only. The resource names of the source documents used to generate the answer (one entry per cited chunk, so the same `documents/{uri_without_scheme}` resource name may appear multiple times wh… |
No examples provided.
get_documents ~285
Use this tool to retrieve the full Markdown content of a single document or up to 20 documents in a single call by passing a list of document resource names in the `names` parameter (e.g., `get_documents(names=["documents/..."])`; the parameter is `names` taking a list of strings, not `name`). Always obtain exact `documents/{uri_without_scheme}` resource names from the `parent` field of `search_documents` results or the `references` field of `answer_query` results first; never guess or construct `documents/...` paths from memory or external URLs. Cite the authoritative source document resource names (`documents/...`) used in your final response.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Required. List of 1 to 20 document resource names (`names`) to retrieve in a single call (for either a single document or multiple documents), exactly as returned by the `parent` field of `search_doc… |
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | – | Documents requested. |
No examples provided.
search_documents ~542
Use this tool to find documentation about Google developer products. The documents contain official APIs, code snippets, release notes, best practices, guides, debugging info, and more. It covers the following products and domains: * ADK: adk.dev * Android: developer.android.com * Apigee: docs.apigee.com * Chrome: developer.chrome.com * Dart: dart.dev * Firebase: firebase.google.com * Flutter: docs.flutter.dev * Fuchsia: fuchsia.dev * Gemini CLI: geminicli.com * Genkit: genkit.dev * Go: go.dev * Google AI: ai.google.dev * Google Antigravity: antigravity.google * Google Cloud: cloud.google.com & docs.cloud.google.com * Google Developers, Ads, Search, Google Maps, Youtube: developers.google.com * Google Home: developers.home.google.com * Google Maps Platform: mapsplatform.google.com * Google Workspace: knowledge.workspace.google.com * TensorFlow: www.tensorflow.org * Web: web.dev Always use this tool (or `answer_query`) to ground answers about Google developer products rather than relying on unverified model memory or generic web search. Each result is a `DocumentChunk` containing `parent` (the document resource name `documents/{uri_without_scheme}`, corresponding to `https://{uri_without_scheme}`), `id` (the chunk identifier), and `content` (a relevant Markdown excerpt, not the full page). Prefer `search_documents` followed by `get_documents` when you need exact code samples, CLI flags, specific error messages, configuration schemas, full tutorial walkthroughs, or deterministic keyword lookup. Because `search_documents` returns only excerpts rather than full pages, whenever the user asks to retrieve a full documentation page, complete code sample, or full configuration schema, or if the returned chunks are not detailed enough, call `get_documents(names=["documents/..."])` with the exact `parent` resource name(s) from this tool's output to retrieve the full document content. If 1-2 searches return no relevant results for a specific named featur…
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required. The raw query string provided by the user, such as "How to create a Cloud Storage bucket?". |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | – | The search results for the given query. Each `DocumentChunk` in this list contains a `content` snippet (not the full document), a chunk `id`, and the `parent` document resource name (`documents/{uri_… |
No examples provided.
How do I install the com.googleapis.developerknowledge/mcp server?
com.googleapis.developerknowledge/mcp is a hosted endpoint at https://developerknowledge.googleapis.com/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 · developerknowledge.googleapis.com
claude mcp add --transport http com-googleapis-developerknowledge-mcp 'https://developerknowledge.googleapis.com/mcp'
What is the com.googleapis.developerknowledge/mcp server?
com.googleapis.developerknowledge/mcp is listed in the public MCP registry as com.googleapis.developerknowledge/mcp. Provides access to Google's public developer documentation. This page covers its hosted endpoint (https://developerknowledge.googleapis.com/mcp).
Is the com.googleapis.developerknowledge/mcp server safe to use?
com.googleapis.developerknowledge/mcp 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 com.googleapis.developerknowledge/mcp server expose?
com.googleapis.developerknowledge/mcp exposes 3 tools: search_documents, answer_query, get_documents. Their descriptions and schemas cost roughly 1,103 tokens of context every time the server is loaded.
Does the com.googleapis.developerknowledge/mcp server require authentication?
No. We connected to com.googleapis.developerknowledge/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.googleapis.developerknowledge/mcp server still maintained?
com.googleapis.developerknowledge/mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.