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.metadataA | Audits supplied HTML offline for on-page SEO metadata, headings, viewport, image alternatives, and Open Graph issues. Use for a quick on-page check; use html.local/html.url for W3C HTML validation, schema.markup for JSON-LD syntax, or report.validation for a combined local-file report. |
| 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 has a clearly distinct purpose: local CSS validation, local HTML validation, URL HTML validation, SEO metadata audit, broken-link checking, JSON-LD syntax checking, combined reporting, and screenshot capture. The aggregate report.validation tool overlaps with several others, but its description clearly distinguishes it as a combined workflow.
All eight tools use a consistent lowercase dot-separated namespace pattern (resource.action or resource.scope), such as css.local, html.url, links.broken, and report.validation. The convention is predictable throughout the set.
Eight tools is well-scoped for a web validation and audit suite. Each tool covers a meaningful validation or reporting capability without excessive fragmentation.
The surface covers the core domain well: HTML/CSS validation, SEO checks, JSON-LD syntax, broken links, screenshots, and a combined report. Minor gaps exist, such as no direct remote CSS URL validation, but most workflows can be handled or worked around.