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.

Vaanzari Commerce

REMOTE · VAANZARI.COM

Discover Banarasi sarees and manage authorized Vaanzari shopping workflows with hosted checkout.

Available components

0 this week 77 Trust /100

Last scanned (18 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security60
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1562 tokens (~37/item across 42 items; 29 tools + 13 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 30 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Oct 26 0
    • Tool “cancel_payment_attempt” rewrote its description, which is the text the model reads security
    • Tool “get_payment_status” rewrote its description, which is the text the model reads security
    • Tool “retry_payment” rewrote its description, which is the text the model reads security
    • Tool “start_checkout” rewrote its description, which is the text the model reads security
    • “get_checkout_summary” added an optional parameter “billing_address” cosmetic
    • “get_checkout_summary” added an optional parameter “shipping_address” cosmetic
    • “start_checkout” added an optional parameter “expected_currency” cosmetic
    • “start_checkout” added an optional parameter “expected_total” cosmetic
  • 4 Oct 26 0
    • Tool “cancel_payment_attempt” rewrote its description, which is the text the model reads security
    • Tool “get_payment_status” rewrote its description, which is the text the model reads security
    • Tool “retry_payment” rewrote its description, which is the text the model reads security
    • Tool “start_checkout” rewrote its description, which is the text the model reads security
  • 2 Oct 26 0
    • Tool “get_saree” rewrote its description, which is the text the model reads security
    • Tool “search_sarees” rewrote its description, which is the text the model reads security
    • “start_checkout” added an optional parameter “payment_scope” cosmetic
  • 1 Oct 26 0
    • Tool “cancel_order” rewrote its description, which is the text the model reads security
    • Tool “cancel_payment_attempt” rewrote its description, which is the text the model reads security
    • Tool “close_support_ticket” rewrote its description, which is the text the model reads security
    • Tool “create_support_ticket” rewrote its description, which is the text the model reads security
    • Tool “get_payment_status” rewrote its description, which is the text the model reads security
    • Tool “reply_support_ticket” rewrote its description, which is the text the model reads security
    • Tool “resume_payment” rewrote its description, which is the text the model reads security
    • Tool “retry_payment” rewrote its description, which is the text the model reads security
    • Tool “start_checkout” rewrote its description, which is the text the model reads security
    • Tool “create_support_ticket” is now declared destructive security
    • Tool “get_payment_status” is now declared destructive security
    • Tool “remove_from_cart” is now declared destructive security
    • Tool “remove_pick” is now declared destructive security
    • Tool “reply_support_ticket” is now declared destructive security
    • Tool “resume_payment” is now declared destructive security
    • Tool “retry_payment” is now declared destructive security
    • Tool “set_cart_quantity” is now declared destructive security
    • Tool “start_checkout” is now declared destructive security
    • Tool “update_profile” is now declared destructive security
    • Schema quality: 29 → 33 ▼ functional
  • 30 Sept 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://vaanzari.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vaanzari.com CN=WE1,O=Google Trust Services,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA256 81a7b14238190266130288dc26c80a55
SANs: vaanzari.com, *.vaanzari.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 secure

Validation of vaanzari.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
vaanzari.com. DS published 2371 13 Verified
vaanzari.com. Verified address RRset verified with the apex keys
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://vaanzari.com/mcp Verified 200
http (plaintext) http://vaanzari.com/mcp HTTPS enforced 301 https://vaanzari.com/mcp
MCP tools · 29 exposed · ~1,291 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
add_to_cart ~34

Add a visible saree to customer cart.

NameTypeReqDescription
quantityinteger––
saree_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

cancel_order ~46

Cancel an eligible customer order and send cancellation notices after signed-in browser approval.

NameTypeReqDescription
confirmation_idstring––
order_idstringyes–
reasonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

cancel_payment_attempt ~68

Cancel an unpaid Cashfree session or check Razorpay/PhonePe/Paytm status after signed-in browser approval, then persist provider state. May restore reservations or finalize an already-paid order; does not capture payment.

NameTypeReqDescription
attempt_idstringyes–
confirmation_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

close_support_ticket ~48

Close a customer support ticket and send a closing remark to Vaanzari support staff after signed-in browser approval.

NameTypeReqDescription
confirmation_idstring––
ticket_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

create_support_ticket ~65

Send a new customer support request to Vaanzari staff after signed-in browser approval. The submitted message cannot be unsent.

NameTypeReqDescription
confirmation_idstring––
messagestringyes–
order_idinteger––
subjectstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_account ~15

Read the authorized customer account profile.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_artisan ~26

Get one public Vaanzari artisan profile.

NameTypeReqDescription
idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_cart ~15

Read customer cart and current totals.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_checkout_summary ~62

Revalidate cart, discounts, points, addresses, and checkout total without placing an order.

NameTypeReqDescription
billing_addressstring––
coupon_codestring––
points_to_redeeminteger––
shipping_addressstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_order ~22

Get one authorized customer order.

NameTypeReqDescription
order_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_payment_status ~61

Refresh a customer payment attempt from Razorpay, Cashfree, PhonePe, or Paytm and persist its server-verified state. May finalize an already-paid order and send confirmation notices; does not initiate or capture payment.

NameTypeReqDescription
attempt_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_picks ~17

Read saved Vaanzari picks.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_rewards ~17

Read customer reward balance and recent point transactions.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_saree ~53

Get one visible Vaanzari saree by public catalogue ID or canonical locator. Includes its canonical storefront url; include that url as a clickable product link when presenting the product.

NameTypeReqDescription
idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_support_ticket ~27

Get one authorized customer support ticket and its messages.

NameTypeReqDescription
ticket_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_artisans ~23

List public artisan profiles connected to the visible Vaanzari catalogue.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_orders ~13

List authorized customer orders.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_support_tickets ~16

List authorized customer support tickets.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

remove_from_cart ~23

Remove one customer cart item.

NameTypeReqDescription
item_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

remove_pick ~25

Remove one saree from customer picks.

NameTypeReqDescription
saree_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

reply_support_ticket ~63

Send a reply to Vaanzari support staff after signed-in browser approval, reopening a closed ticket if needed. The submitted message cannot be unsent.

NameTypeReqDescription
confirmation_idstring––
messagestringyes–
ticket_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

resume_payment ~57

Synchronize provider state and return an existing unpaid hosted checkout after signed-in browser approval. May finalize an already-paid order and send confirmation notices; does not capture payment.

NameTypeReqDescription
attempt_idstringyes–
confirmation_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

retry_payment ~64

Create a replacement hosted Razorpay, Cashfree, PhonePe, or Paytm checkout for a failed or terminated attempt after signed-in browser approval, reserving stock/rewards. Does not capture payment.

NameTypeReqDescription
attempt_idstringyes–
confirmation_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

save_pick ~26

Save one visible saree to customer picks.

NameTypeReqDescription
saree_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_sarees ~97

Search visible Vaanzari sarees using verified catalogue fields. Each result includes its canonical storefront url; include that url as a clickable product link when presenting products. Missing attributes remain unset.

NameTypeReqDescription
fabricstring––
limitinteger––
occasionstring––
pageinteger––
qstring––
regionstring––
techniquestring––

Structured output declared, but exposes no named fields.

No examples provided.

set_cart_quantity ~32

Set quantity for one customer cart item.

NameTypeReqDescription
item_idstringyes–
quantityintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

start_checkout ~200

Create a hosted Razorpay, Cashfree, PhonePe, or Paytm checkout after signed-in browser approval, reserving stock/rewards and clearing the active cart. First call get_checkout_summary with the same addresses, discounts and points; submit its approved total/currency as expected_total/expected_currency. International delivery requires Razorpay in the delivery currency. Paytm supports domestic INR only. Synchronizes any active payment first and may finalize an already-paid order. No payment is captured by this tool.

NameTypeReqDescription
billing_addressstring––
confirmation_idstring––
coupon_codestring––
expected_currencystring––
expected_totalnumber––
idempotency_keystringyes–
payment_methodstringyes–
payment_modestring––
payment_scopestring––
points_to_redeeminteger––
shipping_addressstring––

Structured output declared, but exposes no named fields.

No examples provided.

update_profile ~52

Update customer name, phone, and delivery address after signed-in browser approval.

NameTypeReqDescription
addressstringyes–
confirmation_idstring––
namestringyes–
phonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_coupon ~24

Validate a coupon against the authorized customer cart.

NameTypeReqDescription
codestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Vaanzari Commerce MCP server?

Vaanzari Commerce is a hosted endpoint at https://vaanzari.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 · vaanzari.com

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

What is the Vaanzari Commerce MCP server?

Vaanzari Commerce is an MCP server listed in the public MCP registry as com.vaanzari/commerce. Discover Banarasi sarees and manage authorized Vaanzari shopping workflows with hosted checkout. This page covers its hosted endpoint (https://vaanzari.com/mcp).

Is the Vaanzari Commerce MCP server safe to use?

Vaanzari Commerce 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 Vaanzari Commerce MCP server expose?

Vaanzari Commerce exposes 29 tools: search_sarees, get_saree, list_artisans, get_artisan, get_account, and 24 more. Their descriptions and schemas cost roughly 1,291 tokens of context every time the server is loaded.

Does the Vaanzari Commerce MCP server require authentication?

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

Is the Vaanzari Commerce MCP server still maintained?

Vaanzari Commerce is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Vaanzari Commerce MCP server?

VerifyMCP ran 13 checks on Vaanzari Commerce, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.