Skip to content
Developers
Agents & payments

MCP

Connect tools through Streamable HTTP and OAuth.

All seven lookup tools use the REST operation schemas and billing scopes. Ordinary job tools create, list, inspect, cancel and follow long-running lookups. Supported legacy versions are 2025-03-26, 2025-06-18 and 2025-11-25. The stateless 2026-07-28 adapter usesserver/discover, client metadata and matching routing headers on every request. OAuth supports client metadata documents and retains dynamic registration for older clients.

DeepSearch also exposes a hosted MCP server for agents and IDEs that support Streamable HTTP. Use the same API key as a bearer token; scopes, expiry, rate limits, wallet metering, and onboarding errors behave the same as REST.

This server is published in the official MCP Registry as app.deepsearch/deepsearch. That entry names https://deepsearch.app/api/mcp as its remote, so a client can confirm from the registry's side that this is the endpoint we publish.

streamable-httphttps://deepsearch.app/api/mcp
oauthhttps://deepsearch.app/.well-known/oauth-protected-resource
Open setup panel
{
  "mcpServers": {
    "deepsearch": {
      "type": "streamable-http",
      "url": "https://deepsearch.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${DEEPSEARCH_API_KEY}"
      }
    }
  }
}
Tool
Use
search_people
Search people
build_dossier
Build dossier
ask_about_person
Ask about a person
search_companies
Search companies
build_company_dossier
Build company dossier
reverse_image_search
Search image appearances
lookup_vin
Look up vehicle
get_lookup_job_events
Get lookup progress
create_lookup_job
Create lookup job
get_lookup_job
Get lookup job
cancel_lookup_job
Cancel lookup job
list_lookup_jobs
List lookup jobs

Put DEEPSEARCH_API_KEY in your MCP client's local secret store or environment. Do not commit a plaintext key inside mcp.json.

Example prompts

What each tool is for, in the words a user would actually type. Names and addresses below are invented.

“Compare the legal entities for Northwind Robotics, then build a sourced report for the company I select.”

search_companiesbuild_company_dossier

Retains the selected company's domain, registry identifier and jurisdiction.

“Find public appearances of this image URL, then decode the VIN I provided from a vehicle listing.”

reverse_image_searchlookup_vin

Separates public image matches from vehicle evidence and reports missing information honestly.

“Start an asynchronous sourced company lookup, check its progress and my existing jobs, then cancel it if I ask.”

create_lookup_jobget_lookup_jobget_lookup_job_eventslist_lookup_jobscancel_lookup_job

Uses durable developer jobs for longer research and cancels only when requested.

“A candidate applied with the address jordan.avery@example.com. Which public profiles match it?”

search_people

Resolves one identifier to ranked candidates with confidence scores, instead of pages to reconcile by hand.

“I meet Dana Whitfield of Northwind Robotics tomorrow. Build me a sourced profile of her public background.”

build_dossier

Correlates accounts across platforms into one profile, with every claim linked to the page it came from.

“Where does Dana Whitfield work now, and which public source says so?”

ask_about_person

One grounded fact and its citation - cheaper and more direct than building the whole profile.

“Find whoever is behind the handle @dwhitfield, then give me their full public footprint.”

search_peoplebuild_dossier

The usual chain: disambiguate first, then profile the candidate the user picked.

“A source tells me they were head of engineering at Northwind Robotics. Is that supported by public records?”

build_dossierask_about_person

Verification against cited public sources, rather than taking a stated role at face value.