BidSkim vs Cv.json — open CV data
A side-by-side look at the BidSkim and Cv.json — open CV data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BidSkim for search & data extraction work over a hosted endpoint; choose Cv.json — open CV data 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 BidSkim when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Cv.json — open CV data when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 72/100 · Great | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | — | 4 |
| Directory activity | 6 views 0 installs 1 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View BidSkim | View Cv.json — open CV data |
Tools & capabilities
BidSkim tools
No tool names declared yet. Check the project README from the listing page.
Cv.json — open CV data 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.
BidSkim
{
"mcpServers": {
"bidskim": {
"url": "https://bidskim.com/mcp"
}
}
}
Cv.json — open CV data
{
"mcpServers": {
"cv-json-open-cv-data": {
"command": "npx",
"args": [
"-y",
"ajv-cli"
]
}
}
}
Frequently asked questions
BidSkim is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Cv.json — open CV data belongs to Search & Data Extraction and uses a local stdio subprocess. Pick BidSkim for search & data extraction work and Cv.json — open CV data 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.
BidSkim is listed as a paid service. Auth: oauth 2.0. Cv.json — open CV data has no declared pricing — check the project's own site. 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 bidskim and cv-json-open-cv-data as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BidSkim has a quality signal of 72/100 (Great) with 6 views, 0 installs and 0 GitHub stars. Cv.json — open CV data has 43/100 (Fair) with 1 views, 0 installs and 4 GitHub stars.