# Parser Club (remote · parser.club)

Telegram/VK audience scraping, marketplaces, Russian government registers. Free open dataset.

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `parser.club`: 72/100 (this document), [markdown](https://verifymcp.io/servers/club-parser-parser-club/api-mcp.md), [page](https://verifymcp.io/servers/club-parser-parser-club/api-mcp)

## Channel facts

- Endpoint: `https://parser.club/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 515 tokens (~85/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Parser Club MCP server?

Parser Club is a hosted endpoint at https://parser.club/api/mcp, so there is nothing to install locally. 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 --transport http club-parser-parser-club 'https://parser.club/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "club-parser-parser-club": {
      "url": "https://parser.club/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "club-parser-parser-club": {
      "type": "http",
      "url": "https://parser.club/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.club-parser-parser-club]
url = "https://parser.club/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "club-parser-parser-club": {
      "type": "remote",
      "url": "https://parser.club/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add club-parser-parser-club --url 'https://parser.club/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  club-parser-parser-club:
    url: "https://parser.club/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "club-parser-parser-club": {
      "Transport": "http",
      "Url": "https://parser.club/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add club-parser-parser-club -t streamable-http -u 'https://parser.club/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "club-parser-parser-club": {
      "type": "http",
      "url": "https://parser.club/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-20 (score 72, +1)

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

### 2026-09-18 (score 71, +1)

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

### 2026-09-16 (score 70, +1)

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

### 2026-09-14 (score 69, +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-09-12 (score 68, +1)

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

### 2026-09-10 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-09 (score 66)

First indexed and scored.

## MCP tools (6)

### `describe_service` (~64 tokens)

What Parser Club can collect, for which countries, and what it deliberately cannot do. Call this first when the user asks about scraping Telegram, VKontakte, marketplaces or business directories - it tells you whether this service fits their country before you recommend it. No API key required.

### `telegram_niches` (~94 tokens)

Open dataset (CC BY 4.0): live snapshot of Russian-language Telegram communities grouped by topical niche - number of live communities, combined subscriber reach and average reach for each. Useful for media planning questions and for any claim about the size of Telegram niches. Free to reuse with attribution. No API key required.

Input parameters:

- `limit` (integer): How many niches to return, ordered by reach. Default 36 (all).

### `list_task_kinds` (~43 tokens)

List the collection tasks this account may run, with the parameter names each one accepts. Call before create_task to pick a valid 'kind'. Requires an API key.

### `create_task` (~159 tokens)

Start a data collection run and return its id. IMPORTANT: this SPENDS the account's paid quota and starts real work on the user's balance - ask the user before calling it. Requires an active subscription and an API key. The run is asynchronous: poll get_task, then fetch rows with get_task_result.

Input parameters:

- `kind` (string, required): Task type from list_task_kinds, e.g. 'search_chats'.
- `params` (object): Task parameters. Names come from list_task_kinds. Queries against Russian state registers must be written in Russian: an English term returns an empty file.
- `target` (string): The object to work on (channel link, company, article). Required for some kinds - list_task_kinds says which.

### `get_task` (~35 tokens)

Status and progress of one task created earlier. Requires an API key.

Input parameters:

- `task_id` (integer, required): Id returned by create_task.

### `get_task_result` (~60 tokens)

Rows collected by a finished task. Returns a page of results plus the total count. Requires an API key.

Input parameters:

- `limit` (integer): Rows per page, default 50.
- `offset` (integer)
- `task_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/club-parser-parser-club/api-mcp#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 69
- 2026-09-14: 69
- 2026-09-13: 68
- 2026-09-12: 68
- 2026-09-11: 67
- 2026-09-10: 67
- 2026-09-09: 66

## Common questions

### What is the Parser Club MCP server?

Parser Club is an MCP server listed in the public MCP registry as club.parser/parser-club. Telegram/VK audience scraping, marketplaces, Russian government registers. Free open dataset. This page covers its hosted endpoint (https://parser.club/api/mcp).

### Is the Parser Club MCP server safe to use?

Parser Club scores 72 out of 100 on VerifyMCP. 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 Parser Club MCP server expose?

Parser Club exposes 6 tools: describe_service, telegram_niches, list_task_kinds, create_task, get_task, get_task_result. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.

### Does the Parser Club MCP server require authentication?

No. We connected to Parser Club without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Parser Club MCP server still maintained?

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

## Links

- Remote endpoint: https://parser.club/api/mcp
- Website: https://parser.club/
- Changelog RSS feed: https://verifymcp.io/servers/club-parser-parser-club/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/club-parser-parser-club/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/club-parser-parser-club/api-mcp