Levirge Search
Web search and page reading for AI agents, including JSON APIs, RSS feeds and YouTube.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
claude mcp add --transport http levirge-search 'https://search.levirge.com/mcp'
{
"mcpServers": {
"levirge-search": {
"type": "http",
"url": "https://search.levirge.com/mcp"
}
}
}
التوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
المحتويات
Levirge Search — web research your agent can actually reach
Search the web and read the sources, with citations.
Levirge Search is a hosted MCP server for research: unfiltered web search, and a URL fetch where pages that need JavaScript or refuse plain requests are opened in a full browser — so your agent can open the original source and cite it.
Install (2 minutes)
Claude Code:
claude plugin marketplace add levirge/search
claude plugin install levirge-search@levirge-search
Then run /mcp in a session and sign in.
Codex CLI:
codex plugin add levirge/search
Any other MCP client — point it at https://search.levirge.com/mcp. It answers a standard OAuth
challenge, so clients that speak MCP authorization discover sign-in on their own; no token to paste.
Update
plugin install won't upgrade, and the desktop "Update" button stays greyed out until the app's
marketplace cache is refreshed (the dialog has no refresh button). From the CLI — it shares the same
store as the desktop app:
claude plugin marketplace update levirge-search
claude plugin update levirge-search@levirge-search
Then restart the client — the plugin registry and MCP tool schemas are cached at startup, so new commands and tool params don't appear until then.
What you get
- Search that isn't a summary —
searchruns SearXNG across engines and returns real result sets, not one provider's ranking. - Fetch that opens the page —
fetchtakes any URL, including agent-constructed API endpoints; pages that need JavaScript or refuse plain requests are opened in a full browser. One tool, both routes. - Background scans —
fetch_asyncqueues up to 200 URLs through the same routing and paces them per-domain; collect withfetch_resultsinstead of blocking. - A stealth registry that learns — domains that needed the full browser are remembered per
tenant, so the second visit skips the retry (
/levirge-search:stealth). - A failure queue worth reading —
stealth_failureslists domains where the stealth browser itself got blocked, including regressions on domains that used to work. - A skill that fires on refusal —
web-fetch-fallbackteaches the agent to reach for this when its primary fetch says "blocked", instead of silently falling back to search.
Commands
| Command | Does |
|---|---|
/levirge-search:research | Multi-query search, fetch the top hits, synthesize with sources |
/levirge-search:fetch | Fetch one URL via routed fetch and summarize it |
/levirge-search:stealth | List stealth-required domains, or register one |
Links
- App / sign in: https://search.levirge.com
- Levirge: https://levirge.com
- Plugin reference: plugins/levirge-search/README.md
الأسئلة الشائعة
ما هو Levirge Search؟
Web search and page reading for AI agents, including JSON APIs, RSS feeds and YouTube.
كيف أثبّت Levirge Search؟
يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http levirge-search 'https://search.levirge.com/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.
هل يحتاج Levirge Search إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل Levirge Search مفتوح المصدر؟
شيفرته علنية على GitHub، لكن المستودع لا يعلن ترخيصًا قياسيًا.
من يصون Levirge Search؟
ينشره levirge. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.