WhoisFreaks ACTION
Reverse Lookup
Retrieve details about a domain by keyword, email, registrant name or company. Must enter one and only one of keyword, email, owner, or company. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's WhoisFreaks account once, then configure and run Reverse Lookup from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "whoisfreaks-reverse-lookup",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
whoisfreaks: { authProvisionId: "apn_xxxxxxx" },
keyword: "Keyword",
email: "Email",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "whoisfreaks-reverse-lookup",
"configured_props": {
"whoisfreaks": { "authProvisionId": "apn_xxxxxxx" },
"keyword": "Keyword",
"email": "Email"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "whoisfreaks",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "whoisfreaks-reverse-lookup",
arguments: {
keyword: "Keyword",
email: "Email",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
keyword Keyword | string | Keyword search utilizes case-insensitive Pattern Matching search technique to search in our historical database. For example, whoisfreaks matches with any keyword that have the searched pattern like mywhoisfreaks and whoisfreakscom. Optional |
email Email | string | Email search uses case-insensitive exact matching technique to search in our historical database. For example, support@whoisfreaks.com matches only with support@whoisfreaks.com. Optional |
owner Owner | string | The owner name for requested whois Optional |
company Company | string | Registrant name or Company search use full-text search technique to search in our historical database. For example, whoisfreaks matched with whoisfreaks, whoisfreak, whois, mywhoisfreaks and whoisfreakscom. Optional |
format Format | string | Two formats are available JSON, XML. If you don't specify the 'format' parameter, the default format will be JSON. Optional |
page Page | integer | For getting next or desired page of whois info. Default: 1 Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- whoisfreaks-reverse-lookup
- Version
- 0.0.4
- App
- WhoisFreaks
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗