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.

Vidé Vita

REMOTE · SHOP.VIDE.CARE · SCANNED SEP 20

Vidé Vita supplements — live prices, stock, label amounts, warnings, reviews and checkout

Available components

+3 this week 75 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 497 tokens (~55/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% 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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Vidé Vita MCP server?

Vidé Vita is a hosted endpoint at https://shop.vide.care/wp-json/vide/v1/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 · shop.vide.care

# add to Claude Code
claude mcp add --transport http care-vide-shop-vide-vita 'https://shop.vide.care/wp-json/vide/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "care-vide-shop-vide-vita": {
      "url": "https://shop.vide.care/wp-json/vide/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "care-vide-shop-vide-vita": {
      "type": "http",
      "url": "https://shop.vide.care/wp-json/vide/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.care-vide-shop-vide-vita]
url = "https://shop.vide.care/wp-json/vide/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "care-vide-shop-vide-vita": {
      "type": "remote",
      "url": "https://shop.vide.care/wp-json/vide/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add care-vide-shop-vide-vita --url 'https://shop.vide.care/wp-json/vide/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  care-vide-shop-vide-vita:
    url: "https://shop.vide.care/wp-json/vide/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "care-vide-shop-vide-vita": {
      "Transport": "http",
      "Url": "https://shop.vide.care/wp-json/vide/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add care-vide-shop-vide-vita -t streamable-http -u 'https://shop.vide.care/wp-json/vide/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "care-vide-shop-vide-vita": {
      "type": "http",
      "url": "https://shop.vide.care/wp-json/vide/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 19 Sept 26 0
    • Stability: 0.97 → pass security
    • Server version: 2.4.77 → 2.4.82 functional
  • 18 Sept 26 +1
    • Server version: 2.4.70 → 2.4.77 functional
  • 17 Sept 26 0
    • Server version: 2.4.61 → 2.4.70 functional
  • 16 Sept 26 +1
    • Server version: 2.4.47 → 2.4.61 functional
  • 15 Sept 26 0
    • Server version: 2.4.37 → 2.4.47 functional
  • 14 Sept 26 +1
    • Server version: 2.4.32 → 2.4.37 functional
  • 13 Sept 26 0
    • Server version: 2.4.30 → 2.4.32 functional
  • 12 Sept 26 +1
    • Server version: 2.4.8 → 2.4.30 functional
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 20 Sept 2026 · Probed https://shop.vide.care/wp-json/vide/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vide.care CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB 4 Aug 2026 18 Feb 2027 RSA 2048 SHA256-RSA de8de7e7309bdef65865edc3d744638b
SANs: *.vide.care, vide.care
CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB 22 Mar 2021 21 Mar 2036 RSA 3072 SHA384-RSA 397a66cc2756362e0daa87ca6eabe3b1
CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US 22 Mar 2021 18 Jan 2038 RSA 4096 SHA384-RSA d27fbbc1de359e5216ad6149586099c4
CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US 1 Feb 2010 18 Jan 2038 RSA 4096 SHA384-RSA 1fd6d30fca3ca51a81bbc640e35032d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of shop.vide.care. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
care. present 17539 8 Verified
vide.care. 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
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://shop.vide.care/wp-json/vide/v1/mcp Verified 200
http (plaintext) http://shop.vide.care/wp-json/vide/v1/mcp Served over HTTP 200
MCP tools · 9 exposed · ~357 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
create_payment_link ~66

Write a real pending order into the shop and return its pay page. Needs a token, because it puts a row in the shop's books; for an ordinary purchase use start_checkout instead.

NameTypeReqDescription
emailstringoptional, for the receipt
itemsarrayyes

No output schema declared.

No examples provided.

get_order_status ~41

Where an order has got to. Needs the order number and the email on it.

NameTypeReqDescription
emailstringyes
order_idintegeryes

No output schema declared.

No examples provided.

get_product ~43

Everything the shop says about one product: the label's amounts, how to take it, price, pictures.

NameTypeReqDescription
slugstringyese.g. prime-epa

No output schema declared.

No examples provided.

get_reviews ~28

Reviews customers left, for one product or the whole shop.

NameTypeReqDescription
slugstringoptional

No output schema declared.

No examples provided.

list_products ~23

Every product on sale, with price, stock and a one-line summary.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_products ~39

Search the shop the way a customer would ask, in Thai or English — an ingredient, a concern, a brand.

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

shop_info ~25

What this shop is, who runs it, how delivery, payment and returns work.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

start_checkout ~61

Put these items in the shop's cart and hand back the link that opens checkout. Nothing is charged and no account is needed — the customer pays as a guest, exactly as on the website. Use this for an ordinary purchase.

NameTypeReqDescription
itemsarrayyes

No output schema declared.

No examples provided.

usage_report ~31

What assistants have been asking this shop, and which questions it failed to answer.

NameTypeReqDescription
daysinteger

No output schema declared.

No examples provided.

Common questions

What is the Vidé Vita MCP server?

Vidé Vita is an MCP server listed in the public MCP registry as care.vide.shop/vide-vita. Vidé Vita supplements, live prices, stock, label amounts, warnings, reviews and checkout. This page covers its hosted endpoint (https://shop.vide.care/wp-json/vide/v1/mcp).

Is the Vidé Vita MCP server safe to use?

Vidé Vita scores 75 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 Vidé Vita MCP server expose?

Vidé Vita exposes 9 tools: shop_info, list_products, get_product, search_products, get_reviews, and 4 more. Their descriptions and schemas cost roughly 357 tokens of context every time the server is loaded.

Does the Vidé Vita MCP server require authentication?

No. We connected to Vidé Vita without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vidé Vita MCP server still maintained?

Vidé Vita is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.