Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@asm-mcp-server Scan example.com with Shodan and summarize hosts, open ports, and CVE candidates with evidence."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A local server for using asm-agent from an MCP client. A connected LLM can collect public information, reference saved results, and verify evidence as MCP tools.
This server itself does not call the LLM API. For conversation and summarization, it uses the model on the MCP client side.
Python 3.12 or later
A separately set up asm-agent
An LLM client that supports MCP
Related MCP server: Multi-Agent Deep Researcher MCP
Place asm-agent and asm-mcp-server in separate folders and prepare their dependencies respectively.
cd /absolute/path/to/asm-agent
uv sync
cd /absolute/path/to/asm-mcp-server
uv syncWhen using Shodan, save the API key on the asm-agent side.
cd /absolute/path/to/asm-agent
uv run asm-agent credentials set-shodanAdd the following to the MCP client configuration. Specify everything with absolute paths.
{
"mcpServers": {
"passive-attack-surface": {
"command": "/absolute/path/to/uv",
"args": [
"--directory",
"/absolute/path/to/asm-mcp-server",
"run",
"asm-mcp-server"
],
"env": {
"ASM_AGENT_EXECUTABLE": "/absolute/path/to/asm-agent/.venv/bin/asm-agent",
"ASM_MCP_REPORT_DIR": "/absolute/path/to/asm-mcp-server/reports"
}
}
}
}After registration, restart or reconnect the MCP client.
On Windows, specify the absolute path of uv.exe in command, and specify ASM_AGENT_EXECUTABLE in the following format.
C:\absolute\path\to\asm-agent\.venv\Scripts\asm-agent.exeexample.comをShodanありで調査して、見つかったホスト名、IPアドレス、公開ポート、CVE候補を根拠付きでまとめて。Tool | Description |
| Collects and saves public information about a domain |
| Returns a list of saved reports |
| Returns collection counts, warnings, and errors |
| Returns hostnames, IP addresses, and public services |
| Returns information sources and observation timestamps |
| Returns Shodan CVE candidates, products, and versions |
Tools that return lists support pagination with offset and limit.
Environment variable | Default value | Description |
|
| Absolute path of the |
|
| Report save destination |
|
| Maximum seconds to wait for a single investigation |
Shodan CVEs are candidates based on past observations and do not prove that a system is currently vulnerable.
uv run ruff check .
uv run mypy src
uv run pytest根拠を返す。asset指定時はsubjectまたはobjectが完全一致する根拠だけに絞る。
Inputs: report_id (required), asset, limit, offset. Returns: total, offset, evidence, has_more, +3 more
レポートの対象、収集時刻、件数、一部取得、エラー、警告を返す。
Inputs: report_id (required). Returns: domain, partial, warnings, report_id, +5 more
保存済みレポートのドメイン、ホスト名、IP、サービス、証明書をページ単位で返す。
Inputs: report_id (required), limit, offset, asset_type. Returns: total, assets, offset, has_more, +2 more
MCP経由で作成済みのレポートを新しい順に返す。domainは完全一致で絞り込む。
Inputs: domain. Returns: reports
Shodanがサービス観測へ関連付けた脆弱性候補と製品・観測情報を返す。
Inputs: report_id (required), limit, offset. Returns: total, offset, has_more, returned, +2 more
指定apexドメインを受動調査し、保存したレポートの識別子と件数を返す。
Inputs: domain (required), skip_dns, max_hosts, enable_shodan, +3 more. Returns: domain, partial, warnings, report_id, +5 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a clearly distinct role: scan_domain initiates a scan, list_reports lists report metadata, get_report_summary provides a detailed summary, list_assets retrieves asset data, get_evidence pulls evidence, and list_vulnerabilities returns vulnerability data. There is no meaningful overlap between these operations.
All tool names follow a consistent snake_case verb_noun pattern: scan_domain, list_reports, get_report_summary, list_assets, get_evidence, list_vulnerabilities. The verb choice consistently indicates whether the tool creates or retrieves information.
Six tools is a well-scoped size for an attack surface management/recon server. Each tool maps to a distinct step in the workflow: scan, report listing, summary, asset enumeration, evidence retrieval, and vulnerability listing.
The core reconnaissance workflow is well covered: scan a domain, view reports, inspect summaries, list assets, retrieve evidence, and see vulnerabilities. Minor gaps exist around report lifecycle management, such as deleting or updating reports, but users can complete the primary investigation workflow without dead ends.
MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.
Grounded web and Agent-network research for any MCP client: answers with cited evidence.
Scrape, crawl and search the web for AI agents via MCP.
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
