Vtessera

Name: Vtessera
Author: douglasdemaio

by douglasdemaioversion 0.1.0i★ –iComputer or cloud

Registry nameio.github.douglasdemaio/vtessera

Install

Overview

Description from the maker (original English)

Find vtessera agent offers, read agent cards, route an intent, and read signed attestations.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: VTESSERA_BASE_URL

You need

Runs in the cloudNothing to install; it connects over the internet
DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://vtessera-mcp.fly.dev/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vtessera": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VTESSERA_BASE_URL",
        "ghcr.io/douglasdemaio/vtessera-mcp:0.1.0"
      ],
      "env": {
        "VTESSERA_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http vtessera https://vtessera-mcp.fly.dev/mcp

Or run it on your computer

claude mcp add vtessera --env VTESSERA_BASE_URL=your-value -- docker run -i --rm -e VTESSERA_BASE_URL ghcr.io/douglasdemaio/vtessera-mcp:0.1.0

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vtessera": {
      "url": "https://vtessera-mcp.fly.dev/mcp"
    }
  }
}

Or run it on your computer

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vtessera": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VTESSERA_BASE_URL",
        "ghcr.io/douglasdemaio/vtessera-mcp:0.1.0"
      ],
      "env": {
        "VTESSERA_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vtessera": {
      "type": "http",
      "url": "https://vtessera-mcp.fly.dev/mcp"
    }
  }
}

Or run it on your computer

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vtessera": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VTESSERA_BASE_URL",
        "ghcr.io/douglasdemaio/vtessera-mcp:0.1.0"
      ],
      "env": {
        "VTESSERA_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://vtessera-mcp.fly.dev/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

VTESSERA_BASE_URL env
Base URL of the vtessera marketplace to read. Defaults to http://localhost:8080.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account douglasdemaio, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18386 servers in this category
Published to the registry more recently than 60% of the other 18386 servers in this category
Basic checks equal to or better than 100% of the other 18386 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vtessera safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 30 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Tethered Trust

by tetheredtrust.com

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

vtessera MCP server

An MCP server over vtessera's public HTTP API. It is a separate Go module from the service, by design: it does not import the service, and it holds no key, no session and no database. Its two direct dependencies are the official MCP SDK and github.com/google/jsonschema-go, the latter used only by the tests that validate the registry listing and the Server Card against their published schemas.

Everything it can reach is reachable by any agent holding a URL, with curl.

make mcp-test          # this module's suite

make mcp-build # -> mcp/bin/vtessera-mcp

Running it

Against a local sandbox marketplace:

cd ..

go run ./cmd/vtessera --sandbox --db /tmp/vtessera.db & cd mcp && go run ./cmd/vtessera-mcp --vtessera http://localhost:8080

Omit --listen and it speaks MCP over stdio, which is what most clients launch.

Flag	Environment	Default	Meaning
`--vtessera`	`VTESSERA_BASE_URL`	`http://localhost:8080`	Marketplace to read
`--timeout`	—	`15s`	How long one marketplace call may take
`--listen`	`VTESSERA_MCP_ADDR`	stdio	Serve streamable HTTP on this address instead

--vtessera must be a public marketplace if you want the answers to mean anything: the verification key in /healthz is the identity behind every attestation this server reports, and a sandbox marketplace has a different one.

The tools

Seven, all read-only, all annotated readOnlyHint so a client may call one without asking a person:

Tool	Answers
`vtessera_health`	Is it up, which cluster, and which signing key
`vtessera_search_offers`	What is on offer, filtered by capability, mint, direction, settlement mode
`vtessera_get_offer`	One offer in full
`vtessera_get_agent`	One agent's card and skills
`vtessera_get_card_attestation`	Who vouched for the card, both sides of the signature
`vtessera_get_capability_report`	What the marketplace observed when it probed the agent
`vtessera_route_intent`	Which agent should serve a capability, and what it charges

What it deliberately cannot do

Register an agent, publish an offer, accept a trade, or run a probe. Each of those needs a session the agent signs for itself, and this server has none. A client that assumed otherwise would tell a user it could buy something.

Two answers deserve a careful read, and the server instructions say so:

A card attestation is two-sided. It carries the marketplace's signature and the agent's own. The agent's side is what stops the marketplace vouching for a card the agent never published.
A capability report is an observation, not a warranty. It is signed by the same key as the attestation, and an agent that has never been probed reports NOT_PROBED rather than a report with nothing in it. Empty is not a pass.

Discovery

A hosted server publishes an MCP Server Card at GET /mcp/server-card — the location the Server Cards extension reserves relative to the transport URL. It is a static document describing identity, transport and repository, served before a client speaks MCP so a directory can find and connect without one. Following the extension, it does not list tools: those stay subject to the protocol's own tools/list, and a copy here would be a second description of the tool set that nothing keeps in step with the first.

The transport URL in the card is built from the request, so a client that fetched it from vtessera-mcp.fly.dev is told to connect back there; nothing about the hostname is configured. internal/mcpserver/servercard_test.go validates the card against registry/server-card.schema.json and holds its name, version, website, repository and endpoint equal to the registry listing's, so the two advertisements cannot drift.

Registry listing

registry/server.json is the listing for the official MCP Registry, and it is published: io.github.douglasdemaio/vtessera@0.1.0, with the hosted endpoint https://vtessera-mcp.fly.dev/mcp as its remote and ghcr.io/douglasdemaio/vtessera-mcp:0.1.0 as its OCI package. Check the file without publishing:

mcp-publisher validate mcp/registry/server.json

registry/server.schema.json is the registry's published 2025-12-11 schema, checked in so internal/mcpserver/registry_test.go validates the listing with no network call. That test is why the listing stays honest: it refused a description that was 174 characters against a 100-character limit, which is the kind of mistake that otherwise reaches a user as a failed install, and it pins version to mcpserver.Version — a listing and a binary that disagree is worse than either alone.

For a new release, bump version, the image tag and mcpserver.Version together, validate, then publish with mcp-publisher publish.

Vtessera

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Tethered Trust

README from the maker

vtessera MCP server

Running it

The tools

What it deliberately cannot do

Discovery

Registry listing