SearchForge vs Search1api MCP
A side-by-side look at the SearchForge and Search1api MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SearchForge for search & data extraction work; choose Search1api MCP 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 SearchForge when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You have the keys it needs:
SEARCHFORGE_SEARXNG_URL, SEARCHFORGE_API_KEY.
Choose Search1api 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:
SEARCH1API_KEY. - You want tools like
search, news, crawl.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 40/100 · Fair | 67/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Paid service |
| Required env vars | SEARCHFORGE_SEARXNG_URLSEARCHFORGE_API_KEY | SEARCH1API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 173 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View SearchForge | View Search1api MCP |
Tools & capabilities
SearchForge tools
No tool names declared yet. Check the project README from the listing page.
Search1api MCP tools 5
searchSearch the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Pass a result URL to crawl to retrieve the full page.newsSearch current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.crawlExtract the readable title and full text from a public URL supplied by the user or returned by search.sitemapDiscover related public links from a page or domain when the user wants to explore a site's structure or available pages.trendingList currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.
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.
SearchForge
No confirmed install command for SearchForge yet — follow the setup steps linked from its listing page rather than a guessed package name.
Search1api MCP
{
"mcpServers": {
"fatwang2-search1api-mcp": {
"command": "npx",
"args": [
"-y",
"search1api-mcp"
],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE"
}
}
}
}
Frequently asked questions
SearchForge is categorized under Search & Data Extraction and uses an install path we have not confirmed yet. Search1api MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick SearchForge for search & data extraction work and Search1api MCP 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. SearchForge has no confirmed install command yet — follow its own setup instructions.
SearchForge has no declared pricing — check the project's own site. Search1api MCP is listed as a paid service. 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 divyanshu-iitian-searchforge and fatwang2-search1api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SearchForge has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Search1api MCP has 67/100 (Great) with 1 views, 0 installs and 173 GitHub stars.