app.deepsearch/deepsearch MCP Server

The Model Context Protocol (MCP) server app.deepsearch/deepsearch provides tools to research a person’s public footprint. Inputs include a name, phone, email, or username, and results are sourced as stated in the server description. The server is identified by the slug app-deepsearch-deepsearch and exposes 3 tools.

🛠️ Key Features

Research a person’s public footprint
Accepts name, phone, email, or username inputs
Returns sourced results
Exposes 3 tools

🚀 Use Cases

Investigate public presence associated with a name
Cross-check identifiers such as phone numbers or email addresses
Explore public footprint linked to a username

⚡ Developer Benefits

Standardized MCP tooling (3 tools)
Clear input types: name, phone, email, username
Sourcing is part of the described output

⚠️ Limitations

Scope is limited to “public footprint” research as described
Only the listed identifiers are explicitly supported in the provided data

{ "type": "object", "properties": { "query": { "type": "string", "description": "Name, phone number, email address, or username to look up." }, "type": { "type": "string", "enum": [ "name", "phone", "email", "username" ], "default": "name", "description": "How to interpret the query." }, "platforms": { "type": "array", "items": { "type": "string" }, "description": "Optional: for a username search, restrict discovery to these platforms (e.g. instagram, x, github)." } }, "required": [ "query" ] }

{ "type": "object", "properties": { "name": { "type": "string", "description": "The person's full name." }, "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." }, "refresh": { "type": "boolean", "description": "Rebuild from scratch instead of using the shared cache. Always meters." } }, "required": [ "name" ] }

{ "type": "object", "properties": { "name": { "type": "string", "description": "The person the question is about." }, "question": { "type": "string", "description": "Your question about the person." }, "context": { "type": "string", "description": "Optional extra grounding context, e.g. a prior dossier summary." } }, "required": [ "name", "question" ] }

Install

Tools (3)

search_peoplebuild_dossierask_about_person

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://deepsearch.app/api/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "deepsearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://deepsearch.app/api/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

DeepSearch

app.deepsearch/deepsearch MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

search_people

build_dossier

ask_about_person

Install

Remote endpoint

Related servers

query	string	required	Name, phone number, email address, or username to look up.
type	string	optional	How to interpret the query.
platforms	array	optional	Optional: for a username search, restrict discovery to these platforms (e.g. instagram, x, github).

name	string	required	The person's full name.
headline	string	optional	Optional descriptor to disambiguate, e.g. 'Engineer, London'.
username	string	optional	Optional known handle to focus the profile on the right person.
refresh	boolean	optional	Rebuild from scratch instead of using the shared cache. Always meters.