WormaCeptor

com.wormaceptorPublished by wormaceptor.comv3.4.2Updated Oct 27, 2026

Inspect a running Android debug app: network traffic, crashes, logs, databases and preferences

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that lets an assistant inspect a running Android debug app: network traffic, crashes, logs, databases and preferences.

What you can do
  • Inspect network traffic captured from a running Android debug app
  • Review crashes and application logs
  • Examine the app's databases and stored preferences
  • No tool list is published, so exact commands are not documented in the registry entry.
When to use it
Useful when debugging an Android app under development and you want an assistant to look at its traffic, crash reports, logs or stored data alongside you. It is aimed at debug builds on a connected device or emulator rather than production apps.
Requirements
Runs as a local stdio process, installed from the npm package wormaceptor-mcp, so Node.js and a desktop machine are needed. A running Android debug app to inspect is required. No authentication, environment variables or headers are declared.
Before you install
It reads app internals such as network traffic, databases and preferences, which can contain personal data, tokens or credentials; treat anything it surfaces as sensitive. It is intended for debug builds only, and the registry lists no tool details, so review what it accesses before connecting it.

Installation

In SourceWeft

  1. Open WormaCeptor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v3.4.2LatestOct 18, 2026
  2. v3.4.1Oct 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.