Lyrenth MCP vs Sifter
A side-by-side look at the Lyrenth MCP and Sifter MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
SifterSearch & Data Extraction · Local subprocess (stdio)Structure any document, query it like a database. Open-source extraction engine that turns any document into typed, schema-defined records, queryable in natural language from Claude, ChatGPT, Gemini, or any MCP client.55GoodAuth: api key requiredVerdict: choose Lyrenth MCP for search & data extraction work as a local process; choose Sifter 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?
Choose Lyrenth MCP 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:
LYRENTH_API_KEY, LYRENTH_API_URL. - You want tools like
read_url, read_urls, check_usage.
Choose Sifter 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:
SIFTER_API_KEY, SIFTER_DEFAULT_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Sifter | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 59/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Freemium |
| Required env vars | LYRENTH_API_KEY |
Tools & capabilities
Lyrenth MCP tools 3
read_urlRead any public web page as a clean AIDocument: Markdown plus title, description, and structure, with navigation and boilerplate stripped. Prefer this over a raw HTTP fetch whenever you need the content of a web page; it returns far cleaner, lower-token text. Powered by Lyrenth.read_urlsRead several public web pages in one batch call, each as a clean AIDocument. Up to 20 URLs, faster than calling read_url repeatedly. Use it to compare or summarize multiple pages at once; a failed URL is reported per-item and does not block the others. Powered by Lyrenth.check_usageCheck your Lyrenth credit usage: plan tier, credits used against your monthly limit, credits remaining, and the reset date. Takes no arguments.
Sifter 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.
Lyrenth MCP
{
"mcpServers": {
"lyrenth-lyrenth-mcp": {
"command": "npx",
"args": [
"-y",
"lyrenth-mcp"
],
"env": {
"LYRENTH_API_KEY": "YOUR_LYRENTH_API_KEY_HERE",
"LYRENTH_API_URL": "YOUR_LYRENTH_API_URL_HERE"
}
}
}
}
Sifter
{
"mcpServers": {
"sifter-ai-sifter": {
"command": "uvx",
"args": [
"sifter-mcp"
],
"env": {
"SIFTER_API_KEY": "YOUR_SIFTER_API_KEY_HERE",
"SIFTER_DEFAULT_API_KEY": "YOUR_SIFTER_DEFAULT_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Lyrenth MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Sifter belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Lyrenth MCP for search & data extraction work and Sifter 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.
Lyrenth MCP is listed as free. Auth: api key required. Sifter is listed as freemium — a free tier with paid plans. 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 lyrenth-lyrenth-mcp and sifter-ai-sifter as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lyrenth MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Sifter has 55/100 (Good) with 1 views, 0 installs and 54 GitHub stars.