Data Collection
parser.club
Parser Club MCP server provides tools to configure and run data collection tasks across specified countries, returning task IDs and progress while documenting what it cannot do.
ENDPOINT 1
https://parser.club/api/mcp
MCP server metadata
- Name
- parser-club
- Version
- 1.0.0
Data collection for Telegram (worldwide), plus VKontakte, Wildberries, HH.ru, business directories and Russian state registers (Russia and the CIS only). Call describe_service first to check the country fits. Running a collection spends the user's paid quota - ask before calling create_task.
Known tools 6
describe_serviceWhat Parser Club can collect, for which countries, and what it deliberately cannot do.
Inferred read-onlylist_task_kindsList the collection tasks this account may run, with the parameter names each one accepts.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.parser-club]
url = "https://parser.club/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"parser-club": {
"type": "http",
"url": "https://parser.club/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: parser-club
Remote MCP URL: https://parser.club/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"parser-club": {
"url": "https://parser.club/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"parser-club": {
"type": "http",
"url": "https://parser.club/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "parser-club",
"transport": "streamable-http",
"url": "https://parser.club/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.