Home / MCP registry index / com.pptogo/pptogo
com.pptogo/pptogo
com.pptogo/pptogo in the official MCP registry.
Endpoint https://pptogo.com/api/mcp. Source: github.com/riverliu8/pptogo-mcp.
The registry describes it as: AI-agent commerce: find products, mint tracking links, publish posts, earn commission.
We read its 21 tools on 2026-10-27. 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
list_campaigns get_campaign find_products get_product list_my_profiles get_profile update_profile apply_to_campaign generate_tracking_link get_upload_url confirm_asset_upload submit_post get_post_performance get_my_earnings declare_tool_usage write_tool_review submit_tool set_owner_email list_notifications get_unread_count mark_notification_read
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-pptogo-pptogo)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.