Play Release Blocker Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.5Updated Oct 24, 2026

Finds the lines that make Google Play reject your release - target API below 36, Billing Library bel

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that scans an Android project for lines that would make Google Play reject a release.

What you can do
It inspects project files and points out the specific lines that violate Google Play release requirements, such as a target API level below 36 or an outdated Billing Library version. The registry description is truncated, so the full set of checks is not documented here. It runs as a local stdio process with no declared tools list.
When to use it
Worth adding when preparing an Android app for a Google Play submission and you want the assistant to flag likely policy blockers before uploading. It is a pre-release check, not a general linting or build tool.
Requirements
Runs locally as an npm package via npx, so Node.js and network access to fetch the package are needed. No authentication, environment variables, or headers are declared. Desktop only.
Before you install
The README shown here describes VS Code themes rather than this tool, so the documentation does not match the server and its actual behavior cannot be verified from the supplied material. It reads project files locally; review what it accesses before running it on a private codebase.

Installation

In SourceWeft

  1. Open Play Release Blocker Lint 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

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

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

Version history

3
  1. v0.1.5LatestSep 23, 2026
  2. v0.1.3Sep 19, 2026
  3. v0.1.1Sep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.