MCP servers › io.github.4DA-Systems › victauri

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.4DA-Systems/victauri

In-process MCP server for Tauri apps: DOM, IPC with bodies, Rust state, SQLite. Debug builds only. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedPricing: open-source · AI-classifiedversion 0.10.0Ruststandard input/output35 tools

Summary

io.github.4DA-Systems/victauri is a local MCP server listed in the official MCP registry at version 0.10.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 35 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: not an npm or PyPI package
Not ranked by stars: 4 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: Cargo
Repository: public
Tools: 35
Described as changing data: 11 of 35 toolsAI-classified
Mainly works on: files and code on the machine it runs on; a database; accounts and data in outside web servicesAI-classified
Topic: developer-toolsAI-classified
Pricing: open-sourceAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

11 tools are described as changing something (css, fault, input, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 0.10.0, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-18 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.10.0 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

35tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; a database; accounts and data in outside web services.

11 of 35 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

animationon 1 other serverreads or searches
“Animation introspection (no CDP).”
Takes no inputs.
app_infoon 3 other serversreads or searches
“Get comprehensive app info: Tauri config (identifier, product name, version), app directory paths (data, config, log, local_data), process environment variables, and database files found in app direc…”
Takes no inputs.
app_stateon 2 other serversreads or searches
“Read application-defined backend state via a registered probe.”
Takes no inputs.
assert_semanticcalculates or converts
“Run a semantic assertion: evaluate a JS expression and check the result against an expected condition.”
Takes no inputs.
check_ipc_integrityreads or searches
“Check IPC round-trip integrity: find stale (stuck) pending calls and errored calls.”
Takes no inputs.
csscreates or changes datadescribed as changing data
“CSS injection.”
Takes no inputs.
detect_ghost_commandsreads or searches
“Detect ghost commands (frontend calls with no backend handler) by IPC OUTCOME, not by guessing from Victauri's registry.”
Takes no inputs.
dom_snapshoton 1 other serverreads or searches
“Get the DOM snapshot with stable ref handles.”
Takes no inputs.
eval_json 1 other serverruns code or commandsdescription does not say
“Evaluate JavaScript in the Tauri webview and return the result.”
Takes no inputs.
explainon 29 other serversreads or searches
“Correlate recent activity across all layers into a coherent narrative.”
Takes no inputs.
faultruns code or commandsdescribed as changing data
“Probe a backend command handler under failure by faulting it for chaos engineering.”
Takes no inputs.
find_elementson 4 other serversreads or searches
“Search for elements by text, role, test_id, CSS selector (via `css` or `selector` param), or accessible name without a full snapshot.”
Takes no inputs.

Show 23 more tools

get_diagnosticson 6 other serversreads or searches
“Run environment diagnostics: IPC capture completeness (`info.ipc_capture`: the Tauri IPC transport in use — fetch, or the postMessage fallback Tauri switches to after a custom-protocol failure — and …”
Takes no inputs.
get_memory_statson 1 other serverreads or searches
“Get real-time process memory statistics from the OS (working set, page file usage).”
Takes no inputs.
get_plugin_inforeads or searches
“Inspect the Victauri plugin's own configuration: port, enabled/disabled tools, command filters, privacy settings, capacities, and version.”
Takes no inputs.
get_registryon 3 other serversreads or searches
“List or search all registered Tauri commands with their argument schemas.”
Takes no inputs.
inputon 2 other serversdescribed as changing data
“Text and keyboard input.”
Takes no inputs.
inspecton 26 other serversreads or searches
“CSS and visual inspection.”
Takes no inputs.
interacton 5 other serverscontrols a browser or desktopdescribed as changing data
“DOM element interactions.”
Takes no inputs.
introspectreads or searches
“Deep backend introspection — command profiling, IPC contract testing, coverage, startup timing, capability auditing, database diagnostics, process enumeration, and event bus monitoring.”
Takes no inputs.
invoke_commandruns code or commandsdescribed as changing data
“Invoke a registered Tauri command via IPC, just like the frontend would.”
Takes no inputs.
list_app_dirreads or searches
“List files in the app's data, config, log, or local_data directories.”
Takes no inputs.
logson 11 other serversreads or searches
“Application logs and monitoring.”
Takes no inputs.
navigateon 18 other serverscontrols a browser or desktopdescribed as changing data
“Navigation and dialog control.”
Takes no inputs.
query_dbon 2 other serversruns code or commands
“Execute a bounded, read-only SQL query against a SQLite database in the app's data directory.”
Takes no inputs.
read_app_fileon 2 other serversreads or searches
“Read a file from the app's data, config, log, or local_data directory.”
Takes no inputs.
recordingon 1 other serverdoes something elsedescribed as changing data
“Time-travel recording.”
Takes no inputs.
resolve_commandreads or searches
“Resolve a natural language query to matching Tauri commands.”
Takes no inputs.
routeon 22 other serverscreates or changes datadescribed as changing data
“Network request interception (Playwright route() equivalent, no CDP).”
Takes no inputs.
screenshoton 82 other serversreads or searches
“Capture a screenshot of a Tauri window as a base64-encoded PNG image.”
Takes no inputs.
storageon 3 other serverscreates or changes datadescribed as changing data
“Browser storage operations.”
Takes no inputs.
traceon 10 other serversdoes something elsedescribed as changing data
“Screencast / visual trace (no CDP).”
Takes no inputs.
verify_statecalculates or converts
“Compare frontend state (evaluated via JS expression) against backend state to detect divergences.”
Takes no inputs.
wait_foron 16 other servers
“Wait for a condition to be met.”
Takes no inputs.
windowon 2 other serverscontrols a browser or desktopdescribed as changing data
“Window management.”
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 35 tools
Says what it returns: 91% of 34 tools
States limits, defaults or errors: 9% of 33 tools
Says when to use it: 11% of 35 tools
Items covered per tool: 2.2 of 4 on average

Counted from the listing

Parameters with a description: its tools take no parameters
Tools with a description: 100% of 35
Typical description length: 517 characters

The tool set

Counted from the listing

Tools: 35
Size of the list: about 5,166 tokens for an agent to load (characters ÷ 4)
Naming: 19 of 35 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 35 of 35 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

No config: no ready-made command for the Cargo crate; use the publisher's instructions.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Repository github.com/4DA-Systems/victauri	Opens publicly	matches	api.github.com · 2026-10-22

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.4DA-Systems · 2 servers
GitHub owner: an organization (4DA-Systems)

Repository: github.com/4DA-Systems/victauri
Stars: 4
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-22; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

Not ranked by downloads: not an npm or PyPI package
Not ranked by stars: 4 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.4DA-Systems/victauri

Answered from the data above

Is io.github.4DA-Systems/victauri safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 11 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.4DA-Systems/victauri free to use?

Its website (4da-systems.github.io/Victauri/) describes a open-source pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.github.4DA-Systems/victauri been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.4DA-Systems/victauri do?

It lists 35 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, run code or commands, control a browser or desktop, calculate or convert and do something else. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.4DA-Systems/victauri change or delete data?

11 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.4DA-Systems/victauri publish a security policy?

Yes: its repository has a public security policy (github.com/4da-systems/victauri/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.4DA-Systems/victauri?

In github.com/4DA-Systems/victauri, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.kivanccakmak/yaverYaveralso has tools that calculates or converts, controls a browser or desktop, creates or changes data, runs code or commands, does something else, reads or searchescompare with this one
io.github.yaver-io/yaverYaveralso has tools that calculates or converts, controls a browser or desktop, creates or changes data, runs code or commands, does something else, reads or searchescompare with this one
io.github.tomyud1/godot-mcpalso has tools that calculates or converts, controls a browser or desktop, creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.HaD0Yun/gopeakalso has tools that calculates or converts, controls a browser or desktop, creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.SummerEngine/summerSummer Enginealso has tools that controls a browser or desktop, creates or changes data, runs code or commands, does something else, reads or searchescompare with this one
io.github.SupportPages-io/wtfmWTFMalso has tools that calculates or converts, controls a browser or desktop, creates or changes data, runs code or commands, reads or searchescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
94 msConnected after 0 redirects.
Read the inventory: 35 tools, 0 resources, 0 prompts.
187,788 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

open-source

read from 4da-systems.github.io/Victauri/ · 2026-10-23

“Victauri is open source (Apache-2.0) and built by 4DA Systems, which uses it to test its own Tauri app.”

Programming language

Rust

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

cargo

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here

Integrity hash

does not apply

package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here

Signature / provenance

does not apply

package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here

Dependency advisories

not checked

only npm and PyPI packages are audited

Popularity

does not apply

package ecosystem not queried by this layer (cargo); only npm and PyPI are supported here

Publisher signals

owner: an organization · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-22

Maintenance

active

api.github.com · 2026-10-22

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.4DA-Systems/victauri: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.4DA-Systems/victauri

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.4DA-Systems/victauri)](https://protocolprobe.com/mcp/servers/io.github.4DA-Systems/victauri)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology