SurveyHub-MCP

FOFA Continuous Search

fofa_search_next

Search FOFA assets and paginate through large result sets using a next token for continuous retrieval.

Instructions

Search FOFA assets with /api/v1/search/next. Use returned next value for stable continuous pagination over a large result set.

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": {
      "query": "<query>"
    },
    "name": "fofa_search_next"
  }
}

Input Schema

Name	Required	Description	Default
`full`	No	Set true to search all data instead of one-year data.
`size`	No	Results per page.
`query`	Yes	FOFA query to encode as qbase64.
`fields`	No	Comma-separated return fields.	host,ip,port,domain,title
`r_type`	No	Response type. Use "json" for JSON responses.	json
`next_id`	No	Next page token returned by the previous response.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jul 15, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions pagination stability but omits details on authentication, rate limits, error handling, or result format. The additional context is minimal.

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?

Two sentences that front-load the action and key pagination concept. Every sentence earns its place with no redundancy or wasted words.

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

Completeness4/5

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

For a paginated search tool with good schema coverage and an output schema (present but not shown), the description covers the essential pagination mechanism. Missing details like link to initial search could be helpful but not critical.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds little beyond the schema, e.g., 'Encode as qbase64' is already in the schema. No new semantic value provided.

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

Purpose4/5

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

The description clearly states the tool searches FOFA assets using a specific API endpoint and mentions continuous pagination via a 'next' value. This distinguishes it from sibling tools like fofa_search, but does not explicitly differentiate them.

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 implies usage when stable continuous pagination over large result sets is needed, but does not provide explicit guidance on when to use this vs. other search tools or when not to use it.

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