What agentichtmlexportqa-mcp does
agentichtmlexportqa-mcp MCP server provides a remote interface for agentic HTML export quality assurance. Its documented capabilities cover export checks, layout-gap classification, link-summary checks, export receipts, and QA log generation. The service is intended for workflows that need structured results and evidence suitable for review, rather than an MCP server that runs from source code in the repository.
The repository is a public documentation and directory-submission reference. It does not include the private production implementation, so the available behavior is defined by the hosted service and its published tool list.
How it works
The service is hosted at https://agentichtmlexportqa.clauxel.com/mcp and communicates through MCP over Streamable HTTP. Production requests must include a bearer token in the HTTP authorization header:
Authorization: Bearer <token>
Clients send JSON-RPC requests to the remote endpoint after it has been configured with the endpoint URL and token. Visiting the endpoint without authentication returns a JSON error instead of exposing internal details.
Setup and configuration
agentichtmlexportqa-mcp MCP server requires access to the hosted product rather than a local package installation. The documented setup sequence is:
- Open the product website and select a plan.
- Create or request an API token.
- Add the MCP endpoint to a client that supports Streamable HTTP remote servers.
- Configure the client to send the bearer token with requests.
The product page, pricing information, server card, and MCP endpoint are listed in the project README. No environment variable names or local installation commands are provided in the supplied material.
Tools and capabilities
The published MCP tools are:
check_html_export_qa for HTML export QA checks.
classify_layout_gap for classifying a layout gap.
check_link_summary for checking a link summary.
issue_export_receipt for issuing an export receipt.
export_html_qa_log for exporting an HTML QA log.
Together, these tools support a workflow that checks an export, records relevant results, classifies layout issues, and produces receipts or logs for later review. The supplied documentation does not specify each tool's input schema, output schema, validation rules, or error behavior, so those details should be verified through the service's server card or client tool inspection.
Limitations and notes
The agentichtmlexportqa-mcp MCP server is a paid hosted remote service. A production bearer token is required, and the README does not document a free local mode or a self-hosted deployment. The repository itself cannot be used as the production implementation because it contains documentation and directory-submission material only.
Client compatibility depends on support for remote MCP connections over Streamable HTTP and bearer authentication. The supplied README does not name specific MCP clients. It also does not describe HTML rendering engines, source formats, supported export pipelines, retention policies, service-level guarantees, or the exact contents of receipts and logs. Evaluate those requirements with the provider before adopting it for a specific QA process.