BidSkim vs Ocds MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
BidSkim vs Ocds MCP
In-depth architectural comparison of the BidSkim and Ocds MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
BidSkim
Search & Data Extraction · Remote HTTP/SSE
Quality: 40/100 (Fair) | Auth: OAuth 2.0
Ocds MCP
Search & Data Extraction · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose BidSkim if you need specialized Search & Data Extraction tools running via a hosted cloud SSE transport. Choose Ocds MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose BidSkim when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Paid Service).
UK procurement intelligence: 8 read-only tools for live tender search (keyword, CPV, region, value, deadline), semantic search, contract-renewal intelligence (expiry dates, incumbent suppliers, buyer contacts), buyer and supplier profiles, and the caller's saved pipeline. Covers Find a Tender, Contracts Finder, PCS and Sell2Wales, deduplicated to one record per opportunity.
German public procurement data (OCDS) — semantic search, tender matching with company profiles, and structured filtering.
Category & Scope
Tools & Capabilities Breakdown
BidSkim Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ocds MCP Tools (11)
search_text
Semantic search across all tenders (query embedded locally)
list_releases
Filter and browse tenders by phase, CPV prefix, country, value range, deadline, buyer, procurement method
get_release
Raw [eForms](https://vergabe-dashboard.qune.de/wissen/eforms/) XML envelope for one OCID (optional `notice_id` selects a sibling)
linked_notices
A procurement's notice lineage (PIN→CN→CAN) as `{ocid, notice_id}` refs
get_index_info
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
BidSkim is categorized under Search & Data Extraction and uses a remote streaming HTTP/SSE transport. In contrast, Ocds MCP belongs to Search & Data Extraction using local stdio subprocess. Select BidSkim when you need capabilities focused on search & data extraction and Ocds MCP when you require tools for search & data extraction.