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.

Vellium & Co Testing Lab

REMOTE · VELLIUMANDCO.COM

Independent checks of paid x402 data sellers and of AI-agent access to shopping and travel sites

Available components

64 Trust /100

Last scanned (2 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Search and Retrieval

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 Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 806 tokens (~89/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 18 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.

  • 16 Oct 26 +11
    • Transport: fail → pass ▲ security
  • 15 Oct 26 −10
    • Transport: pass → fail ▼ security
  • 14 Oct 26 +1
    • Tool “find_route” rewrote its description, which is the text the model reads security
    • “find_route” added an optional parameter “detail” cosmetic
  • 13 Oct 26 +1
    • Schema quality: 75 → 85 ▼ functional
    • Tool coverage: 50% → 59% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “find_route” functional
    • “list_websites” added an optional parameter “cursor” cosmetic
    • “list_websites” added an optional parameter “detail” cosmetic
    • “list_websites” added an optional parameter “limit” cosmetic
  • 12 Oct 26 60

    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 18 Oct 2026 · Probed https://velliumandco.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=velliumandco.com CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 b1427012ef4045060e9aea327f8161e3
SANs: velliumandco.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of velliumandco.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
velliumandco.com. 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://velliumandco.com/mcp Verified 200
http (plaintext) http://velliumandco.com/mcp HTTPS enforced 301 https://velliumandco.com/mcp
MCP tools · 9 exposed · ~779 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
batch ~41

Check up to 25 sellers and 25 websites in one call (cheapest for many checks).

NameTypeReqDescription
sellersarray––
websitesarray––

No output schema declared.

No examples provided.

changes ~30

What changed since a day — keep a local copy in sync.

NameTypeReqDescription
sincestring–YYYY-MM-DD

No output schema declared.

No examples provided.

check_seller ~65

Our latest independent check of one paid seller, by its address (any spelling) or id: answering, price, buyers, and its paid answers checked against an independent record (with proof).

NameTypeReqDescription
idstring––
resourcestring–the seller's URL

No output schema declared.

No examples provided.

check_website ~51

Can AI agents use this shopping or travel website? Plain-agent access, each AI agent at the door, robots rules, llms.txt, history.

NameTypeReqDescription
domainstringyese.g. walmart.com

No output schema declared.

No examples provided.

find_route ~153

Where to go for a job, before you spend tokens on trial and error: the best tested free official source with its exact call and how much it returns (and a fallback). Ask in plain words, e.g. 'UK company directors', 'Apple revenue', 'EU gas storage'. detail=full adds the paid sellers we rate and other sources.

NameTypeReqDescription
countrystring–optional ISO 3166 two-letter country code to prefer sources for that country, e.g. GB, US, DE
detailstring–full = also the paid sellers, registry-listed sources and other sources (a strong match otherwise returns the route alone)
qstringyeswhat you need, in plain words

No output schema declared.

No examples provided.

list_categories ~44

Every category of paid service agents buy, with sellers, buyers and how we check it; names in your language with lang.

NameTypeReqDescription
langstring–language for category names

No output schema declared.

No examples provided.

list_websites ~140

Rated websites, filtered by market (e.g. 'United States', 'Japan'), plain-agent outcome (open, blocked, timeout) or price honesty (does the price agents read match what people see).

NameTypeReqDescription
cursorstring–next_cursor from the last page
detailstring–full = per-agent tables for every site (else counts; check_website has the tables)
limitinteger–default 40
marketstring––
plain_agentstring––
pricesstring–price honesty on product, event or stay pages: keep sites with at least one page in this state

No output schema declared.

No examples provided.

search_sellers ~223

Find paid x402 data services AI agents can buy, inside one category, ranked. Use before paying any seller.

NameTypeReqDescription
answeringboolean––
categorystringyescategory slug or its name in any of 19 languages, e.g. crypto-prices, 加密货币价格, 暗号資産の価格, cotización cripto (see list_categories)
cursorstring––
limitinteger––
max_pricenumber–max USDC per call
min_accuracynumber–keep sellers whose 95% range of correct paid answers starts at or above this share (0 to 1)
min_buyersinteger––
qstring–text to match in name or address
sortstring–accuracy ranks by the low end of the 95% range of paid answers judged correct
tools_honouredboolean–AI chat sellers only: keep those whose checked calls passed an agent's tools to the model and never dropped them

No output schema declared.

No examples provided.

sellers_on_domain ~32

Every paid seller we check on one host.

NameTypeReqDescription
domainstringyes–
limitinteger––

No output schema declared.

No examples provided.

Install

How do I install the Vellium & Co Testing Lab MCP server?

Vellium & Co Testing Lab is a hosted endpoint at https://velliumandco.com/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 · velliumandco.com

# add to Claude Code
claude mcp add --transport http com-velliumandco-lab 'https://velliumandco.com/mcp'
Common questions

What is the Vellium & Co Testing Lab MCP server?

Vellium & Co Testing Lab is an MCP server listed in the public MCP registry as com.velliumandco/lab. Independent checks of paid x402 data sellers and of AI-agent access to shopping and travel sites. This page covers its hosted endpoint (https://velliumandco.com/mcp).

Is the Vellium & Co Testing Lab MCP server safe to use?

Vellium & Co Testing Lab scores 64 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 Vellium & Co Testing Lab MCP server expose?

Vellium & Co Testing Lab exposes 9 tools: search_sellers, check_seller, sellers_on_domain, list_categories, check_website, and 4 more. Their descriptions and schemas cost roughly 779 tokens of context every time the server is loaded.

Does the Vellium & Co Testing Lab MCP server require authentication?

No. We connected to Vellium & Co Testing Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vellium & Co Testing Lab MCP server still maintained?

Vellium & Co Testing Lab is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.