DeepSearch MCP server
app.deepsearch/deepsearchdeepsearch.appstreamable-httpv1.0.1Scanned
Research a person's public footprint from a name, phone, email, or username. Sourced.
13 tools: 1 can delete or cancel things, 5 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 11
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DeepSearch MCP server can do
The DeepSearch MCP server is published by deepsearch.app, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (1 tool: cancel_lookup_job) and create or change data (5 tools: build_dossier, ask_about_person, research, build_company_dossier and 1 more). 7 tools only read.
1 tool reads private data (search_people); 11 tools bring in text other people can write (search_people, build_dossier, ask_about_person and 8 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 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 5Claude Code: ask
ask_about_personAnswer one specific question about a person, grounded in their public footprint, and suggest follow-ups.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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…Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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 any lookup or research operation 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 any lookup or research operation 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
researchRun a multi-step research agent on a public topic, company, or vehicle and return one cited Markdown report: it plans, searches, reads the pages themselves, and corroborates claims…Reads text others write1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "research" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Run a multi-step research agent on a public topic, company, or vehicle and return one cited Markdown report: it plans, searches, reads the pages themselves, and corroborates claims across sources before writing. Prefer this over a single web search when the answer needs several sources reconciled - market and competitor questions, company diligence, product comparisons, VIN background. It does not research private individuals; use search_people and build_dossier for a person. Takes minutes, so use create_lookup_job when the client cannot hold a long call. 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
Only reads 7Show 7 read-only tools
get_lookup_jobGet saved progress status and the completed result.Reads text others writeNo findings
Why it is in this group
- The name "get_lookup_job" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo findings
Why it is in this group
- The name "get_lookup_job_events" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo findings
Why it is in this group
- The name "list_lookup_jobs" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo findings
Why it is in this group
- The name "lookup_vin" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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
reverse_image_searchSearch image appearances using public sources.Reads text others writeNo findings
Why it is in this group
- The name "reverse_image_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search image appearances 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. Find image appearances, never facial recognition. 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_companiesSearch companies using public sources.Reads text others writeNo findings
Why it is in this group
- The name "search_companies" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_people" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "resolve" and "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "resolve" and "email": it reads inbound email, which other people can write.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write11
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://deepsearch.app/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://deepsearch.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://deepsearch.app/api/mcp: tools/list returned 14 tools to an anonymous client, including cancel_lookup_job (destructive), build_dossier (write), ask_about_person (write), research (write), build_company_dossier (write) and 1 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 5 to 6
Findings
Matches of fixed checks, with the text they matched.
- Warnresearch
The server marks "research" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:researchChanges things
- Changed:create_lookup_jobChanges thingsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
- Tools that change things, listed without credentials: 5 to 6
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/mcpclaude mcp add --transport http deepsearch https://deepsearch.app/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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__research",
"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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as deepsearch. Review it before you use it.
Capability tags behind 11 rules
- mcp__deepsearch__search_people private-data, untrusted-input
- mcp__deepsearch__build_dossier untrusted-input
- mcp__deepsearch__ask_about_person untrusted-input
- mcp__deepsearch__research untrusted-input
- mcp__deepsearch__search_companies untrusted-input
- mcp__deepsearch__build_company_dossier untrusted-input
- mcp__deepsearch__reverse_image_search untrusted-input
- mcp__deepsearch__lookup_vin untrusted-input
- mcp__deepsearch__get_lookup_job_events untrusted-input
- mcp__deepsearch__get_lookup_job untrusted-input
- mcp__deepsearch__list_lookup_jobs untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.deepsearch/deepsearch/verify?hash=f40ec4206f053b424c66766206ff7f18956deb4524cc41f6b2fec95bd5fefb0d" | jq -e '.changed == false'Pinned hash f40ec4206f05, from Nov 12, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.deepsearch/deepsearch/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.deepsearch/deepsearch)Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.
DeepSearch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DeepSearch MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the DeepSearch MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_lookup_job.
Can the DeepSearch MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DeepSearch MCP server have?
- 13 tools: 1 destructive, 5 write, 7 read. cancel_lookup_job, build_dossier, ask_about_person, research, build_company_dossier, create_lookup_job, search_people, search_companies and 5 more.
Does the DeepSearch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the DeepSearch MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DeepSearch MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 30, 2026. Every change is on this page and in its Atom feed.