Home / MCP registry index / xyz.rubenayla.partle/marketplace
Partle
xyz.rubenayla.partle/marketplace in the official MCP registry.
Endpoint https://partle.rubenayla.xyz/mcp/. Source: github.com/rubenayla/partle-mcp.
The registry describes it as: Search products in nearby stores. Agents can also list items for sale on a user's behalf.
We read its 30 tools on 2026-10-26. 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 search_stores get_store get_stats search_wanted create_buy_request submit_feedback create_product update_product delete_product delete_product_image get_my_products get_upload_url upload_product_image get_my_inventory add_inventory_item update_inventory_item delete_inventory_item mark_for_sale mark_sold get_account_settings update_account_settings set_account_username list_account_api_keys create_account_api_key rotate_account_api_key revoke_account_api_key list_connected_apps revoke_connected_app
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/xyz-rubenayla-partle-marketplace)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.