Skip to content
MCP server

DeepSearch

By reloadAll Deepsearch servers

Research a person's public footprint from a name, phone, email, or username. Sourced.

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

2
Directories
Collected by InvokeRank
12
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
ask_about_personAnswer 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, which accounts are theirs - rather than a full profile: it is cheaper and answers directly. Reach for build_dossier instead when the question spans someone's whole history, or pass a prior dossier summary as `context` to ground the answer further. Public sources only - never private accounts or breach data. Requires chat scope. Provider work consumes account usage; cached results consume none.Read-only
build_company_dossierBuild 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 create_lookup_job. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.Read-only
build_dossierAssemble 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 mentions - every claim linked to the page it came from. Prefer this over reading search results yourself when you need the whole picture of one person rather than a single fact; it does the cross-platform correlation that a web search leaves to you. Pass a name plus the headline or username from search_people so the right individual is profiled. Repeat profiles are served from a shared cache: free and instant. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.Read-only
cancel_lookup_jobCancel your queued or running job. Work already delivered can remain charged; cancellation adds no charge.Destructive
create_lookup_jobRun one of the seven lookups durably. The operation's existing scope and billing apply; creating a job adds no surcharge. Use Idempotency-Key to retry safely.Changes data
get_lookup_jobGet saved progress status and the completed result. Free; account-owned jobs only.Read-only
get_lookup_job_eventsRead saved progress after a numeric event ID. Free; account-owned jobs only. The next_cursor resumes subsequent calls.Read-only
list_lookup_jobsPage through your saved lookup jobs. Free.Read-only
lookup_vinLook 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_lookup_job. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.Read-only
reverse_image_searchSearch 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_job. Find image appearances, never facial recognition. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.Read-only
search_companiesSearch 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. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.Read-only
search_peopleResolve 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 question is who someone is: it separates same-name individuals into candidates you can choose between, instead of returning pages to read and reconcile yourself. Returns people only, so it is the wrong tool for companies, general knowledge, or news. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.Read-only

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryDeepSearch-2 Oct 2026
SmitheryDeepSearch-2 Oct 2026