MCP Server

DeepSearch

app.deepsearch/deepsearch
Search & Research Public & reachable MCP 2026-07-28

What this MCP does

Searches public sources to identify people and compiles sourced profiles covering their public online footprint.

ask_about_person
Ask about a 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, 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.
Read only Open world
Input schema
{'type': 'object', 'required': ['name', 'question'], 'properties': {'name': {'type': 'string', 'description': 'The person the question is about.'}, 'context': {'type': 'string', 'description': 'Optional extra grounding context, e.g. a prior dossier summary.'}, 'question': {'type': 'string', 'description': 'Your question about the person.'}}}
build_dossier
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 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.
Read only Open world
Input schema
{'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': "The person's full name."}, 'refresh': {'type': 'boolean', 'description': 'Rebuild from scratch instead of using the shared cache. Always meters.'}, 'headline': {'type': 'string', 'description': "Optional descriptor to disambiguate, e.g. 'Engineer, London'."}, 'username': {'type': 'string', 'description': 'Optional known handle to focus the profile on the right person.'}}}
search_people
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 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.
Read only Open world
Input schema
{'type': 'object', 'required': ['query'], 'properties': {'type': {'enum': ['name', 'phone', 'email', 'username'], 'type': 'string', 'default': 'name', 'description': 'How to interpret the query.'}, 'query': {'type': 'string', 'description': 'Name, phone number, email address, or username to look up.'}, 'platforms': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Optional: for a username search, restrict discovery to these platforms (e.g. instagram, x, github).'}}}
Added
ask_about_person
Sept. 17, 2026, 7:57 a.m.
Added
build_dossier
Sept. 17, 2026, 7:57 a.m.
Added
search_people
Sept. 17, 2026, 7:57 a.m.