BidSkim vs Kagimcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
BidSkim vs Kagimcp
In-depth architectural comparison of the BidSkim and Kagimcp 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: 72/100 (Great) | Auth: OAuth 2.0
Kagimcp
Search & Data Extraction · Local stdio
Quality: 80/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose BidSkim if you need specialized Search & Data Extraction tools running via a hosted cloud SSE transport. Choose Kagimcp 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.
Tools & Capabilities Breakdown
BidSkim Tools (6)
Eight read-only procurement tools
Keyword, CPV, region, value, and deadline search
Semantic tender search
Contract-renewal intelligence
Buyer and supplier profiles
Deduplicated UK opportunity records
Kagimcp Tools (2)
kagi_search_fetch
Fetch web results for a query using the Kagi Search API. Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are numbered so that a user may refer to a result by a specific number.
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, Kagimcp belongs to Search & Data Extraction using local stdio subprocess. Select BidSkim when you need capabilities focused on search & data extraction and Kagimcp when you require tools for search & data extraction.