Vtessera

io.github.douglasdemaiov0.1.0更新於 Oct 8, 2026

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

已驗證Streamable HTTP可網頁執行AI & MLBusiness & Commerce

概覽

AI 產生的概覽

以唯讀方式存取 vtessera 代理市集：搜尋報價、讀取代理卡片、路由意圖並檢視簽章證明。

功能
把 vtessera 的公開 HTTP API 包裝成七個唯讀工具。可檢查市集健康狀態與簽章金鑰，依能力、鑄造、方向或結算模式搜尋報價，取得單一報價或某個代理的卡片與技能，讀取卡片證明與能力報告，並把意圖路由到應處理它的代理及其收費。它不能註冊代理、發布報價、接受交易或執行探測。
適用情境
當助理需要在 vtessera 市集上尋找或比較代理與報價、確認誰為某張代理卡片背書，或判斷某項能力該由哪個代理處理時使用。它不用於交易，只做讀取。
執行需求
可作為遠端 streamable HTTP 端點執行，也可在本機透過 stdio 執行，例如用 Docker 執行已發布的容器映像。環境變數 VTESSERA_BASE_URL（或 --vtessera 參數）指定要讀取的市集，預設為
安裝前請注意
所有工具皆為唯讀，伺服器不持有金鑰、工作階段或資料庫，因此無法花費、簽章或變更市集狀態。若希望結果有意義，應把 VTESSERA_BASE_URL 指向公開市集，因為沙箱市集使用不同的驗證金鑰。能力報告只是觀察結果而非保證：未被探測的代理會回報 NOT_PROBED，空結果不等於通過。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Vtessera，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

README

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 test that validates the registry listing against the published schema.

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

bash
make mcp-test          # this module's suitemake mcp-build         # -> mcp/bin/vtessera-mcp

Running it

Against a local sandbox marketplace:

bash
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.

FlagEnvironmentDefaultMeaning
--vtesseraVTESSERA_BASE_URLhttp://localhost:8080Marketplace to read
--timeout—15sHow long one marketplace call may take
--listenVTESSERA_MCP_ADDRstdioServe 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:

ToolAnswers
vtessera_healthIs it up, which cluster, and which signing key
vtessera_search_offersWhat is on offer, filtered by capability, mint, direction, settlement mode
vtessera_get_offerOne offer in full
vtessera_get_agentOne agent's card and skills
vtessera_get_card_attestationWho vouched for the card, both sides of the signature
vtessera_get_capability_reportWhat the marketplace observed when it probed the agent
vtessera_route_intentWhich 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.

Registry listing

registry/server.json is the draft for the official MCP Registry. It is schema-valid and its readyToSubmit flag is false: it still carries two placeholders, because a published container image and a hosted endpoint are deployment decisions that belong to the operator, not to a commit.

registry/server.schema.json is the registry's published 2025-09-29 schema, checked in so internal/mcpserver/registry_test.go validates the listing with no network call. That test is why the draft is 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.

Submit with mcp publish once the placeholders are real and the flag is flipped.

來源：mcp/README.md，提交 793ffb4

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.1.0最新Oct 8, 2026