FofaMap
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fofa_validate_queryA | Perform local syntax checks without spending FOFA quota. |
| fofa_fieldsA | Return the versioned FOFA field and membership capability catalogue without using quota. |
| fofa_accountA | Return the current FOFA account tier, API capabilities and quota information. |
| fofa_searchB | Run one read-only FOFA search page. If the user named a product/OA/VPN, call fofa_rules first and paste its query verbatim. |
| fofa_search_nextA | Continue a FOFA search using the opaque cursor returned by fofa_search. |
| fofa_icon_searchB | Fetch a public website favicon safely, calculate its FOFA MurmurHash3 value, and search matching assets. |
| fofa_host_profileA | Get FOFA Host aggregation for one IP or DNS name. Registered users have no Host API. |
| fofa_statsB | Get FOFA stats. Personal/education accounts have no stats API. size is Top-N (default 5). |
| fofa_syntaxA | Return official FOFA query operators and syntax fields from the API appendix. |
| fofa_rulesA | Search bundled official app= names; call before product searches and use returned queries verbatim. |
| fofa_exportB | Start a bounded export job; retrieve status and artifact through MCP resources. |
| fofa_job_statusB | Read local export, agent or scan job state. |
| fofa_agent_runA | Run planning with bundled app= fingerprints and evidence-labelled website candidates; never scan. |
| nuclei_planA | Create an exact, expiring Nuclei plan and one-time approval token. Scanning must be enabled. |
| nuclei_executeA | Consume a scope-bound approval exactly once and execute that exact plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| fields_resource | Current versioned FOFA field catalogue. |
| rules_resource | Bundled FOFA app= fingerprint library (official names from fofa.info/library). |
| account_resource | Current FOFA account capability and usage data. |
TDQS
Scored across 15 tools
Each tool mostly maps to a distinct capability: search, pagination, icon search, host aggregation, stats, metadata, export, job status, and nuclei execution. The only mild overlap is fofa_agent_run versus nuclei_plan, but the descriptions clearly separate evidence planning from executable scan planning.
Names consistently use snake_case with a clear fofa_ or nuclei_ prefix. The pattern is not strictly verb_noun since several tools are plain nouns like fofa_fields or fofa_syntax, but the grouping is predictable and readable.
At 15 tools the server is slightly above the ideal compact range, but each tool corresponds to a distinct FOFA API capability or scanning workflow step. The count is justified by the broad domain, though it does require more context for an agent to keep straight.
The toolset covers the main FOFA lifecycle: account/quota checks, query validation, search and pagination, icon search, host aggregation, statistics, field/syntax/rules metadata, export, and job status. The nuclei planning, approval, and execution flow is also complete with no obvious dead ends.