TenderHunt vs MCP Server
A side-by-side look at the TenderHunt and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TenderHuntSearch & Data Extraction · Remote HTTP/SSEBelarus public tenders: search, analytics, docs, and alerts via TenderHunt agent.39FairAuth: oauth 2.0Verdict: choose TenderHunt for search & data extraction work over a hosted endpoint; choose MCP Server 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?
TChoose TenderHunt 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 MCP Server when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ATLAS_API_BASE, ATLAS_API_KEY, ATLAS_TIMEOUT_MS, ATLAS_MAX_RETRIES. - You want tools like
search_tenders, get_tender, get_buyer.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TenderHunt | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 39/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | ATLAS_API_BASEATLAS_API_KEYATLAS_TIMEOUT_MSATLAS_MAX_RETRIES |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View TenderHunt | View MCP Server |
Tools & capabilities
TenderHunt tools
No tool names declared yet. Check the project README from the listing page.
MCP Server tools 8
search_tendersSearch public procurement tenders from BZP (Biuletyn Zamówień Publicznych) and TED (Tenders Electronic Daily) via Atlas Przetargów. Returns a list with titles, buyers, locations, CPV codes, estimated values and deadlines. Use for queries like 'aktywne przetargi budowlane w Warszawie', 'zamówienia IT powyżej 500k PLN', 'co kupuje ZUS'.get_tenderRetrieve detailed information about a specific Polish public tender by its ID. Returns buyer, location, deadlines, estimated value, CPV codes, contractor (if awarded), notice type and a content excerpt. Optionally includes AI-generated summary points (requires ATLAS_API_KEY).get_buyerFetch a profile of a Polish public procuring entity (zamawiający) by its NIP (tax ID). Returns name, location, statistics, recent tenders, and top winning contractors. Use for due diligence on who buys what and from whom.get_contractorFetch a profile of a Polish tender contractor by its NIP. Returns name, location, total wins, total value and top buyers they win tenders from.search_entitiesSearch Polish public procurement entities (buyers / zamawiający) or contractors (wykonawcy) by name. Returns a list with NIP, location and volume. Useful to find the NIP for get_buyer / get_contractor tools.get_category_statsRetrieve aggregate statistics for a CPV category: count, average/median value, average number of offers, average deadline period. Based on historical BZP+TED data. Useful for market sizing and competitive benchmarking.get_province_statsRetrieve aggregate tender statistics by Polish province (all 16 voivodeships) or drill down to a specific city (top buyers, top CPV categories). Without arguments returns the full province ranking.search_cpvLook up CPV (Common Procurement Vocabulary — EU procurement category) codes by Polish keyword. Use this before search_tenders to find the right CPV filter. Returns code, name, division, and historical tender count.
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.
TenderHunt
{
"mcpServers": {
"tenderhunt": {
"command": "npx",
"args": [
"-y",
"tenderhunt"
]
}
}
}
MCP Server
{
"mcpServers": {
"atlasprzetargow-mcp-server": {
"command": "npx",
"args": [
"-y",
"@atlasprzetargow/mcp"
],
"env": {
"ATLAS_API_BASE": "YOUR_ATLAS_API_BASE_HERE",
"ATLAS_API_KEY": "YOUR_ATLAS_API_KEY_HERE",
"ATLAS_TIMEOUT_MS": "YOUR_ATLAS_TIMEOUT_MS_HERE",
"ATLAS_MAX_RETRIES": "YOUR_ATLAS_MAX_RETRIES_HERE"
}
}
}
}
Frequently asked questions
TenderHunt is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. MCP Server belongs to Search & Data Extraction and uses a local stdio subprocess. Pick TenderHunt for search & data extraction work and MCP Server 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.
TenderHunt has no declared pricing — check the project's own site. Auth: oauth 2.0. MCP Server is listed as free. Auth: api key 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 tenderhunt and atlasprzetargow-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TenderHunt has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Server has 65/100 (Great) with 7 views, 0 installs and 4 GitHub stars.