🛡MobSF MCP Tool

Created By
pullkitsana year ago
This MCP server uses mobsf api's to scan and analyze the apk and ipa files.
Overview

What is MobSF MCP Tool?

MobSF MCP Tool is a Model Context Protocol compatible tool that allows users to scan and analyze APK and IPA files using the Mobile Security Framework (MobSF) APIs.

How to use MobSF MCP Tool?

To use the MobSF MCP Tool, ensure that MobSF is installed on your system, clone the repository, install dependencies, and configure your MobSF API key. You can then run the server and use any MCP client to scan your APK or IPA files.

Key features of MobSF MCP Tool?

  • Supports scanning of APK and IPA files.
  • Utilizes MobSF's REST API for uploading files, triggering scans, and fetching analysis summaries.
  • Automatically filters large results to prevent output overload.
  • Provides a MCP-compatible interface for easy integration.

Use cases of MobSF MCP Tool?

  1. Scanning mobile applications for security vulnerabilities.
  2. Analyzing APK and IPA files for compliance and security best practices.
  3. Integrating with other MCP-capable clients for automated security assessments.

FAQ from MobSF MCP Tool?

  • What file types does MobSF MCP Tool support?

Only .apk and .ipa file types are supported.

  • Do I need to install MobSF separately?

Yes, MobSF must be installed on your system to use this tool.

  • How does the tool handle large outputs?

The tool avoids fetching large fields like raw strings or source code dumps to keep responses fast and compliant with message limits.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pullkitsan
Star
0
Language
TypeScript
License
MIT license
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago