Home / MCP registry index / pl.przetargowyjanusz/tenders
Przetargowy Janusz — Polish public tenders
pl.przetargowyjanusz/tenders in the official MCP registry.
Endpoint https://przetargowyjanusz.pl/mcp.
The registry describes it as: Polish tenders: search, AI summaries. Trial/paid: matched tenders, pipeline, archive, doc filling
We read its 25 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_tenders list_tenders list_facets get_tender search_entities get_buyer get_contractor cpv_stats cpv_search cpv_tree cpv_labels list_my_tenders list_my_alerts search_my_tenders list_matched_tenders get_my_tender list_tender_files get_tender_file get_tender_documents add_to_my_tenders set_tender_status request_summary start_fill set_fill_details confirm_bid_price
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/pl-przetargowyjanusz-tenders)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.