Home / MCP registry index / com.bagsthatpay/site
com.bagsthatpay/site
com.bagsthatpay/site in the official MCP registry.
Endpoint https://bagsthatpay.com/mcp.
The registry describes it as: Bags That Pay: the site's own MCP server — dataset, enquiry, entities, listing (enquiry = a...
We read its 32 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
dataset_columns dataset_search dataset_row dataset_compare dataset_stats dataset_top dataset_provenance entities_schema entity_lookup entities_search entities_in entities_export listing_describe listing_terms agent_session_start agent_session_verify claim_start claim_verify claim_status listing_draft listing_pay_card listing_pay_stripe listing_pay_usdc listing_confirm_usdc listing_status listing_withdraw listings_published placements_active claim_public enquiry_describe enquiry_fields submit_enquiry
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-bagsthatpay-site)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.