Skip to main content
Glama
il-il1

MobSF MCP Server

by il-il1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MobSF MCP Server

No user-submitted related servers found.

    Related Servers

    • Node Omnibus MCP Server

      bsmi021
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server that provides advanced Node.js development tooling for automating project creation, component generation, package management, and documentation with AI-powered assistance.
      7
      9
      MIT

    • MCP Server

      NavanethaKrishnan-14
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight and extensible Model Context Protocol server built with Node.js, exposing custom tools and resources for AI clients.
      33 npm
      -

    • va-pentest-mcp

      banhongit7
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for automated security vulnerability assessment, combining OWASP Dependency-Check dependency scanning with custom code vulnerability detection, and generating detailed HTML and JSON reports.
      -
    • Binalyze AIR MCP Server by binalyze

      Binalyze AIR MCP Serverofficial

      binalyze
      A
      license
      C
      quality
      D
      maintenance
      A Node.js server implementing Model Context Protocol (MCP) that enables natural language interaction with Binalyze AIR's digital forensics and incident response capabilities.
      100
      50 npm
      6
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.7/5.0

    Scored across 71 tools

    Disambiguation2/5

    The sheer number of getJsonSection_* tools (52) makes it difficult for an agent to distinguish between them; they all perform the same operation on different sections. Additionally, tools like getJsonReport and getJsonReportSection overlap, causing ambiguity.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., uploadFile, deleteScan, getJsonSection_*). However, a few like getJsonReportSections and getJsonReportSection break the precise schema, and compareApps uses a verb phrase.

    Tool Count1/5

    71 tools is excessively high for a mobile security scanner. The majority are redundant getJsonSection_* tools that could be replaced by a single parameterized tool, drastically reducing the count. Tools like listAllHashes and getScanTasks add little value.

    Completeness2/5

    The tool set lacks essential operations like starting a scan (scanFile), which is critical for the workflow. Reporting is over-covered, but lifecycle management (update, re-analyze) is missing. There are no tools for dynamic analysis or interacting with scan progress.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources