io.github.atlasprzetargow/mcp
NPM · @ATLASPRZETARGOW/MCP
Polish public tenders (BZP, TED): 1M+ notices, buyer and contractor profiles, CPV, stats, glossary.
Available components
Last scanned (18 hours ago)
Scores higher than 63% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1897 tokens (~189/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- Stability: pass → 0.97 functional
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- Stability: 0.97 → pass security
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@atlasprzetargow/mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_buyer Get profile of a procuring entity (zamawiający) ~117
Fetch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_winning_contractors | boolean | – | If true, also fetch the list of contractors that most frequently win this buyer's tenders. Default: true. |
| nip | string | yes | Polish tax ID (NIP) of the procuring entity — 10 digits |
No output schema declared.
No examples provided.
get_category_stats Get tender statistics for a CPV category ~115
Retrieve 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cpv | string | yes | CPV code or prefix, e.g. '45' (construction), '72' (IT), '45240000-1' |
| window | string | – | Statistics window: month=30d, quarter=90d, year=365d. Default: year |
No output schema declared.
No examples provided.
get_contractor Get profile of a contractor (wykonawca) ~94
Fetch a profile of a Polish tender contractor by its NIP. Returns name, location, total wins, total value and top buyers they win tenders from.
| Name | Type | Req | Description |
|---|---|---|---|
| include_winning_buyers | boolean | – | If true, also fetch the list of buyers this contractor most frequently wins tenders from. Default: true. |
| nip | string | yes | Polish tax ID (NIP) of the contractor — 10 digits |
No output schema declared.
No examples provided.
get_province_stats Get tender statistics by province or city ~94
Retrieve 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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | If provided, returns top buyers and top CPV categories for this city instead. |
| province | string | – | Province code like 'PL14'. If omitted, returns totals for ALL provinces. |
No output schema declared.
No examples provided.
get_tender Get full details of a public tender ~137
Retrieve 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).
| Name | Type | Req | Description |
|---|---|---|---|
| include_ai_summary | boolean | – | If true and ATLAS_API_KEY is configured, attach AI-generated summary of the tender notice. Default: false. |
| tender_id | string | yes | Tender ID in BZP format '2026/BZP 00202613' or dashed '2026-BZP-00202613'. TED IDs are also supported. |
No output schema declared.
No examples provided.
search_cpv Search CPV codes by keyword ~111
Look 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (1-30, default 10) |
| query | string | yes | Search term for CPV (Common Procurement Vocabulary) codes — keyword in Polish, e.g. 'komputer', 'budowa drogi', 'usługi prawne' |
No output schema declared.
No examples provided.
search_entities Search procuring entities or contractors by name ~140
Search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (1-30, default 10) |
| query | string | yes | Name (or fragment) of the entity to search, e.g. 'warszawa', 'gddkia', 'budimex' |
| type | string | – | Limit to buyers (zamawiający), contractors (wykonawcy), or both. Default: all |
No output schema declared.
No examples provided.
search_tenders Search Polish public tenders ~503
Search 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'.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerNip | string | – | NIP (tax ID) of the procuring entity (zamawiający) |
| city | string | – | City name, e.g. 'Warszawa', 'Kraków' |
| cpv | string | – | CPV code prefix or full code. Examples: '45' (roboty budowlane), '72' (IT services), '45240000-1' |
| dateFrom | string | – | ISO date YYYY-MM-DD — filter publications from |
| dateTo | string | – | ISO date YYYY-MM-DD — filter publications to |
| limit | integer | – | Max results per page (1-50, default 20) |
| noticeType | string | – | ContractNotice = active tender; TenderResultNotice/ContractAwardNotice = results |
| orderKind | string | – | Kind of procurement: works (roboty), supplies (dostawy), services (usługi) |
| page | integer | – | Page number (default 1) |
| province | string | – | Polish province code: PL02 dolnośląskie, PL04 kujawsko-pomorskie, PL06 lubelskie, PL08 lubuskie, PL10 łódzkie, PL12 małopolskie, PL14 mazowieckie, PL16 opolskie, PL18 podkarpackie, PL20 podlaskie, PL… |
| query | string | – | Full-text search query (Polish terms work best), e.g. 'budowa drogi', 'komputer' |
| sort | string | – | Sort order (default: newest) |
| valueMax | number | – | Maximum estimated value in PLN |
| valueMin | number | – | Minimum estimated value in PLN |
No output schema declared.
No examples provided.
How do I install the io.github.atlasprzetargow/mcp server?
io.github.atlasprzetargow/mcp runs locally as an npm package, launched with npx -y @atlasprzetargow/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @atlasprzetargow/mcp
claude mcp add atlasprzetargow-mcp -- npx -y @atlasprzetargow/mcp
What is the io.github.atlasprzetargow/mcp server?
io.github.atlasprzetargow/mcp is listed in the public MCP registry as io.github.atlasprzetargow/mcp. Polish public tenders (BZP, TED): 1M+ notices, buyer and contractor profiles, CPV, stats, glossary. This page covers its npm package (@atlasprzetargow/mcp).
Is the io.github.atlasprzetargow/mcp server safe to use?
io.github.atlasprzetargow/mcp scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.atlasprzetargow/mcp server expose?
io.github.atlasprzetargow/mcp exposes 8 tools: search_tenders, get_tender, get_buyer, get_contractor, search_entities, and 3 more. Their descriptions and schemas cost roughly 1,311 tokens of context every time the server is loaded.
Is the io.github.atlasprzetargow/mcp server still maintained?
io.github.atlasprzetargow/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.atlasprzetargow/mcp server under?
io.github.atlasprzetargow/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.atlasprzetargow/mcp server?
VerifyMCP ran 16 checks on io.github.atlasprzetargow/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.