Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.googleapis.design/mcp

REMOTE · DESIGN.GOOGLEAPIS.COM

Provides UX capabilities to enhance the design output and understanding of AI systems.

0 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 843 tokens (~168/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 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
  • 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
Diagnostics

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 21 Nov 2026 · Probed https://design.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 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 9e681c42d24198f809a4b6d0e53428ab
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 design.googleapis.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
googleapis.com. No DS 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://design.googleapis.com/mcp Verified 200
http (plaintext) http://design.googleapis.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~843 tokens

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 →

Tool Tokens
describe_font ~82

Describes a font family in detail, including its look and feel, supported styles, weights and how to use it.

NameTypeReqDescription
fontFamilystringyesRequired. The full name of the font family to describe. Example: "Roboto", "Noto Sans".
platformstringyesRequired. The platform in which the font family is going to be used.
NameTypeReqDescription
descriptionstring–Description of the font family, in Markdown format.
errorHelpstring–Optional. Contextual help text if the font family name was not found or is invalid.
featuresstring–Supported features of the font family such as weight, style and variable axes, if available, in Markdown format.
guidancestring–Guidance on how to effectively use the font family, if available.
languagesarray–List of supported language and script in BCP47 format.

No examples provided.

generate_color_scheme ~427

Generates a Material Design color scheme from one or more key colors. Always use this when you need to create a color scheme for an application. The input is one or more named colors in hex format, and the output is a color scheme with a map of color role names to colors in hex format.

NameTypeReqDescription
backgroundKeystring–Optional. The neutral key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CSS color name.
contrastLevelnumber–Optional. The contrast level of the color scheme. Values range from -1 (minimum contrast) to 1 (maximum contrast). 0 represents standard contrast (i.e. the design as specified).
optionalSchemeVariantstring–Optional. If only the primary key color is supplied, this will select which variant of the color scheme to use. If only the primary key color is supplied and this is not set, it defaults to "TONAL_SP…
optionalThemestring–Optional. Whether to generate a light or dark theme. If unspecified, and a background key is supplied, it will be inferred from that. If not, it will default to light theme.
primaryKeystringyesRequired. The primary key color used as the main seed for the scheme. Can be a 6-character hex code (e.g., "#4285F4" or "4285F4"), or any standard CSS color name (e.g., "blue").
secondaryKeystring–Optional. The secondary key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CSS color name.
tertiaryKeystring–Optional. The tertiary key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CSS color name.
NameTypeReqDescription
colorScheme––The generated color scheme.

No examples provided.

icons_instructions ~27

Provides essential and critical instructions on how to use Material Icons and Material Symbols efficiently on Web.

Input schema present but exposes no named parameters.

NameTypeReqDescription
instructionsstring–Instructions on how to use Google Material Icons and Google Symbols efficiently.

No examples provided.

search_fonts ~119

Finds appropriate fonts matching categories and/or languages.

NameTypeReqDescription
categoriesarray–Optional. One or more categories to filter font families
languagesarray–Optional. Language tags in BCP47 format to filter fonts that support specific scripts (e.g., "en_Latn", "zh_Hans").
platformstringyesRequired. The platform in which the font family is going to be used.
sortstring–Optional. The sort order for the returned font families. Defaults to POPULARITY_DESCENDING if unspecified.
NameTypeReqDescription
errorHelpstring–Optional. Contextual help text or error descriptions if the query failed.
fontFamiliesarray–The names of font families that match the search criteria (e.g., "Roboto", "Open Sans").

No examples provided.

search_icons ~188

Finds appropriate Material Design icons matching keywords that describe their usage, style, or shape.

NameTypeReqDescription
iconSetstring–Optional. The icon set to search within (e.g., "Material Symbols", "Material Icons"). If omitted, the default icon set of the environment is used.
tagsarrayyesRequired. A list of semantic keywords or metadata tags that describe the desired icon's visual or functional properties. If possible, specify at least three tags to describe usage, style, and shape.…
NameTypeReqDescription
iconsarray–The names of icons that match the provided tags, ordered by relevance.

No examples provided.

Install

How do I install the com.googleapis.design/mcp server?

com.googleapis.design/mcp is a hosted endpoint at https://design.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 · design.googleapis.com

# add to Claude Code
claude mcp add --transport http com-googleapis-design-mcp 'https://design.googleapis.com/mcp'
Common questions

What is the com.googleapis.design/mcp server?

com.googleapis.design/mcp is listed in the public MCP registry as com.googleapis.design/mcp. Provides UX capabilities to enhance the design output and understanding of AI systems. This page covers its hosted endpoint (https://design.googleapis.com/mcp).

Is the com.googleapis.design/mcp server safe to use?

com.googleapis.design/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.design/mcp server expose?

com.googleapis.design/mcp exposes 5 tools: generate_color_scheme, search_icons, icons_instructions, search_fonts, describe_font. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

Does the com.googleapis.design/mcp server require authentication?

No. We connected to com.googleapis.design/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.googleapis.design/mcp server still maintained?

com.googleapis.design/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.googleapis.design/mcp server?

VerifyMCP ran 12 checks on com.googleapis.design/mcp, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.googleapis.design/mcp: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.