ViewportWitness by Apex Labs
REMOTE · QA.HONEYGATE.APP · SCANNED SEP 28
Agent website testing: browser QA, visual regression, Markdown extraction, and security checks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (check_page). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 636 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ViewportWitness by Apex Labs MCP server?
ViewportWitness by Apex Labs is a hosted endpoint at https://qa.honeygate.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · qa.honeygate.app
claude mcp add --transport http baffles78-viewport-witness 'https://qa.honeygate.app/mcp'
{
"mcpServers": {
"baffles78-viewport-witness": {
"url": "https://qa.honeygate.app/mcp"
}
}
} {
"servers": {
"baffles78-viewport-witness": {
"type": "http",
"url": "https://qa.honeygate.app/mcp"
}
}
} [mcp_servers.baffles78-viewport-witness] url = "https://qa.honeygate.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"baffles78-viewport-witness": {
"type": "remote",
"url": "https://qa.honeygate.app/mcp",
"enabled": true
}
}
} openclaw mcp add baffles78-viewport-witness --url 'https://qa.honeygate.app/mcp' --transport streamable-http
mcp_servers:
baffles78-viewport-witness:
url: "https://qa.honeygate.app/mcp" {
"McpServers": {
"baffles78-viewport-witness": {
"Transport": "http",
"Url": "https://qa.honeygate.app/mcp"
}
}
} assistant mcp add baffles78-viewport-witness -t streamable-http -u 'https://qa.honeygate.app/mcp'
{
"mcpServers": {
"baffles78-viewport-witness": {
"type": "http",
"url": "https://qa.honeygate.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://qa.honeygate.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=honeygate.app | CN=YE1,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 512a4b5e751a579631e7c2f3a4bb52560e3 |
| SANs: *.honeygate.app, honeygate.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of qa.honeygate.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| honeygate.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qa.honeygate.app/mcp | Verified | 200 | |
| http (plaintext) | http://qa.honeygate.app/mcp | HTTPS enforced | 301 | https://qa.honeygate.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_page ~117
Choose this for broad website testing when the caller wants screenshots, responsive layout checks, accessibility findings, console/network errors, performance evidence, and a release diagnosis across phone portrait, phone landscape, and desktop. For explicit pass/fail assertions use verify_page instead. Costs $0.08 USDC via x402. Requires an x402-aware client to authorise payment; standard AI assistants cannot automatically sign x402.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTPS page URL. Private, loopback, credentialed, and non-HTTPS URLs are rejected. |
No output schema declared.
No examples provided.
compare_page ~133
Choose this for visual regression testing after check_page has produced a completed, unexpired baseline. Compares screenshots and QA evidence, returning pixel-diff percentages, new or resolved accessibility issues, error deltas, performance evidence, and diagnosis. Costs $0.12 USDC via x402. Requires an x402-aware client; standard AI assistants cannot automatically sign x402.
| Name | Type | Req | Description |
|---|---|---|---|
| baselineJobId | string | yes | Completed, unexpired ViewportWitness check job to use as the visual baseline. |
| url | string | yes | Public HTTPS page URL. Private, loopback, credentialed, and non-HTTPS URLs are rejected. |
No output schema declared.
No examples provided.
extract_page ~91
Choose this when an agent needs the readable content of a public webpage as deterministic clean Markdown, without screenshots or browser execution. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| maxOutputTokens | integer | – | Optional approximate output budget from 500 to 12000 tokens. |
| url | string | yes | Public HTTPS page URL. Private, loopback, credentialed, and non-HTTPS URLs are rejected. |
No output schema declared.
No examples provided.
get_report ~63
Retrieve the status or completed QA report for a previously submitted job. Free and read-only. Poll until status is "complete", "failed", or "retryable". No payment required.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | ViewportWitness job UUID returned by a paid tool. |
No output schema declared.
No examples provided.
verify_page ~138
Choose this only when the caller supplies explicit website assertions that need pass/fail results across three viewports. For broad exploratory browser QA use check_page instead. Assertion types: noHorizontalOverflow, noConsoleErrors, textVisible, titleIncludes, selectorExists, selectorVisible. Costs $0.10 USDC via x402. Requires an x402-aware client; standard AI assistants cannot automatically sign x402.
| Name | Type | Req | Description |
|---|---|---|---|
| assertions | array | yes | One to twenty explicit pass/fail assertions to evaluate across all three viewports. |
| url | string | yes | Public HTTPS page URL. Private, loopback, credentialed, and non-HTTPS URLs are rejected. |
No output schema declared.
No examples provided.
web_release_gate ~94
Choose this for a passive website release-security review of headers, cookie flags, mixed content, cross-origin script integrity, and server disclosure. It does not run browser QA, probe the site, execute code, or replace a security audit. Costs $0.05 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTPS page URL. Private, loopback, credentialed, and non-HTTPS URLs are rejected. |
No output schema declared.
No examples provided.
What is the ViewportWitness by Apex Labs MCP server?
ViewportWitness by Apex Labs is an MCP server listed in the public MCP registry as io.github.Baffles78/viewport-witness. Agent website testing: browser QA, visual regression, Markdown extraction, and security checks. This page covers its hosted endpoint (https://qa.honeygate.app/mcp).
Is the ViewportWitness by Apex Labs MCP server safe to use?
ViewportWitness by Apex Labs scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ViewportWitness by Apex Labs MCP server expose?
ViewportWitness by Apex Labs exposes 6 tools: check_page, verify_page, compare_page, extract_page, web_release_gate, get_report. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Does the ViewportWitness by Apex Labs MCP server require authentication?
No. We connected to ViewportWitness by Apex Labs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ViewportWitness by Apex Labs MCP server still maintained?
ViewportWitness by Apex Labs is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.