VIQTON
REMOTE · VIQTON.COM
Capability continuity for AI agents: fail over to a verified alternative and get a signed receipt.
Available components
Last scanned (20 hours ago)
Scores higher than 51% of remote servers
Reachable. Last reached 21 Nov 2026.
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 not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 516 tokens (~86/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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "viqton_attest_outcome" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 7 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Nov 26 64
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 21 Nov 2026 · Probed https://viqton.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.viqton.com | CN=YR2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 50cca444c99c7a7931a500ff162532dc863 |
| SANs: *.viqton.com, viqton.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of viqton.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| viqton.com. | No DS | 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=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://viqton.com/mcp | Verified | 200 | |
| http (plaintext) | http://viqton.com/mcp | HTTPS enforced | 308 | https://viqton.com/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 →
viqton_attest_outcome Independent outcome check (ResultBond) ~93
Send a receipt from viqton_run_capability to ResultBond's independent evaluator (policy rb.capability-outcome.v0.1). It re-queries public DNS itself and signs PASS/FAIL/INCONCLUSIVE; VIQTON verifies that signature against a pinned evaluator key. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | The receipt object exactly as returned by viqton_run_capability. |
No output schema declared.
No examples provided.
viqton_capability_catalog VIQTON capability catalog ~39
List what VIQTON can run right now, with its limits (target, modes, spend cap, rate limits). Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
viqton_continuity Continuity proof (Lumaion) ~42
VIQTON's latest Lumaion continuity proof (same identity across runtime changes, committed deployment/trust state preserved), verified offline. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
viqton_run_capability Run with fallback ~118
Run the public DNS capability through VIQTON. "normal": Cloudflare first, Google if it fails. "inject_primary_unavailable": simulate a Cloudflare outage and watch VIQTON hand over to Google (real query). "dual_observe": query both and cross-check. Read-only, fixed target example.com, $0. Requires consent=true from the user.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | Set to true only after the user agreed to this one run. |
| mode | string | – | How to run the capability. |
No output schema declared.
No examples provided.
viqton_runtime_trust Runtime trust status ~32
What this runtime can and cannot prove: signing state, limits, and which integrations are not connected.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
viqton_verify_receipt Verify a receipt ~59
Check a receipt returned by viqton_run_capability: SHA-256 integrity, or the VIQTON self-signature when configured. Not an independent attestation.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | The receipt object exactly as returned. |
No output schema declared.
No examples provided.
How do I install the VIQTON MCP server?
VIQTON is a hosted endpoint at https://viqton.com/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 · viqton.com
claude mcp add --transport http valtris-viqton 'https://viqton.com/mcp'
What is the VIQTON MCP server?
VIQTON is an MCP server listed in the public MCP registry as io.github.valtris/viqton. Capability continuity for AI agents: fail over to a verified alternative and get a signed receipt. This page covers its hosted endpoint (https://viqton.com/mcp).
Is the VIQTON MCP server safe to use?
VIQTON scores 66 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 VIQTON MCP server expose?
VIQTON exposes 6 tools: viqton_capability_catalog, viqton_run_capability, viqton_verify_receipt, viqton_attest_outcome, viqton_continuity, viqton_runtime_trust. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Does the VIQTON MCP server require authentication?
No. We connected to VIQTON without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VIQTON MCP server still maintained?
VIQTON is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the VIQTON MCP server?
VerifyMCP ran 12 checks on VIQTON, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VIQTON: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.