Skip to main content
ClaudeWave

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

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/12/2026
Install in Claude Code / Claude Desktop
Method: NPX · @pipeworx/mcp-42matters
Claude Code CLI
claude mcp add mcp-42matters -- npx -y @pipeworx/mcp-42matters
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "mcp-42matters": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-42matters"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# mcp-42matters

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

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1558+ live data sources.

## Tools

| Tool | Description |
|------|-------------|
| `fortytwo_app_lookup` | 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" }) |
| `fortytwo_app_search` | 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" }) |
| `fortytwo_top_charts` | 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" }) |
| `fortytwo_apps_by_sdk` | 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" }) |

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "42matters": {
      "url": "https://gateway.pipeworx.io/42matters/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/42matters/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1558+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no
gateway round-trip:

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

Or run it directly to confirm it starts:

```bash
npx -y @pipeworx/mcp-42matters
```

It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
for **only** this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about 42matters data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT
42mattersmcpmcp-servermodel-context-protocolpipeworx

Lo que la gente pregunta sobre mcp-42matters

¿Qué es pipeworx-io/mcp-42matters?

+

pipeworx-io/mcp-42matters es mcp servers para el ecosistema de Claude AI. 42matters MCP — wraps the 42matters App Market Data API (42matters.com) Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-09-11.

¿Cómo se instala mcp-42matters?

+

Puedes instalar mcp-42matters clonando el repositorio (https://github.com/pipeworx-io/mcp-42matters) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar pipeworx-io/mcp-42matters?

+

Nuestro agente de seguridad ha analizado pipeworx-io/mcp-42matters y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene pipeworx-io/mcp-42matters?

+

pipeworx-io/mcp-42matters es mantenido por pipeworx-io. La última actividad registrada en GitHub es del 2026-09-11, con 0 issues abiertos.

¿Hay alternativas a mcp-42matters?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega mcp-42matters en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: pipeworx-io/mcp-42matters
[![Featured on ClaudeWave](https://claudewave.com/api/badge/pipeworx-io-mcp-42matters)](https://claudewave.com/repo/pipeworx-io-mcp-42matters)
<a href="https://claudewave.com/repo/pipeworx-io-mcp-42matters"><img src="https://claudewave.com/api/badge/pipeworx-io-mcp-42matters" alt="Featured on ClaudeWave: pipeworx-io/mcp-42matters" width="320" height="64" /></a>

Más MCP Servers

Alternativas a mcp-42matters