# 42matters (npm · @pipeworx/mcp-42matters)

42matters MCP — wraps the 42matters App Market Data API (42matters.com)

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-42matters/42matters-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-42matters/42matters-mcp)
- npm · `@pipeworx/mcp-42matters`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-42matters/pipeworx-mcp-42matters.md), [page](https://verifymcp.io/servers/pipeworx-io-42matters/pipeworx-mcp-42matters)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-42matters`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-42matters).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1069 tokens (~267/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the 42matters MCP server?

42matters runs locally as an npm package, launched with npx -y @pipeworx/mcp-42matters. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-42matters -- npx -y @pipeworx/mcp-42matters
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-42matters": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-42matters"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-42matters": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-42matters"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-42matters -- npx -y @pipeworx/mcp-42matters
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-42matters": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-42matters"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-42matters --command npx --arg -y --arg @pipeworx/mcp-42matters
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-42matters:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-42matters"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-42matters": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-42matters"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-42matters -t stdio -c npx -a -y @pipeworx/mcp-42matters
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-42matters": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-42matters"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, 0)

- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `fortytwo_app_lookup` (~228 tokens)

Look up full details for a single mobile app — title, developer, ratings, downloads/installs, category, price, and more. For Android pass the package name via `app_id` (e.g. "com.facebook.katana"); for iOS pass the numeric App Store id (e.g. "284882215"). Example: fortytwo_app_lookup({ platform: "android", app_id: "com.facebook.katana", _apiKey: "your-token" })

Input parameters:

- `_apiKey` (string, required): 42matters API access token (get one at https://42matters.com/pricing).
- `app_country` (string): Optional 2-letter country code for pricing/availability metadata (default "US").
- `app_id` (string, required): Android package name (e.g. "com.facebook.katana") or iOS App Store numeric id (e.g. "284882215").
- `platform` (string): App store to query: "android" (Google Play) or "ios" (Apple App Store). Defaults to "android".

### `fortytwo_app_search` (~177 tokens)

Search the app store by keyword and return matching apps with pagination. Example: fortytwo_app_search({ platform: "ios", query: "racing games", limit: 20, page: 1, _apiKey: "your-token" })

Input parameters:

- `_apiKey` (string, required): 42matters API access token (get one at https://42matters.com/pricing).
- `limit` (number): Results per page (1-50). Default 10.
- `page` (number): Page number for pagination (default 1).
- `platform` (string): App store to query: "android" (Google Play) or "ios" (Apple App Store). Defaults to "android".
- `query` (string, required): Search term, e.g. "racing games", "meditation".

### `fortytwo_top_charts` (~387 tokens)

Get a ranked top-chart list (top free, top paid, top grossing, etc.) for a country and category. Android uses `cat_key` (e.g. "OVERALL"); iOS uses `genre_id` (e.g. "36" for the overall/all-apps genre) plus optional `device_type`. Example: fortytwo_top_charts({ platform: "android", list_name: "topselling_free", cat_key: "OVERALL", country: "US", limit: 10, _apiKey: "your-token" })

Input parameters:

- `_apiKey` (string, required): 42matters API access token (get one at https://42matters.com/pricing).
- `cat_key` (string): Android only — category key, e.g. "OVERALL" or a Google Play category id. Default "OVERALL".
- `country` (string): 2-letter country code for the chart (default "US").
- `device_type` (string): iOS only — "iphone" or "ipad" (optional).
- `genre_id` (string): iOS only — App Store genre/category id (e.g. "36" for all apps).
- `limit` (number): Number of ranked results (1-100). Default 10.
- `list_name` (string): Chart type. Android: "topselling_free", "topselling_paid", "topgrossing", "movers_shakers", "topselling_new_free", "topselling_new_paid". iOS: "topselling_free", "topselling_paid", "topgrossing". Def…
- `page` (number): Page number for pagination (optional).
- `platform` (string): App store to query: "android" (Google Play) or "ios" (Apple App Store). Defaults to "android".

### `fortytwo_apps_by_sdk` (~221 tokens)

Find apps that integrate a given SDK. Pass one or more SDK ids via `sdk` (e.g. "google-ads-admob"). Useful for competitive/market-share analysis of ad networks, analytics, and other SDKs. Example: fortytwo_apps_by_sdk({ platform: "android", sdk: "google-ads-admob", limit: 20, _apiKey: "your-token" })

Input parameters:

- `_apiKey` (string, required): 42matters API access token (get one at https://42matters.com/pricing).
- `limit` (number): Results per page (default 10).
- `page` (number): Page number for pagination (optional).
- `platform` (string): App store to query: "android" (Google Play) or "ios" (Apple App Store). Defaults to "android".
- `sdk` (string, required): SDK id, or comma-separated SDK ids, to match (apps embedding ANY of them). e.g. "google-ads-admob", "facebook-sdk".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-42matters/pipeworx-mcp-42matters#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the 42matters MCP server?

42matters is an MCP server listed in the public MCP registry as io.github.pipeworx-io/42matters. 42matters MCP, wraps the 42matters App Market Data API (42matters.com). This page covers its npm package (@pipeworx/mcp-42matters).

### Is the 42matters MCP server safe to use?

42matters scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the 42matters MCP server expose?

42matters exposes 4 tools: fortytwo_app_lookup, fortytwo_app_search, fortytwo_top_charts, fortytwo_apps_by_sdk. Their descriptions and schemas cost roughly 1,013 tokens of context every time the server is loaded.

### Is the 42matters MCP server still maintained?

42matters is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the 42matters MCP server under?

42matters declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-42matters
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-42matters
- Repository: https://github.com/pipeworx-io/mcp-42matters
- Website: https://pipeworx.io/packs/42matters
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-42matters/pipeworx-mcp-42matters.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-42matters/pipeworx-mcp-42matters.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-42matters/pipeworx-mcp-42matters