Home / MCP registry index / app.deepsearch/deepsearch
DeepSearch
app.deepsearch/deepsearch in the official MCP registry.
Endpoint https://deepsearch.app/api/mcp.
The registry describes it as: Research a person's public footprint from a name, phone, email, or username. Sourced.
We read its 12 tools on 2026-10-22. 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
search_people build_dossier ask_about_person search_companies build_company_dossier reverse_image_search lookup_vin get_lookup_job_events create_lookup_job get_lookup_job cancel_lookup_job list_lookup_jobs
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-deepsearch-deepsearch)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.