Clearfront MCP Server

search_harvester

Collect emails, people, and subdomains from public sources through passive reconnaissance.

Instructions

Passive organisation/domain recon via theHarvester: emails, people, and subdomains from public sources (passive only, no active probing). Authorized use only: your own assets or a target you are authorized to assess. Passive, public-source collection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "search_harvester"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes
`json_output`	No	Return result as structured JSON.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.7.2Jul 27, 2026
Removedv2.7.1Jul 26, 2026
First observedv2.5.0Jul 8, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description emphasizes 'passive only, no active probing' and 'passive, public-source collection,' clearly disclosing non-invasive behavior. However, without annotations, it omits details on authentication requirements, rate limits, or data handling practices.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences, front-loading the core purpose and key constraints (passive, authorized use). Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and only two parameters, the description covers the tool's purpose and passivity but lacks information on return values, pagination, or error handling. Adequate for a simple passive search tool but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% with only the 'json_output' parameter having a description; the 'domain' parameter has no schema description. The tool description does not add parameter-specific details beyond what is already in the schema, failing to compensate for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs passive organization/domain recon using theHarvester to gather emails, people, and subdomains from public sources. The verb 'recon' and specific resource types distinguish it from siblings like search_domain or search_email.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions authorized use only, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. It implies usage for passive domain recon but lacks exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.