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