Home / MCP registry index / com.paidhandshake/exchange
PaidHandshake Exchange
com.paidhandshake/exchange in the official MCP registry.
Endpoint https://paidhandshake.com/mcp.
The registry describes it as: Verified agent commerce plus worker-published structured intelligence and machine payments.
We read its 18 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.
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
get_fulfillment_proof get_live_inventory get_published_intelligence_catalog get_published_intelligence_sample get_free_data_sample search_matches get_unlock_quote create_checkout quote_paid_machine_job get_machine_payment_options get_machine_onboarding submit_paid_machine_job get_paid_machine_job create_recurring_paid_watch list_recurring_paid_watches set_recurring_paid_watch get_machine_wallet get_paidhandshake_capabilities
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-paidhandshake-exchange)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.