Agentichtmlexportqa MCP vs Clianythingharness MCP
A side-by-side look at the Agentichtmlexportqa MCP and Clianythingharness MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agentichtmlexportqa MCP for security work over a hosted endpoint; choose Clianythingharness MCP for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agentichtmlexportqa MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_html_export_qa, classify_layout_gap, check_link_summary.
Choose Clianythingharness MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
cli_tool_list, cli_command_run, cli_schema_validate.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | 4 |
| Full listing | View Agentichtmlexportqa MCP | View Clianythingharness MCP |
Tools & capabilities
Agentichtmlexportqa MCP tools 5
check_html_export_qaclassify_layout_gapcheck_link_summaryissue_export_receiptexport_html_qa_log
Clianythingharness MCP tools 4
cli_tool_listcli_command_runcli_schema_validatecli_result_receipt
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agentichtmlexportqa MCP
{
"mcpServers": {
"agentichtmlexportqa-mcp": {
"url": "https://agentichtmlexportqa.clauxel.com/mcp"
}
}
}
Clianythingharness MCP
{
"mcpServers": {
"clianythingharness-mcp": {
"url": "https://clianythingharness.clauxel.com/mcp"
}
}
}
Frequently asked questions
Agentichtmlexportqa MCP is categorized under Security and uses a remote HTTP/SSE transport. Clianythingharness MCP belongs to Security and uses a remote HTTP/SSE transport. Pick Agentichtmlexportqa MCP for security work and Clianythingharness MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agentichtmlexportqa MCP has no declared pricing — check the project's own site. Clianythingharness MCP is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agentichtmlexportqa-mcp and clianythingharness-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentichtmlexportqa MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Clianythingharness MCP has 49/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.