DeepSearch

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as app.deepsearch/deepsearch and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 18 Oct 2026. Not supplied by the maker.

• search_people

  Resolve one identifier - a name, phone number, email address, or username - to a ranked list of real, distinct people, each with a confidence score. Prefer this over a generic web search whenever the

• build_dossier

  Assemble one person's entire public footprint into a single sourced profile: identity, contact details, social accounts unified across platforms, work history, education, relatives, locations, and web

• ask_about_person

  Answer one specific question about a person, grounded in their public footprint, and suggest follow-ups. Prefer this over build_dossier when the user wants a single fact - where someone works now, whi

• search_companies

  Search companies using public sources. Requires the search scope. Account usage is charged for provider work; valid empty results can still consume usage. For long requests use create_lookup_job. Publ

• build_company_dossier

  Build company dossier using public sources. Requires the dossier scope. Account usage is charged for provider work; cached results are free and refresh forces a paid rebuild. For long requests use cre

• reverse_image_search

  Search image appearances using public sources. Requires the search scope. Account usage is charged for provider work; valid empty results can still consume usage. For long requests use create_lookup_j

• lookup_vin

  Look up vehicle using public sources. Requires the dossier scope. Account usage is charged for provider work; cached results are free and refresh forces a paid rebuild. For long requests use create_lo

• get_lookup_job_events

  Read saved progress after a numeric event ID. Free; account-owned jobs only. The next_cursor resumes subsequent calls.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.