My Websearch vs Search1API
A side-by-side look at the My Websearch and Search1API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose My Websearch for search & data extraction work; choose Search1API 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 My Websearch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- Its auth model fits you: No auth required.
- You want tools like
search, fetchWebContent, fetchGithubContent.
Choose Search1API when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- 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 | 67/100 · Great | 68/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | SEARCH1API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 174 |
| Directory activity | 7 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | 7 |
| Full listing | View My Websearch | View Search1API |
Tools & capabilities
My Websearch tools 4
searchSearch the web across multiple engines (Chinese/English/Code). Supports multi-query fan-out ('queries'), timeRange filtering, site limits, fetchTop article content, and no API keys required.fetchWebContentFetch readable web content/docs/PDFs from public URLs. Auto-cleans ads, keeps code/tables. Batch urls (1-3), CSS selector scoping, bm25 focus, startIndex paging, cache, schema extract to JSON, citations, link retention.fetchGithubContentFetch GitHub/Gitee by URL: README, source file (/blob/, with lines), tree, issue, PR, commit, compare, or releases. Example: https://github.com/o/r/blob/main/src/index.ts — ref can be branch/tag/commit; not a repo clone.queryDocsGet official docs, API references, and code snippets for libraries/packages (e.g. 'react', 'fastapi', 'next.js'). Queries Context7 with fallback to npm/PyPI registry and GitHub README. Direct, no proxy needed.
Search1API tools 7
searchSearch the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Each result includes a URL that can be read in full.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.askDescribe what you are looking for in natural language when you do not know which source to search. Search1API picks up to five engines (web, Hacker News, Reddit, GitHub, X, arXiv, Wikipedia, and more), infers a time window from phrases such as "this week", and returns at most 10 relevant results ranked by relevance. Costs 5 credits; use search when you already know the engine.render_resultsPresent already retrieved source results as source cards when the host supports UI, with a complete readable text list otherwise. Use when the user wants to browse sources or a visual list helps the task. Pass existing results in the desired order; never invent source URLs or factual titles. Does not search, crawl, fetch URLs, verify sources, or consume search credits. Do not call for intermediate research results or when a text answer is sufficient.
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.
My Websearch
No confirmed install command for My Websearch yet — follow the setup steps linked from its listing page rather than a guessed package name.
Search1API
{
"mcpServers": {
"search1api": {
"command": "npx",
"args": [
"-y",
"search1api-mcp@latest"
],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE"
}
}
}
}
Frequently asked questions
My Websearch is categorized under Search & Data Extraction and uses an install path we have not confirmed yet. Search1API belongs to Search & Data Extraction and uses a local stdio subprocess. Pick My Websearch for search & data extraction work and Search1API 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. My Websearch has no confirmed install command yet — follow its own setup instructions.
My Websearch is listed as free. Auth: no auth required. Search1API is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 my-websearch and search1api as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, My Websearch has a quality signal of 67/100 (Great) with 7 views, 0 installs and 3 GitHub stars. Search1API has 68/100 (Great) with 1 views, 0 installs and 174 GitHub stars.