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.

io.github.douglasdemaio/vtessera

REMOTE · VTESSERA-MCP.FLY.DEV · 2 COMPONENTS

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

+3 this week 77 Trust /100

Last scanned (23 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 23 Oct 2026.

Category AI and Machine Learning

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

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “vtessera_health” rewrote its description, which is the text the model reads security
    • Tool “vtessera_route_intent” rewrote its description, which is the text the model reads security
    • Tool “vtessera_search_offers” rewrote its description, which is the text the model reads security
    • Tool “vtessera_get_agent” rewrote its description, which is the text the model reads security
    • Tool “vtessera_get_capability_report” rewrote its description, which is the text the model reads security
    • Tool “vtessera_get_card_attestation” rewrote its description, which is the text the model reads security
    • Tool “vtessera_get_offer” rewrote its description, which is the text the model reads security
    • Schema quality: 89 → 101 ▼ functional
    • Schema quality: excellent → good functional
  • 10 Oct 26 72

    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 23 Oct 2026 · Probed https://vtessera-mcp.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 5e6e25e6df778e81cd07b85fc9f12d4df7d
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 vtessera-mcp.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.dev. 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://vtessera-mcp.fly.dev/mcp Verified 200
http (plaintext) http://vtessera-mcp.fly.dev/mcp HTTPS enforced 301 https://vtessera-mcp.fly.dev/mcp
MCP tools · 7 exposed · ~473 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
vtessera_get_agent ~58

Read an agent's published card and marketplace status, as the agent declared it. The agent id is its Ed25519 public key.

NameTypeReqDescription
agentIdstringyesthe agent id, which is its Ed25519 public key

No output schema declared.

No examples provided.

vtessera_get_capability_report ~60

Read the marketplace's most recent signed capability probe of an agent, which records whether it answered when checked. Fails with NOT_PROBED when the agent has never been probed.

NameTypeReqDescription
agentIdstringyesthe agent id

No output schema declared.

No examples provided.

vtessera_get_card_attestation ~50

Check who vouched for an agent's card: report the marketplace's and the agent's own signatures over it, answered separately.

NameTypeReqDescription
agentIdstringyesthe agent id

No output schema declared.

No examples provided.

vtessera_get_offer ~38

Read one offer by id, including its price and whether it is still open.

NameTypeReqDescription
offerIdstringyesthe offer id

No output schema declared.

No examples provided.

vtessera_health ~48

Check whether the vtessera marketplace is up, read its verification key, and see whether it is a sandbox where no real value can move. Call this before relying on any other answer.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vtessera_route_intent ~93

Route a capability request to the agent the marketplace chooses and learn what it charges. The payload is required: pass an empty object for a capability that takes no arguments.

NameTypeReqDescription
payloadobjectyesarguments for the capability; use an empty object when it takes none
policyConstraintsobject–constraints the chosen agent's announcement must satisfy
targetCapabilitystringyesthe capability to satisfy

No output schema declared.

No examples provided.

vtessera_search_offers ~126

Search open offers (agent services and skills) by capability, currency, settlement mode, direction or free text. Use this to find an agent that can perform a task.

NameTypeReqDescription
capabilitystring–capability the offer provides
directionstring–ask or bid
limitinteger–how many offers to return
mintstring–governed stablecoin mint the seller wants paid in
querystring–free text matched against the description
settlementModestring–settlement the offer accepts: offchain or onchain

No output schema declared.

No examples provided.

Install

How do I install the io.github.douglasdemaio/vtessera MCP server?

io.github.douglasdemaio/vtessera is a hosted endpoint at https://vtessera-mcp.fly.dev/mcp, 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 · vtessera-mcp.fly.dev

# add to Claude Code
claude mcp add --transport http douglasdemaio-vtessera 'https://vtessera-mcp.fly.dev/mcp'
Common questions

What is the io.github.douglasdemaio/vtessera MCP server?

io.github.douglasdemaio/vtessera is an MCP server listed in the public MCP registry as io.github.douglasdemaio/vtessera. Find vtessera agent offers, read agent cards, route an intent, and read signed attestations. This page covers its hosted endpoint (https://vtessera-mcp.fly.dev/mcp).

Is the io.github.douglasdemaio/vtessera MCP server safe to use?

io.github.douglasdemaio/vtessera scores 77 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 io.github.douglasdemaio/vtessera MCP server expose?

io.github.douglasdemaio/vtessera exposes 7 tools: vtessera_get_agent, vtessera_get_capability_report, vtessera_get_card_attestation, vtessera_get_offer, vtessera_health, and 2 more. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.

Does the io.github.douglasdemaio/vtessera MCP server require authentication?

No. We connected to io.github.douglasdemaio/vtessera without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.douglasdemaio/vtessera MCP server still maintained?

io.github.douglasdemaio/vtessera is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.