6Frame Verify
REMOTE · SITEVERIFY.DEV
Pre-launch website QA in 60s via real Chromium. $3/check; agents can pay in USDC (x402).
Available components
Last scanned (4 hours ago)
Scores higher than 8% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Testing and QA
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 14 Oct 26 −38
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
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 5 Nov 2026 · Probed https://siteverify.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of siteverify.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| siteverify.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://siteverify.dev/mcp | Unreachable | ||
| http (plaintext) | http://siteverify.dev/mcp | HTTPS enforced |
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 →
verify_buy_credits ~56
Get a Stripe checkout_url for a credit pack: credit_pack_9 ($9 → $10) or credit_pack_29 ($29 → $35). A human pays. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| pack | string | – | – |
No output schema declared.
No examples provided.
verify_check_site ~246
Run a pre-launch QA check on a live site: real Chromium on desktop + mobile, HTTP status, broken links, title/meta/H1, Open Graph, mobile overflow, console errors, screenshots. Uses today's free Quick Check, else prepaid credit, else returns payment options: a Stripe checkout_url for a human ($3 Quick / $12 Full) and, when available, x402 USDC-on-Base details (accepts[]) so an agent can pay itself — retry with x402_payment. No API key is needed for the x402 path.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | – | Optional: what the site must do |
| paths | array | – | website_full only: extra paths like /pricing |
| pay_with | string | – | – |
| required_ctas | array | – | – |
| required_terms | array | – | – |
| sku | string | – | – |
| url | string | yes | Public https:// URL of the site to check |
| x402_payment | string | – | Optional: base64 x402 X-PAYMENT payload (EIP-3009 USDC authorization) for the accepts[] requirement returned by a previous call. Pays for this check with no human. |
No output schema declared.
No examples provided.
verify_get_capabilities ~62
Free, no key. What 6Frame Verify checks, prices (Quick $3, Full $12, credit packs $9→$10 and $29→$35), free tier (1 Quick Check/day per key) and how to sign up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_get_credits ~24
Prepaid credit balance and today's free-check usage. Requires API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_get_job ~40
Status of a check (queued, running, completed, completed_with_warnings, failed_platform). Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
verify_get_report ~40
Signed report for a finished check: score, decision, findings with fixes, report page link. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
verify_quote ~59
Free, no key. Price for checking a URL (website_quick = 1 page, website_full = up to 10 pages).
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | – | – |
| url | string | yes | Public https:// URL of the site to check |
No output schema declared.
No examples provided.
verify_signup ~52
Free, no key. Create an API key from an email address (shown once). Includes 1 free Quick Check per day. Rate limited.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email of the human who owns this key |
No output schema declared.
No examples provided.
How do I install the 6Frame Verify MCP server?
6Frame Verify is a hosted endpoint at https://siteverify.dev/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 · siteverify.dev
claude mcp add --transport http bret1976-6frame-verify 'https://siteverify.dev/mcp'
What is the 6Frame Verify MCP server?
6Frame Verify is an MCP server listed in the public MCP registry as io.github.bret1976/6frame-verify. Pre-launch website QA in 60s via real Chromium. $3/check; agents can pay in USDC (x402). This page covers its hosted endpoint (https://siteverify.dev/mcp).
Is the 6Frame Verify MCP server safe to use?
6Frame Verify scores 23 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 6Frame Verify MCP server expose?
6Frame Verify exposes 8 tools: verify_get_capabilities, verify_signup, verify_quote, verify_check_site, verify_get_job, and 3 more. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.
Does the 6Frame Verify MCP server require authentication?
Its publisher declares no required credentials for 6Frame Verify. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the 6Frame Verify MCP server still maintained?
6Frame Verify is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.