Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

vidit (demo)

REMOTE · MCP.VIDIT.CH

Demo of a Swiss tax service for AI agents: AI-drafted answers, sample quotes, nothing validated yet.

Available components

69 Trust /100

Last scanned (23 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1278 tokens (~319/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Changelog

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 Oct 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 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 18 Oct 26 67

    First indexed and scored.

Diagnostics

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 22 Oct 2026 · Probed https://mcp.vidit.ch/mcp/r

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.vidit.ch CN=YE2,O=Let's Encrypt,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA384 65ffe89c879020242aeca0d6f9fff3125ef
SANs: mcp.vidit.ch
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.vidit.ch. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ch. present 58745 13 Verified
vidit.ch. absent 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.vidit.ch/mcp/r Verified 200
http (plaintext) http://mcp.vidit.ch/mcp/r HTTPS enforced 308 https://mcp.vidit.ch/mcp/r
MCP tools · 4 exposed · ~1,011 tokens

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 →

Tool Tokens
ask ~461

Ask a Swiss tax question for a business or freelancer. Demo: what comes back is a draft written by AI and validated by no professional; do not use it or pass it on. Fill every intake field you can (jurisdiction, category, entity_type, tax_residence, activity_code, revenue_band, vat_status, cross_border, period, already_filed): matching uses these fields only, never the question text. If all fields match an entry, you get the draft entry with its assumptions, sources and validity window. If any field differs, or no entry exists, you get a sample indicative price band and turnaround instead. To see how a review would be quoted, call `ask` again with `request_quotes: true`; the reply says how your principal can hear when the pilot opens, and `status` shows the sample quotes. Free: nothing is charged and nobody is contacted. Do not use for private matters or for countries other than Switzerland, and send no real personal data.

NameTypeReqDescription
categorystringyesTaxonomy path, as search_library returns it (e.g. tax.vat.mwst_registration).
factsobjectyesIntake fields (schema intake.ch-tax.v0). Fill every field you can. Matching uses these only.
jurisdictionstringyes–
languagestring–Language of the answer.
max_budgetobject–Cap for this question, CHF, VAT excluded.
max_waitstring–Longest acceptable turnaround, ISO 8601 duration (e.g. P5D).
principalobject–Public demo: not needed; if sent, it is discarded unread. Send no real data.
questionstring–Public demo: not needed; if sent, it is discarded unread. Send no real data.
request_quotesboolean–true after a library miss: asks the professionals for named quotes. Free; nothing is charged until commit.
sourcestring–Who is asking: agent (software acting for the principal) or human (a person using the operator's interface). Set by the operator's integration; defaults to the operator's declared default.
urgencystring–priority asks for a faster turnaround and may raise the quotes.

No output schema declared.

No examples provided.

commit ~274

Commit to one of the sample quotes returned by `status`: chosen by your principal, or by a rule your principal set explicitly, never by position. Demo: this returns a sample ticket; nothing is ordered, nothing is charged and no professional is contacted. In the pilot this will be the only tool that commits money beyond the plan (the professional's quoted fee, paid to them in full, plus a vidit fee paid by the operator), and only within the budget and policy your principal set.

NameTypeReqDescription
accepted_bystring–Public demo: not needed; if sent, it is discarded unread. Send no real data.
choicestringyesThe quote_id the principal chose, or "none".
chosen_bystringyesprincipal: a person at the principal chose. principal_rule: a rule the principal set or expressly accepted chose.
max_budgetobject–Cap for this question, CHF, VAT excluded.
principal_ruleobject–Required with chosen_by principal_rule: which rule chose, who at the principal set or accepted it, and when.
request_idstringyesThe request_id returned by ask with request_quotes.
reuse_opt_inboolean–The principal allows the professional to turn the review, stripped of identifying facts, into a library entry. Revocable.

No output schema declared.

No examples provided.

search_library ~165

Browse the demo's draft Swiss tax entries before you ask. Free. Each entry was drafted by AI and has been validated by no professional; in the pilot, entries will be validated by a named Treuhänder before they are served. Returns, for each matching entry, the canonical question, its assumptions and the intake fields it matches on. The entry itself comes back only from `ask`, and only when your principal's fields match it. Use it to see which topics exist, or which facts decide an answer, before you collect them.

NameTypeReqDescription
category_prefixstring–e.g. tax.vat
jurisdictionstring––
keywordsstring–Plain words; every word must appear in the entry's question or category.
languagestring––

No output schema declared.

No examples provided.

status ~111

Check a request for quotes or a ticket. Free. After `ask` with `request_quotes`, returns three sample quotes from sample professionals ("SAMPLE Professional 1" to "3"), side by side and in no ranked order, as the pilot will show real ones. Choose among quotes only by a rule your principal set explicitly; otherwise present them to your principal and wait; never choose by position. After `commit`, returns the sample ticket.

NameTypeReqDescription
idstringyesA request_id or a ticket_id.

No output schema declared.

No examples provided.

Install

How do I install the vidit (demo) MCP server?

vidit (demo) is a hosted endpoint at https://mcp.vidit.ch/mcp/r, 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 · mcp.vidit.ch

# add to Claude Code
claude mcp add --transport http ch-vidit-demo 'https://mcp.vidit.ch/mcp/r'
Common questions

What is the vidit (demo) MCP server?

vidit (demo) is an MCP server listed in the public MCP registry as ch.vidit/demo. Demo of a Swiss tax service for AI agents: AI-drafted answers, sample quotes, nothing validated yet. This page covers its hosted endpoint (https://mcp.vidit.ch/mcp/r).

Is the vidit (demo) MCP server safe to use?

vidit (demo) scores 69 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 vidit (demo) MCP server expose?

vidit (demo) exposes 4 tools: ask, search_library, status, commit. Their descriptions and schemas cost roughly 1,011 tokens of context every time the server is loaded.

Does the vidit (demo) MCP server require authentication?

No. We connected to vidit (demo) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the vidit (demo) MCP server still maintained?

vidit (demo) is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.