App Pain API vs Steamworks Release Assistant
App Pain API is an MCP server published by apppainapi. Marketplaces we read that list it: 1 (Official MCP Registry). Steamworks Release Assistant is an MCP server published by wazzapsenk. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  App Pain API |  Steamworks Release Assistant |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.1 Forks (GitHub): 0 (last published figure) Stars (GitHub): 2 (last published figure) Not marked · First seen |
Listed Version: 0.5.2 Downloads/month (PyPI): 274 Downloads/week (PyPI): 1 276 Forks (GitHub): 0 Stars (GitHub): 13 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.5.2 Downloads/month (PyPI): 274 Downloads/week (PyPI): 1 276 Forks (GitHub): 0 Stars (GitHub): 13 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | App Pain API | Steamworks Release Assistant |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (last published figure) | 13 |
| Forks (GitHub) (differs) | 0 (last published figure) | 0 |
| Last release (differs) | 2026-11-01 (worse) | 2026-11-05 (better) |
| Where it runs (differs) | Remote server (hawkmill.com/mcp) | On your machine (steamworks-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/apppainapi/app-pain-api | github.com/wazzapsenk/steamworks-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-23 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded less than an hour ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
App Pain API
What users hate about ANY iOS/Android app: clustered complaints, evidence, trends. No key needed.
Steamworks Release Assistant
Put a game on Steam: store page, achievements, Valve-rule checks, market data, Steamworks.
How to run each
App Pain API As a remote MCP server
claude mcp add --transport http app-pain-api https://hawkmill.com/mcp --header "x-api-key: <YOUR_X_API_KEY>"Requires: x-api-key header
Steamworks Release Assistant As a local MCP server: PyPI package
claude mcp add --env "STEAMWORKS_PUBLISHER_KEY=<YOUR_STEAMWORKS_PUBLISHER_KEY>" --transport stdio steamworks-mcp -- uvx steamworks-mcpRequires: STEAMWORKS_PUBLISHER_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only App Pain API has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of App Pain API publish no settings it asks for, so we do not compare settings.
What it can do: App Pain API · What it can do: Steamworks Release Assistant · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.