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.vaadin/docs-mcp

REMOTE · MCP.VAADIN.COM

Provides Vaadin Documentation and help with development tasks

Available components

0 this week 25 Trust /100

Last scanned (1 hour ago)

Scores higher than 10% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Code Search and Documentation

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
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 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
  • 15 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified 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
  • 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
  • 6 Aug 26 0
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Schema quality: unverified → fail ▼ functional
    • Schema quality: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → good ▲ functional
    • First check of Tool coverage: 100 functional
    • New tool “get_component_java_api” functional
    • New tool “get_component_react_api” functional
    • New tool “get_component_styling” functional
    • New tool “get_component_web_component_api” functional
    • New tool “get_components_by_version” functional
    • New tool “get_full_document” functional
    • New tool “get_latest_vaadin_version” functional
    • New tool “get_supported_vaadin_versions” functional
    • New tool “get_theme_css_properties” functional
    • New tool “get_vaadin_primer” functional
    • New tool “search_vaadin_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
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 5 Nov 2026 · Probed https://mcp.vaadin.com/docs/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.vaadin.com CN=YR2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 RSA 4096 SHA256-RSA 523e43f377b00d0b1c1bc6f0448e6f786c1
SANs: mcp.vaadin.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.vaadin.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vaadin.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404
Header Value
strict-transport-security max-age=15552000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.vaadin.com/docs/ HTTP error 404
http (plaintext) http://mcp.vaadin.com/docs/ HTTPS enforced 301 https://mcp.vaadin.com/docs/
MCP tools · 11 exposed · ~1,443 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
get_component_java_api ~122

Returns the Java API documentation for a specific Vaadin component. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button').

NameTypeReqDescription
component_namestringyesThe name of the component (e.g., 'Button', 'button', 'TextField', 'text-field')
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3".

No output schema declared.

No examples provided.

get_component_react_api ~123

Returns the React API documentation for a specific Vaadin component. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button').

NameTypeReqDescription
component_namestringyesThe name of the component (e.g., 'Button', 'button', 'TextField', 'text-field')
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3".

No output schema declared.

No examples provided.

get_component_styling ~134

Returns the styling/theming documentation for a specific Vaadin component. Returns both Java and React styling documentation when available. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button').

NameTypeReqDescription
component_namestringyesThe name of the component (e.g., 'Button', 'button', 'TextField', 'text-field')
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3".

No output schema declared.

No examples provided.

get_component_web_component_api ~135

Returns the Web Component/TypeScript API documentation for a specific Vaadin component by fetching from external TypeScript API docs. The component name can be in any format (e.g., 'Button', 'button', 'vaadin-button').

NameTypeReqDescription
component_namestringyesThe name of the component (e.g., 'Button', 'button', 'TextField', 'text-field')
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3".

No output schema declared.

No examples provided.

get_components_by_version ~73

Returns a comprehensive list of components available in a specific Vaadin version, including component names, React component names, Java class names, and npm packages.

NameTypeReqDescription
versionstringyesThe Vaadin version as a minor version (e.g., '24.8', '24.9', '25.0')

No output schema declared.

No examples provided.

get_full_document ~68

Retrieves complete documentation pages for one or more file paths. Use this when you need full context beyond what search results provide. Provide file_paths only (array).

NameTypeReqDescription
file_pathsarrayyesArray of file paths from search results. Use this to fetch one or more documents in a single call.

No output schema declared.

No examples provided.

get_latest_vaadin_version ~52

Returns the latest stable version of Vaadin as a simple JSON object. This is useful when setting up new projects, checking for updates, or when helping with dependency management. Returns: {version, released}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_supported_vaadin_versions ~67

Returns the latest stable release for each supported Vaadin major version (25, 24, 23, 14, 8, 7) with version number, release date, and whether it requires a commercial license. Useful for migration planning and understanding which versions are available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_theme_css_properties ~163

Returns CSS custom properties documentation for a specific Vaadin theme (Aura, Lumo, or Base styles). Use this to look up the correct CSS variables for the theme the application is using. Base style properties (--vaadin-*) are available in all themes.

NameTypeReqDescription
themestringyesThe theme to get CSS custom properties for: "aura" (Vaadin 25+ default), "lumo" (classic theme), or "base" (base styles available in all themes, Vaadin 25+ only).
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3".

No output schema declared.

No examples provided.

get_vaadin_primer ~164

IMPORTANT: Always use this tool FIRST before working with Vaadin. Returns a comprehensive primer document with current (2025+) information about modern Vaadin development. This addresses common AI misconceptions about Vaadin and provides up-to-date information about Java vs React development models, project structure, components, and best practices. Essential reading to avoid outdated assumptions. For legacy versions (7, 8, 14), returns guidance on version-specific resources.

NameTypeReqDescription
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3". For legacy versions (7, 8, 14), returns guidance on version-specific resources.

No output schema declared.

No examples provided.

search_vaadin_docs ~342

Search Vaadin documentation for relevant information about Vaadin development, components, and best practices. Uses hybrid semantic + keyword search. USE THIS TOOL for questions about: Vaadin components (Button, Grid, Dialog, etc.), TestBench, UI testing, unit testing, integration testing, @BrowserCallable, Binder, DataProvider, validation, styling, theming, security, Push, Collaboration Engine, PWA, production builds, Docker, deployment, performance, and any Vaadin-specific topics. When using this tool, try to deduce the correct development model from context: use "java" for Java-based views, "react" for React-based views, or "common" for both. Use get_full_document with file_paths containing the result's file_path when you need complete context.

NameTypeReqDescription
max_resultsnumber–Maximum number of results to return (default: 5)
max_tokensnumber–Maximum number of tokens to return (default: 1500)
questionstringyesThe search query or question about Vaadin. Will be used to query a vector database with hybrid search (semantic + keyword).
ui_languagestring–The UI implementation language: "java" for Java-based views, "react" for React-based views, or "common" for both. If not specified, the agent should try to deduce the correct language from context or…
vaadin_versionstringyesRequired. Vaadin version: "7", "8", "14", "24", "25.0", "25.1", "25.2", or "25.3".

No output schema declared.

No examples provided.

Install

How do I install the com.vaadin/docs-mcp server?

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

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

What is the com.vaadin/docs-mcp server?

com.vaadin/docs-mcp is listed in the public MCP registry as com.vaadin/docs-mcp. Provides Vaadin Documentation and help with development tasks. This page covers its hosted endpoint (https://mcp.vaadin.com/docs/).

Is the com.vaadin/docs-mcp server safe to use?

com.vaadin/docs-mcp scores 25 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.vaadin/docs-mcp server expose?

com.vaadin/docs-mcp exposes 11 tools: get_vaadin_primer, search_vaadin_docs, get_full_document, get_latest_vaadin_version, get_supported_vaadin_versions, and 6 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.

Does the com.vaadin/docs-mcp server require authentication?

Its publisher declares no required credentials for com.vaadin/docs-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the com.vaadin/docs-mcp server still maintained?

com.vaadin/docs-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.