Skip to main content
Glama
kalala252

asm-mcp-server

by kalala252

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ASM_MCP_REPORT_DIRNoDirectory where reports are saved./reports
ASM_AGENT_EXECUTABLENoThe absolute path to the asm-agent executableasm-agent
ASM_MCP_SCAN_TIMEOUT_SECONDSNoMaximum seconds to wait for a scan600

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_domainB

指定apexドメインを受動調査し、保存したレポートの識別子と件数を返す。

list_reportsA

MCP経由で作成済みのレポートを新しい順に返す。domainは完全一致で絞り込む。

get_report_summaryB

レポートの対象、収集時刻、件数、一部取得、エラー、警告を返す。

list_assetsA

保存済みレポートのドメイン、ホスト名、IP、サービス、証明書をページ単位で返す。

get_evidenceB

根拠を返す。asset指定時はsubjectまたはobjectが完全一致する根拠だけに絞る。

list_vulnerabilitiesC

Shodanがサービス観測へ関連付けた脆弱性候補と製品・観測情報を返す。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues