Parser Club
REMOTE · PARSER.CLUB
Telegram/VK audience scraping, marketplaces, Russian government registers. Free open dataset.
Available components
Last scanned (18 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Web Scraping
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 515 tokens (~85/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 16 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Oct 26 +1
- Stability: 0.93 → pass security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 93. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +13
- Transport: fail → pass ▲ security
- HSTS header: fail → pass ▲ security
- Authorization: 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. security
- 1 Oct 26 64
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://parser.club/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=parser.club | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 612da18d68d500b3c5bf05a409ebe258cb6 |
| SANs: parser.club | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of parser.club. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| club. | present | 679 | 13 | Verified |
| parser.club. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' https://web.telegram.org https://*.telegram.org |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://parser.club/api/mcp | Verified | 200 | |
| http (plaintext) | http://parser.club/api/mcp | HTTPS enforced | 308 | https://parser.club/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_task ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | 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. |
No output schema declared.
No examples provided.
describe_service ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_task ~35
Status and progress of one task created earlier. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Id returned by create_task. |
No output schema declared.
No examples provided.
get_task_result ~60
Rows collected by a finished task. Returns a page of results plus the total count. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows per page, default 50. |
| offset | integer | – | – |
| task_id | integer | yes | – |
No output schema declared.
No examples provided.
list_task_kinds ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
telegram_niches ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many niches to return, ordered by reach. Default 36 (all). |
No output schema declared.
No examples provided.
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.
remote · parser.club
claude mcp add --transport http club-parser-parser-club 'https://parser.club/api/mcp'
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 80 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.