developerknowledge.googleapis.com MCP server
com.googleapis.developerknowledge/mcpdeveloperknowledge.googleapis.comstreamable-httpv1.0.0Scanned
Provides access to Google's public developer documentation.
3 tools: 3 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.
What the developerknowledge.googleapis.com MCP server can do
The developerknowledge.googleapis.com MCP server is published by developerknowledge.googleapis.com, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools read private data (search_documents, answer_query and get_documents).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
answer_queryUse 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 …Reads private dataNo findings
Why it is in this group
- The name "answer_query" says "query": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_documentsUse 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` paramete…Reads private dataNo findings
Why it is in this group
- The name "get_documents" says "get": a word for reading.
What it can reach
- private-dataThe name "get_documents" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
search_documentsUse this tool to find documentation about Google developer products.Reads private data1 finding
Why it is in this group
- The name "search_documents" says "search": a word for reading.
What it can reach
- private-dataThe name "search_documents" says "search" and "document": it reads documents.
Findings
- Info
The description is 2,351 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...urce document resource names (`documents/...`) or corresponding `https://` URIs."
Description, as the server wrote it 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 feature, API, or setting, stop searching (do not fall back to `answer_query`, which uses the same corpus) and inform the user that it is not documented in the official corpus rather than guessing or fabricating details. When answering the user, always cite the authoritative source document resource names (`documents/...`) or corresponding `https://` URIs.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://developerknowledge.googleapis.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://accounts.google.com/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- no
Findings
Matches of fixed checks, with the text they matched.
- Infosearch_documents
The description is 2,351 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...urce document resource names (`documents/...`) or corresponding `https://` URIs."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:answer_queryOnly readsdescription
- Changed:get_documentsOnly readsdescriptioninputSchema
- Changed:search_documentsOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http developerknowledge https://developerknowledge.googleapis.com/mcpclaude mcp add --transport http developerknowledge https://developerknowledge.googleapis.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__developerknowledge__search_documents",
"mcp__developerknowledge__answer_query",
"mcp__developerknowledge__get_documents"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as developerknowledge. Review it before you use it.
Capability tags behind 3 rules
- mcp__developerknowledge__search_documents private-data
- mcp__developerknowledge__answer_query private-data
- mcp__developerknowledge__get_documents private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.googleapis.developerknowledge/mcp/verify?hash=341c52d2a9f9327d7f168c5ea061c8d61be446093bb76d9199a2bf92a4c201d9" | jq -e '.changed == false'Pinned hash 341c52d2a9f9, from Nov 17, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.googleapis.developerknowledge/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.googleapis.developerknowledge/mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.
developerknowledge.googleapis.com MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the developerknowledge.googleapis.com MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.
Can the developerknowledge.googleapis.com MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the developerknowledge.googleapis.com MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the developerknowledge.googleapis.com MCP server have?
- 3 tools: 3 read. search_documents, answer_query and get_documents.
Does the developerknowledge.googleapis.com MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the developerknowledge.googleapis.com MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the developerknowledge.googleapis.com MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.