zoomeye-ai/mcp_zoomeye
by Various
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
MCP
zoomeye-ai/mcp_zoomeye
Added 1 June 2026
Overview
A Model Context Protocol server that exposes ZoomEye network asset data to LLMs. It accepts query conditions such as ZoomEye dorks and returns matching asset information. Built in Python, it enables AI agents to perform network reconnaissance through a standardized interface.
Best for
Best for
Developers building LLM agents that need on-demand network asset intelligence
Use cases
- Querying network assets by ZoomEye dork for security research
- Integrating network intelligence into LLM-based automation workflows
- Enabling AI agents to retrieve open port and service data on demand
Notes
A Model Context Protocol server that exposes ZoomEye network asset data to LLMs. It accepts query conditions such as ZoomEye dorks and returns matching asset information. Built in Python, it enables AI agents to perform network reconnaissance through a standardized interface.
74 stars on GitHub. Last updated 2025-11-27.
Use cases
- Querying network assets by ZoomEye dork for security research
- Integrating network intelligence into LLM-based automation workflows
- Enabling AI agents to retrieve open port and service data on demand
Pros
- Provides structured network asset data directly to LLMs via MCP
- Simple Python implementation easy to extend or deploy
- Leverages ZoomEye’s extensive internet scanning database
Cons
- Requires a valid ZoomEye API key with associated usage limits
- Limited to data available through ZoomEye’s API (no real-time scanning)
- Dependency on external service availability and API changes
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Provides structured network asset data directly to LLMs via MCP
- Simple Python implementation easy to extend or deploy
- Leverages ZoomEye's extensive internet scanning database
Cons
- Requires a valid ZoomEye API key with associated usage limits
- Limited to data available through ZoomEye's API (no real-time scanning)
- Dependency on external service availability and API changes
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.