Skip to main content
Glama
OdellMoreno

Uber APK Signer MCP Server

by OdellMoreno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Uber APK Signer MCP Server

No user-submitted related servers found.

    Related Servers

    • re-apktool

      Heretek-RE
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Android APK triage, providing tools to parse APK headers, list DEX classes, and decode AndroidManifest.xml using apktool or androguard backends.
      5
      1
      MIT

    • mobile-security-mcp

      Serhatcck
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to analyze Android APK and iOS IPA files for security issues through natural language conversation, including permission auditing, secret detection, and SDK enumeration.
      12
      6 npm
      4
      MIT

    • Fables MCP Server

      Atum246
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides AI agents with tools to build, deploy, and manage Flutter applications, including APK/AAB generation, keystore management, and CI/CD integration.
      4 npm
      1
      MIT

    • jadx-rpc

      AsherDLL
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for analyzing Android APK, DEX, or JAR files via a headless jadx engine, enabling LLM agents to query decompiled code, symbols, call graphs, and more.
      2
      GPL 3.0

    • android-mcp

      tomdwipo
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server for Android operating system automation. This server provides tools to interact directly with Android devices and app interaction with control
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating, listing, signing, and verifying. No overlap, and descriptions reinforce the differences.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (create_keystore, list_keystores, sign_apk, verify_apk_signature).

    Tool Count5/5

    With 4 tools, the server covers the essential operations for APK signing without unnecessary extras, perfectly scoped for its purpose.

    Completeness4/5

    Core workflow (create keystore, sign, verify, list) is covered, but missing a delete/update keystore tool is a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources