Home / MCP registry index / uk.co.teas/shop
teas.co.uk
uk.co.teas/shop in the official MCP registry.
Endpoint https://teas.co.uk/mcp.
The registry describes it as: Find, compare and buy tea, coffee and hot chocolate from teas.co.uk, a UK online tea shop.
We read its 26 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
find_products get_product compare_products find_recipes delivery_and_returns quote_cart get_promotions get_return_status get_invoice report_problem find_substitutes add_to_basket view_basket update_basket checkout_link checkout_session get_profile my_orders track_order reorder my_subscriptions change_subscription rewards_balance start_return start_subscription join_teas
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/uk-co-teas-shop)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.