Partly liveWhat works today is listed first. What is still to come is listed under Not yet.

VZN Connect

Check a desk connection before calling its tools.

Your desk is an MCP server, and it reaches other servers. Connect an AI client to your desk over MCP with a scoped key, and allowlist the tools your agents may call on other MCP servers.

See it work

One request, one answer.

Example · scriptedPOST /mcp

Request

{"jsonrpc":"2.0","id":1,"method":"ping"}

Response

{"jsonrpc":"2.0","id":1,"result":{}}

Use a scoped connection key. The example checks connectivity.

How it goes

Three steps.

  1. Choose a deskUse a scoped connection key.
  2. Ping the serverSend a ping over the authenticated connection.
  3. Check the replyMatch the response ID to the request.
Evidence

What we can show, and where it comes from.

Successful ping
An empty result with the same request IDSource: network/src/mcp-server/handler.ts
Example · scripted
job_01HX2 billing.credit · 200 · R 35.00 · receipt kept

Every action leaves a receipt: who approved it, when, and the proof that it happened. Nothing is billed without an approval.

Proposed pricing

Your desk is an MCP server; scoped keys are the only way in.

Self-hosted

R0 / one-time

Run the desk MCP server yourself with scoped connection keys.

  • Streamable HTTP MCP server
  • Scoped keys
  • Tool allowlist

Team

Most common

R150 / month

Shared connectors and an allowlist per agent.

  • Shared connector catalogue
  • Per-agent allowlists
  • Usage history

Enterprise

Talk to us

OAuth for remote web clients and private connectors.

  • OAuth
  • Private connectors
  • Talk to us
Status

What runs today, and what is still open.

Works today

  • The desk as a Streamable HTTP MCP server with scoped connection keys
  • A connector catalogue with an allowlist per agent

Not yet

  • Live connectors: the catalogue entries are previews
  • OAuth for remote web clients

Connect it, read the docs, start.