Saliga data tools (Apify) vs Contendeo
A side-by-side look at the Saliga data tools (Apify) and Contendeo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Saliga data tools (Apify)Speech-to-TextPay-per-result data tools: bulk API calls, docs to Markdown, OCR, Whisper, sitemaps, tech stack.36FairAuth: api key requiredVerdict: choose Saliga data tools (Apify) for speech-to-text work; choose Contendeo for speech-to-text over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Saliga data tools (Apify) when
- You need dedicated capabilities in the Speech-to-Text domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
APIFY_TOKEN.
Choose Contendeo when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
quick_transcribe, deep_analyze, clip_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Saliga data tools (Apify) | |
|---|---|---|
| Category | Speech-to-Text | Speech-to-Text |
| Quality signal | 36/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | APIFY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Saliga data tools (Apify) | View Contendeo |
Tools & capabilities
Saliga data tools (Apify) tools
No tool names declared yet. Check the project README from the listing page.
Contendeo tools 4
quick_transcribeTimestamped transcript with speaker identification. Audio-only. Fast.deep_analyzeFull multimodal pipeline — transcript + keyframe vision + OCR, unified output.clip_contextAnalyze a specific timestamp range without paying for the full video.batch_analyzeProcess up to 10 videos in parallel with cross-video synthesis.
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.
Saliga data tools (Apify)
No confirmed install command for Saliga data tools (Apify) yet — follow the setup steps linked from its listing page rather than a guessed package name.
Contendeo
{
"mcpServers": {
"contendeo": {
"url": "https://contendeo.app/mcp/"
}
}
}
Frequently asked questions
Saliga data tools (Apify) is categorized under Speech-to-Text and uses an install path we have not confirmed yet. Contendeo belongs to Speech-to-Text and uses a remote HTTP/SSE transport. Pick Saliga data tools (Apify) for speech-to-text work and Contendeo for speech-to-text.
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. Saliga data tools (Apify) has no confirmed install command yet — follow its own setup instructions.
Saliga data tools (Apify) is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Contendeo has no declared pricing — check the project's own site. 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 saliga-data-tools-apify and contendeo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Saliga data tools (Apify) has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Contendeo has 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.