StatelessServer
https://developerknowledge.googleapis.com
Registry code: 98149e0973910ba3
Provides access to Google's public developer documentation.
from a public catalogue that lists it, not from the operator
- endpoint
- https://developerknowledge.googleapis.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is StatelessServer live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is StatelessServer free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does StatelessServer have?
- 3 tools: answer_query, get_documents, search_documents.
- Is StatelessServer safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- search google developer documentation
- get a grounded answer about google apis
- retrieve full google docs pages
- takes → gives
- text → text
- tools
- 3 reads
- note
- documentation mirror
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
answer_query reads auth-required 17h ago
Use answer_query to get a grounded answer to a query about Google developer products. 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. This tool returns the generated answer_text and a list of document names (references) used to generate the answer. Use get_documents with the document names to fetch the entire document content if needed. If you get a 429 out of quota error, use search_documents instead.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Required. The query to answer." } }, "description": "Request message for AnswerQuery." }arguments 13 linesget_documents reads auth-required 17h ago
Use this tool to retrieve the full content of a single document or up to 20 documents in a single call. The document names should be obtained from the `parent` field of results from a call to the `search_documents` tool. Set the `names` parameter to a list of document names.
{ "type": "object", "required": [ "names" ], "properties": { "names": { "type": "array", "items": { "type": "string" }, "description": "Required. The names of the documents to retrieve, as returned by `search_documents`. A maximum of 20 documents can be retrieved in one call. The documents are returned in the same order as the `names` in the request. Format: `documents/{uri_without_scheme}` Example: `documents/docs.cloud.google.com/storage/docs/creating-buckets`" } }, "description": "Request schema for `get_documents`." }arguments 16 linessearch_documents reads auth-required 17h ago
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 This tool returns chunks of text, names, and URLs for matching documents. If the returned chunks are not detailed enough to answer the user's question, use `get_documents` with the `parent` from this tool's output to retrieve the full document content.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Required. The raw query string provided by the user, such as \"How to create a Cloud Storage bucket?\"." } }, "description": "Request schema for `search_documents`. Use the `query` field to search for related Google developer documentation." }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id98149e0973910ba3.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/98149e0973910ba3/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/98149e0973910ba3?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- compute.googleapis.com
- gmailmcp.googleapis.com
- firestore.googleapis.com
- container.googleapis.com
- sqladmin.googleapis.com
- stitch.googleapis.com
- memorystore.googleapis.com
- bigtableadmin.googleapis.com
11 more sit on this domain. All of them.