Skip to content

Parser Club MCP server

club.parser/parser-clubparser.clubstreamable-httpv1.0.1Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Parser Club MCP server can do

The Parser Club MCP server is published by parser.club, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: telegram_niches and create_task), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • create_taskStart a data collection run and return its id.No findings

    Why it is in this group

    • The name "create_task" says "create": a word for a change.
    Description, as the server wrote it
    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.
  • telegram_nichesOpen 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 …No findings

    Why it is in this group

    • The description's first verb is "open": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • describe_serviceWhat Parser Club can collect, for which countries, and what it deliberately cannot do.No findings

    Why it is in this group

    • The name "describe_service" says "describe": a word for reading.
    Description, as the server wrote it
    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.
  • get_taskStatus and progress of one task created earlier.No findings

    Why it is in this group

    • The name "get_task" says "get": a word for reading.
    Description, as the server wrote it
    Status and progress of one task created earlier. Requires an API key.
  • get_task_resultRows collected by a finished task.No findings

    Why it is in this group

    • The name "get_task_result" says "get": a word for reading.
    Description, as the server wrote it
    Rows collected by a finished task. Returns a page of results plus the total count. Requires an API key.
  • list_task_kindsList the collection tasks this account may run, with the parameter names each one accepts.No findings

    Why it is in this group

    • The name "list_task_kinds" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://parser.club/api/mcp: tools/list returned 6 tools to an anonymous client, including telegram_niches (write), create_task (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 2
    • Protocol version: none to 2025-06-18
  2. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 2
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http parser-club https://parser.club/api/mcp
claude mcp add --transport http parser-club https://parser.club/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__parser-club__describe_service",
      "mcp__parser-club__list_task_kinds",
      "mcp__parser-club__get_task",
      "mcp__parser-club__get_task_result"
    ],
    "ask": [
      "mcp__parser-club__telegram_niches",
      "mcp__parser-club__create_task"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as parser-club. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/club.parser/parser-club/verify?hash=14163c38a925cbd53664136ec83bfa3dd95691b6bf01e620224d5f4d0bb3934d" | jq -e '.changed == false'

Pinned hash 14163c38a925, from Nov 12, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/club.parser/parser-club/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for club.parser/parser-club
[![Anlyon Radar](https://radar.anlyon.com/badge/club.parser/parser-club.svg)](https://radar.anlyon.com/servers/club.parser/parser-club)

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

Parser Club MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Parser Club MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Parser Club MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Parser Club MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Parser Club MCP server have?

6 tools: 2 write, 4 read. telegram_niches, create_task, describe_service, list_task_kinds, get_task and get_task_result.

Does the Parser Club MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Parser Club MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Parser Club MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.