Home / MCP registry index / com.serpzilla/mcp
Serpzilla MCP Server
com.serpzilla/mcp in the official MCP registry.
Endpoint https://mcp.serpzilla.com/mcp.
The registry describes it as: Enables AI assistants to natively interact with the Serpzilla link-building marketplace.
We read its 28 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
list_projects create_project add_article add_texts get_project_content_list set_limits update_url search_sites search_rent_sites search_context_sites get_site_info favorites_add_list favorites_get_lists favorites_rename_list favorites_delete_list favorites_get_domains favorites_add_domains favorites_delete_domains favorites_move_domains blacklist_get blacklist_add_domains blacklist_delete_domains purchase_placement purchase_rent_placement purchase_context_placement get_project_placements perform_placement_action get_user_info
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-serpzilla-mcp)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.