Home / MCP registry index / io.usefulapi/zenserp
Zenserp MCP by usefulapi
io.usefulapi/zenserp in the official MCP registry.
Endpoint https://zenserp.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search Google, images, news, maps, shopping, YouTube, jobs, hotels, flights and trends with Zenserp.
We read its 19 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
zenserp_get_status zenserp_search zenserp_image_search zenserp_news_search zenserp_video_search zenserp_maps_search zenserp_shopping_search zenserp_youtube_search zenserp_reverse_image_search zenserp_jobs_search zenserp_shopping_product zenserp_hotels zenserp_flights zenserp_trends zenserp_answer_engine zenserp_list_search_engines zenserp_list_languages zenserp_list_countries zenserp_search_locations
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-zenserp)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.