Skip to content

DeepSearch

by deepsearch.app · remote · no sign-in to list tools · v1.0.1 · published by app.deepsearch

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

Deletes · 1Changes · 4
CompareRegistry entry

12 tools: 1 can delete or cancel things, 4 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

12 tools

Deletes or cancels 1Claude Code: deny
  • cancel_lookup_jobCancel your queued or running job.No findings

    Why it is in this group

    • The name "cancel_lookup_job" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel your queued or running job. Work already delivered can remain charged; cancellation adds no charge.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
Changes things 4Claude Code: ask
  • ask_about_personAnswer one specific question about a person, grounded in their public footprint, and suggest follow-ups.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Requires chat scope. Provider work consumes account usage; cached results consume none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • build_company_dossierBuild company dossier using public sources.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Build company dossier using public sources. Requires the dossier scope. Account usage is charged for provider work; cached results are free and refresh forces a paid rebuild. For long requests use create_lookup_job. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • build_dossierAssemble one person's entire public footprint into a single sourced profile: identity, contact details, social accounts unified across platforms, work history, education, relatives…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Repeating the same request from the same account replays its cached profile: free and instant. Profiles are not shared between accounts. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • create_lookup_jobRun one of the seven lookups durably.No findings

    Why it is in this group

    • The name "create_lookup_job" says "create": a word for a change.
    Description, as the server wrote it
    Run one of the seven lookups durably. The operation's existing scope and billing apply; creating a job adds no surcharge. Use Idempotency-Key to retry safely.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
Only reads 7Claude Code: allow
  • get_lookup_jobGet saved progress status and the completed result.No findings

    Why it is in this group

    • The name "get_lookup_job" says "get": a word for reading.
    Description, as the server wrote it
    Get saved progress status and the completed result. Free; account-owned jobs only.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_lookup_job_eventsRead saved progress after a numeric event ID.No findings

    Why it is in this group

    • The name "get_lookup_job_events" says "get": a word for reading.
    Description, as the server wrote it
    Read saved progress after a numeric event ID. Free; account-owned jobs only. The next_cursor resumes subsequent calls.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • list_lookup_jobsPage through your saved lookup jobs.No findings

    Why it is in this group

    • The name "list_lookup_jobs" says "list": a word for reading.
    Description, as the server wrote it
    Page through your saved lookup jobs. Free.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • lookup_vinLook up vehicle using public sources.No findings

    Why it is in this group

    • The name "lookup_vin" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up vehicle using public sources. Requires the dossier scope. Account usage is charged for provider work; cached results are free and refresh forces a paid rebuild. For long requests use create_lookup_job. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • search_companiesSearch companies using public sources.No findings

    Why it is in this group

    • The name "search_companies" says "search": a word for reading.
    Description, as the server wrote it
    Search companies using public sources. Requires the search scope. Account usage is charged for provider work; valid empty results can still consume usage. For long requests use create_lookup_job. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • search_peopleResolve one identifier - a name, phone number, email address, or username - to a ranked list of real, distinct people, each with a confidence score.No findings

    Why it is in this group

    • The name "search_people" says "search": a word for reading.
    Description, as the server wrote it
    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. Requires search scope. Provider work consumes account usage; cached results consume none.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__deepsearch__search_people",
      "mcp__deepsearch__search_companies",
      "mcp__deepsearch__reverse_image_search",
      "mcp__deepsearch__lookup_vin",
      "mcp__deepsearch__get_lookup_job_events",
      "mcp__deepsearch__get_lookup_job",
      "mcp__deepsearch__list_lookup_jobs"
    ],
    "ask": [
      "mcp__deepsearch__build_dossier",
      "mcp__deepsearch__ask_about_person",
      "mcp__deepsearch__build_company_dossier",
      "mcp__deepsearch__create_lookup_job"
    ],
    "deny": [
      "mcp__deepsearch__cancel_lookup_job"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as deepsearch. Review it before you use it.