DeepSearch

connects

deepsearch.app

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

https://deepsearch.app/api/mcpWebsiteOAuthMCP 2025-11-25v1.0.1last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 1014 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://deepsearch.app
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	search, dossier, chat
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 3 tools listable
Documentation	https://deepsearch.app/api/docs#mcp

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

3 tools usable without signing in

The server exposes a public surface before authorization: search_people, build_dossier, ask_about_person.

Tools

ask_about_personbuild_dossiersearch_people

Contract history

24 Aug 2026v1.0.1first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/deepsearch/badge.svg)](https://mcpi.app/servers/deepsearch)