# VIQTON (remote · viqton.com)

Capability continuity for AI agents: fail over to a verified alternative and get a signed receipt.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `viqton.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/valtris-viqton/viqton.md), [page](https://verifymcp.io/servers/valtris-viqton/viqton)

## Channel facts

- Endpoint: `https://viqton.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 516 tokens (~86/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http valtris-viqton 'https://viqton.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "valtris-viqton": {
      "url": "https://viqton.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "valtris-viqton": {
      "type": "http",
      "url": "https://viqton.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.valtris-viqton]
url = "https://viqton.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "valtris-viqton": {
      "type": "remote",
      "url": "https://viqton.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add valtris-viqton --url 'https://viqton.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  valtris-viqton:
    url: "https://viqton.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "valtris-viqton": {
      "Transport": "http",
      "Url": "https://viqton.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add valtris-viqton -t streamable-http -u 'https://viqton.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "valtris-viqton": {
      "type": "http",
      "url": "https://viqton.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 66, +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.

### 2026-11-19 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-18 (score 64)

First indexed and scored.

## MCP tools (6)

### `viqton_capability_catalog` (~39 tokens)

VIQTON capability catalog

List what VIQTON can run right now, with its limits (target, modes, spend cap, rate limits). Read-only.

### `viqton_run_capability` (~118 tokens)

Run with fallback

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.

Input parameters:

- `consent` (boolean, required): Set to true only after the user agreed to this one run.
- `mode` (string): How to run the capability.

### `viqton_verify_receipt` (~59 tokens)

Verify a receipt

Check a receipt returned by viqton_run_capability: SHA-256 integrity, or the VIQTON self-signature when configured. Not an independent attestation.

Input parameters:

- `receipt` (object, required): The receipt object exactly as returned.

### `viqton_attest_outcome` (~93 tokens)

Independent outcome check (ResultBond)

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.

Input parameters:

- `receipt` (object, required): The receipt object exactly as returned by viqton_run_capability.

### `viqton_continuity` (~42 tokens)

Continuity proof (Lumaion)

VIQTON's latest Lumaion continuity proof (same identity across runtime changes, committed deployment/trust state preserved), verified offline. Read-only.

### `viqton_runtime_trust` (~32 tokens)

Runtime trust status

What this runtime can and cannot prove: signing state, limits, and which integrations are not connected.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/valtris-viqton/viqton#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://viqton.com/mcp
- Website: https://viqton.com/
- Changelog RSS feed: https://verifymcp.io/servers/valtris-viqton/viqton.xml
- Changelog JSON feed: https://verifymcp.io/servers/valtris-viqton/viqton/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/valtris-viqton/viqton.json
- HTML version of this page: https://verifymcp.io/servers/valtris-viqton/viqton
