Home / MCP registry index / com.vesremont/store

Vesremont

com.vesremont/store in the official MCP registry. Endpoint https://vesremont.com/mcp.

The registry describes it as: Vesremont catalog, product search and buyer-authorized shopping operations.

We read its 22 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

search_products get_product get_products_batch search_brands get_catalog_filters get_product_reviews get_cart add_cart_item update_cart_item remove_cart_item get_favorites add_favorite remove_favorite get_checkout update_checkout prepare_order submit_order get_order list_webhooks create_webhook delete_webhook list_webhook_deliveries

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-vesremont-store/badge.svg)](https://lazaretto.dev/mcp-registry/com-vesremont-store)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.