Research a person's public footprint from a name, phone, email, or username. Sourced.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://deepsearch.app/api/mcp3 tools · 928mssearch_peopleResolve 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 betwe…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 betwe…
| Parameter | Type | Description |
|---|---|---|
| query* | string | Name, phone number, email address, or username to look up. |
| type | string | How to interpret the query. |
| platforms | array | Optional: for a username search, restrict discovery to these platforms (e.g. instagram, x, github). |
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, locations, and web mentions - every claim linked to the page it came from. Prefer this over reading search results yo…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 yo…
| Parameter | Type | Description |
|---|---|---|
| name* | string | The person's full name. |
| headline | string | Optional descriptor to disambiguate, e.g. 'Engineer, London'. |
| username | string | Optional known handle to focus the profile on the right person. |
| refresh | boolean | Rebuild from scratch instead of using the shared cache. Always meters. |
ask_about_personAnswer 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…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…
| Parameter | Type | Description |
|---|---|---|
| name* | string | The person the question is about. |
| question* | string | Your question about the person. |
| context | string | Optional extra grounding context, e.g. a prior dossier summary. |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Research a person's public footprint from a name, phone, email, or username. Sourced.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.