A Model Context Protocol server that provides network asset information based on query conditions. This server allows LLMs to obtain network asset
If you already use ZoomEye, the zoomeye mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol server that provides network asset information based on query conditions. This server allows LLMs to obtain network asset information and supports querying network asset information by zoomeye dork etc.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
zoomeye_search — Get network asset information based on query conditionsPrerequisites — The Prerequisites tool exposed by this serverCaching — The ZoomEye MCP server implements caching to improve performance and reduce API calls:Pagination — For queries that return many results, you can paginate through them:Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: ZOOMEYE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ZoomEye's toolset — zoomeye_search, Prerequisites, Caching and 1 more — is a fair guide to whether it matches your workflow. It is maintained by zoomeye-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| zoomeye_search | Get network asset information based on query conditions. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Caching | The ZoomEye MCP server implements caching to improve performance and reduce API calls: |
| Pagination | For queries that return many results, you can paginate through them: |
{
"mcpServers": {
"zoomeye": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"ZOOMEYE_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ZOOMEYE_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.