# DeepSearch (remote · deepsearch.app)

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

- Trust score: 89/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `deepsearch.app`: 89/100 (this document), [markdown](https://verifymcp.io/servers/app-deepsearch-deepsearch/api-mcp.md), [page](https://verifymcp.io/servers/app-deepsearch-deepsearch/api-mcp)

## Channel facts

- Endpoint: `https://deepsearch.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 880 tokens (~125/item across 7 items; 3 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the DeepSearch MCP server?

DeepSearch is a hosted endpoint at https://deepsearch.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http app-deepsearch-deepsearch 'https://deepsearch.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-deepsearch-deepsearch": {
      "url": "https://deepsearch.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-deepsearch-deepsearch": {
      "type": "http",
      "url": "https://deepsearch.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-deepsearch-deepsearch]
url = "https://deepsearch.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-deepsearch-deepsearch": {
      "type": "remote",
      "url": "https://deepsearch.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-deepsearch-deepsearch --url 'https://deepsearch.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-deepsearch-deepsearch:
    url: "https://deepsearch.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-deepsearch-deepsearch": {
      "Transport": "http",
      "Url": "https://deepsearch.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-deepsearch-deepsearch -t streamable-http -u 'https://deepsearch.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-deepsearch-deepsearch": {
      "type": "http",
      "url": "https://deepsearch.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 89, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `search_people` (~167 tokens)

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.

Input parameters:

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

### `build_dossier` (~204 tokens)

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.

Input parameters:

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

### `ask_about_person` (~150 tokens)

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.

Input parameters:

- `context` (string): Optional extra grounding context, e.g. a prior dossier summary.
- `name` (string, required): The person the question is about.
- `question` (string, required): Your question about the person.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-deepsearch-deepsearch/api-mcp#diagnostics

## Score history

- 2026-09-20: 89
- 2026-09-19: 89
- 2026-09-18: 89
- 2026-09-17: 89
- 2026-09-16: 88
- 2026-09-15: 88
- 2026-09-14: 87
- 2026-09-13: 87
- 2026-09-12: 87
- 2026-09-11: 86
- 2026-09-10: 86
- 2026-09-09: 85
- 2026-09-08: 85
- 2026-09-07: 84
- 2026-09-06: 84
- 2026-09-05: 83
- 2026-09-04: 83
- 2026-09-03: 82
- 2026-09-02: 82
- 2026-09-01: 81
- 2026-08-31: 81
- 2026-08-30: 80
- 2026-08-29: 80
- 2026-08-28: 80
- 2026-08-27: 79
- 2026-08-26: 79
- 2026-08-25: 77
- 2026-08-24: 77
- 2026-08-23: 76
- 2026-08-22: 76

## Common questions

### What is the DeepSearch MCP server?

DeepSearch is an MCP server listed in the public MCP registry as app.deepsearch/deepsearch. Research a person's public footprint from a name, phone, email, or username. Sourced. This page covers its hosted endpoint (https://deepsearch.app/api/mcp).

### Is the DeepSearch MCP server safe to use?

DeepSearch scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DeepSearch MCP server expose?

DeepSearch exposes 3 tools: search_people, build_dossier, ask_about_person. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.

### Does the DeepSearch MCP server require authentication?

No. We connected to DeepSearch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DeepSearch MCP server still maintained?

DeepSearch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://deepsearch.app/api/mcp
- Website: https://deepsearch.app/api/docs
- Changelog RSS feed: https://verifymcp.io/servers/app-deepsearch-deepsearch/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-deepsearch-deepsearch/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-deepsearch-deepsearch/api-mcp