Web Validator by DigestSEO
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 |
|---|---|
| html.localA | Reads a bounded local HTML or .xhtml file and sends its markup to the W3C Nu HTML Checker. .xhtml files use application/xhtml+xml parsing semantics. Use only files the user is authorized to share. |
| html.urlA | Fetches a bounded public HTTP(S) page, then sends its markup to the W3C Nu HTML Checker. Private, reserved, credentialed, and nonstandard-port destinations are rejected. |
| css.localA | Reads a bounded local CSS file and sends it to the W3C Jigsaw CSS Validator. Use only files the user is authorized to share. |
| seo.metadataB | Analyzes supplied HTML locally for metadata, heading structure, viewport configuration, image alternatives, and Open Graph fields. |
| links.brokenA | Resolves and checks up to 25 public HTTP(S) links in supplied HTML. Redirects are reported but not followed, and response bodies are discarded. |
| schema.markupA | Parses JSON-LD blocks in supplied HTML locally and reports empty blocks or JSON syntax errors. It does not validate vocabulary semantics. |
| report.validationA | Combines W3C HTML/CSS validation, local SEO/accessibility checks, JSON-LD syntax checks, and a bounded public-link check into a Markdown and structured report. |
| screenshot.captureA | Renders a local HTML file or HTTP(S) URL in a sandboxed local Chromium browser and writes PNG screenshots to the requested directory. Downloads the pinned headless browser on first use if it is not already cached. Existing matching files may be replaced. |
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 8 tools
Each tool targets a distinct validation concern (HTML, CSS, links, schema, SEO, screenshots), and the two HTML validators are clearly separated by local vs. URL source. Minor overlap exists between report.validation and the individual tools it aggregates, but the descriptions make the difference explicit (combined report vs. single-purpose check).
All tool names follow a consistent dot-separated pattern where the first segment identifies the resource (html, css, links, schema, seo, report) and the second segment specifies the action or variant (local, url, broken, markup, metadata, validation). This is highly predictable and readable.
Eight tools is well-scoped for a web validation server. Each tool addresses a meaningful aspect of validation or analysis, and none feel redundant or superfluous. The count supports a coherent workflow without overwhelming the agent.
The tool surface covers HTML validation from file and URL, CSS file validation, broken link checking, JSON-LD syntax, SEO metadata analysis, screenshots, and an aggregate report. A minor gap is the lack of a CSS URL validation tool, but the core validation workflows are well covered for the apparent domain.