Cv.json — open CV data vs Open WebSearch
A side-by-side look at the Cv.json — open CV data and Open WebSearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cv.json — open CV data for search & data extraction work as a local process; choose Open WebSearch 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 Cv.json — open CV data when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Choose Open WebSearch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search, fetchLinuxDoArticle, fetchCsdnArticle.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 43/100 · Fair | 72/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 1,873 |
| Directory activity | 1 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Cv.json — open CV data | View Open WebSearch |
Tools & capabilities
Cv.json — open CV data tools
No tool names declared yet. Check the project README from the listing page.
Open WebSearch tools 6
searchSearch the web using multiple engines (e.g., Baidu, Bing, DuckDuckGo, CSDN, Exa, Brave, Juejin(掘金), Startpage, Sogou(搜狗)) with no API key required. searchMode meanings: omit or set auto to use the server configured SEARCH_MODE; request forces request-based search; playwright forces browser-based search.fetchLinuxDoArticleFetch full article content from a linux.do post URLfetchCsdnArticleFetch full article content from a csdn post URLfetchGithubReadmeFetch README content from a GitHub repository URLfetchWebContentFetch content from a public HTTP(S) URL (supports Markdown files and normal web pages)fetchJuejinArticleFetch full article content from a Juejin(掘金) post URL
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.
Cv.json — open CV data
{
"mcpServers": {
"cv-json-open-cv-data": {
"command": "npx",
"args": [
"-y",
"ajv-cli"
]
}
}
}
Open WebSearch
{
"mcpServers": {
"aas-ee-open-websearch": {
"command": "npx",
"args": [
"-y",
"open-websearch@latest"
]
}
}
}
Frequently asked questions
Cv.json — open CV data is categorized under Search & Data Extraction and uses a local stdio subprocess. Open WebSearch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Cv.json — open CV data for search & data extraction work and Open WebSearch 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.
Cv.json — open CV data has no declared pricing — check the project's own site. Open WebSearch is listed as free. Auth: no auth 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 cv-json-open-cv-data and aas-ee-open-websearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cv.json — open CV data has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 4 GitHub stars. Open WebSearch has 72/100 (Great) with 8 views, 0 installs and 1,873 GitHub stars.