digitalassetscan-mcp
OfficialRelated Servers
Alternatives to digitalassetscan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to add and verify ownership of targets, launch non-destructive security scans, and inspect or export run reports through MCP tools.MIT
- AlicenseAqualityAmaintenanceEnables scanning Android and iOS app packages from MCP clients for security issues, mapping findings to OWASP MASVS, CWE, and CVSS, and downloading pentest-style reports.8MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to work with DefAudit, supporting project and scan listing, starting scans, retrieving results, and marking or unmarking false positives.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run and track scans, inspect quota usage, redeem existing studio report rights, and list or download generated reports through the associated REST API. It operates locally over stdio with API-key authentication and bounded retry/polling behavior.38 npmApache 2.0

scanmalware-mcpofficial
AlicenseNot gradedqualityBmaintenanceWraps the ScanMalware.com API to enable phishing triage, malware scanning, and certificate inspection through natural language, allowing users to submit scans, retrieve results, and analyze threats via MCP tools.1Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables an MCP client to discover ABS datasets, inspect SDMX dimension order and codelists, and run bounded statistical-data queries against the Australian Bureau of Statistics Data API.MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: submitting an analysis, polling for results, listing assets, and retrieving methodology. There is no overlap or ambiguity in what an agent would use each tool for.
All tool names follow a consistent verb_noun snake_case pattern: analyze_asset, get_analysis_job, list_assets, get_methodology. The naming is predictable and easy to navigate.
Four tools is well-scoped for a focused asset-scanning server. Each tool serves a necessary part of the workflow: discover assets, understand methodology, submit analysis, and retrieve results.
The core async analysis lifecycle is covered with submit and poll, and the supporting discovery/methodology tools are present. Minor gaps exist, such as no explicit cancel operation or asset detail retrieval, but the primary workflow is fully usable.