Data Gleaner vs Signal Lab Apify Tools
A side-by-side look at the Data Gleaner and Signal Lab Apify Tools MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
Data GleanerSearch & Data ExtractionPay-per-result web data tools: company and YouTube contacts, hotel prices, Weibo and Bilibili.36FairAuth: oauth 2.0Verdict: choose Data Gleaner for search & data extraction work; choose Signal Lab Apify Tools for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
DChoose Data Gleaner when
- You need dedicated capabilities in the Search & Data Extraction domain.
- Its auth model fits you: OAuth 2.0.
Choose Signal Lab Apify Tools when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
APIFY_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | D Data Gleaner | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 36/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | APIFY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Data Gleaner | View Signal Lab Apify Tools |
Tools & capabilities
Data Gleaner tools
No tool names declared yet. Check the project README from the listing page.
Signal Lab Apify Tools tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Data Gleaner
No confirmed install command for Data Gleaner yet — follow the setup steps linked from its listing page rather than a guessed package name.
Signal Lab Apify Tools
{
"mcpServers": {
"signal-lab-apify-tools": {
"command": "npx",
"args": [
"-y",
"askill-cli"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Data Gleaner is categorized under Search & Data Extraction and uses an install path we have not confirmed yet. Signal Lab Apify Tools belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Data Gleaner for search & data extraction work and Signal Lab Apify Tools for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Data Gleaner has no confirmed install command yet — follow its own setup instructions.
Data Gleaner has no declared pricing — check the project's own site. Auth: oauth 2.0. Signal Lab Apify Tools is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add data-gleaner and signal-lab-apify-tools as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Data Gleaner has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Signal Lab Apify Tools has 53/100 (Good) with 3 views, 0 installs and 0 GitHub stars.