Skip to content

VIQTON MCP server

io.github.valtris/viqtonvaltrisstreamable-httpv1.4.0Scanned

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

6 tools: 1 do something that can't be undone, 4 change things and 1 only read.

Tools: 0 delete, 1 irreversible, 4 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 1
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VIQTON MCP server can do

The VIQTON MCP server is published by the GitHub account valtris. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (viqton_attest_outcome) and create or change data (4 tools: viqton_run_capability, viqton_verify_receipt, viqton_continuity and viqton_runtime_trust), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (viqton_run_capability, viqton_attest_outcome and viqton_continuity); 1 tool can send data out of your system (viqton_attest_outcome).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Can't be undone 1Claude Code: ask
  • viqton_attest_outcomeSend a receipt from viqton_run_capability to ResultBond's independent evaluator (policy rb.capability-outcome.v0.1).Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "send": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "viqton_attest_outcome" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 4Claude Code: ask
  • viqton_continuityVIQTON's latest Lumaion continuity proof (same identity across runtime changes, committed deployment/trust state preserved), verified offline.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    VIQTON's latest Lumaion continuity proof (same identity across runtime changes, committed deployment/trust state preserved), verified offline. Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • viqton_run_capabilityRun the public DNS capability through VIQTON.Reads text others write1 finding

    Why it is in this group

    • The name "viqton_run_capability" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "viqton_run_capability" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "viqton_run_capability" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • viqton_runtime_trustWhat this runtime can and cannot prove: signing state, limits, and which integrations are not connected.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What this runtime can and cannot prove: signing state, limits, and which integrations are not connected.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • viqton_verify_receiptCheck a receipt returned by viqton_run_capability: SHA-256 integrity, or the VIQTON self-signature when configured.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check a receipt returned by viqton_run_capability: SHA-256 integrity, or the VIQTON self-signature when configured. Not an independent attestation.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • viqton_capability_catalogList what VIQTON can run right now, with its limits (target, modes, spend cap, rate limits).No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List what VIQTON can run right now, with its limits (target, modes, spend cap, rate limits). Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:20 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://viqton.com/mcp: tools/list returned 6 tools to an anonymous client, including viqton_attest_outcome (irreversible), viqton_run_capability (write), viqton_verify_receipt (write), viqton_continuity (write), viqton_runtime_trust (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "viqton_run_capability" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "viqton_run_capability" says "run": a word for a change.

    What this check looks for
  • The server marks "viqton_attest_outcome" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http viqton https://viqton.com/mcp
claude mcp add --transport http viqton https://viqton.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__viqton__viqton_capability_catalog"
    ],
    "ask": [
      "mcp__viqton__viqton_run_capability",
      "mcp__viqton__viqton_verify_receipt",
      "mcp__viqton__viqton_attest_outcome",
      "mcp__viqton__viqton_continuity",
      "mcp__viqton__viqton_runtime_trust"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as viqton. Review it before you use it.

Capability tags behind 3 rules
  • mcp__viqton__viqton_run_capability untrusted-input
  • mcp__viqton__viqton_attest_outcome untrusted-input, outbound
  • mcp__viqton__viqton_continuity untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.valtris/viqton/verify?hash=839783374ab62097b43ae69cea294516d6a17a6334a0480d81b375ad2fac04ee" | jq -e '.changed == false'

Pinned hash 839783374ab6, from Nov 18, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.valtris/viqton/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.valtris/viqton
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.valtris/viqton.svg)](https://radar.anlyon.com/servers/io.github.valtris/viqton)

Source: MCP Registry. Synced Nov 18, 2026, 21:18 UTC.

VIQTON MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VIQTON MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VIQTON MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the VIQTON MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: viqton_attest_outcome.

What tools does the VIQTON MCP server have?

6 tools: 1 irreversible, 4 write, 1 read. viqton_attest_outcome, viqton_run_capability, viqton_verify_receipt, viqton_continuity, viqton_runtime_trust and viqton_capability_catalog.

Does the VIQTON MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VIQTON MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): viqton_attest_outcome.

Has the VIQTON MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.