MCP Web Validator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| seo.metadataA | Inspects supplied HTML locally for title, meta description, h1 headings, and image alt attributes. |
| schema.markupB | Parses JSON-LD script blocks in supplied HTML and reports empty blocks or JSON syntax errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools target clearly different validation areas: SEO HTML metadata versus JSON-LD schema markup. There is no overlap in purpose, so an agent can easily choose between them.
Both tool names follow the same namespace.action convention: seo.metadata and schema.markup. The pattern is predictable and consistent across the set.
Two tools is borderline thin for a server called 'MCP Web Validator,' which implies broader validation coverage. The count is reasonable only if the server is intentionally limited to SEO/schema checks.
For a web validator, the surface has significant gaps: it lacks checks for links, accessibility, performance, canonical tags, Open Graph, robots directives, and deeper schema validation. It covers a narrow slice of SEO/schema markup inspection rather than a complete web validation lifecycle.