io.github.ContentWriterco/kolejki-nfz-mcp
REMOTE · KOLEJKI.COMPABASE.COM · 2 COMPONENTS
NFZ waiting times in Poland: where a specialist, test or treatment is available soonest
Available components
Last scanned (4 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 24 Oct 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 628 tokens (~209/item across 3 items; 3 tools + 0 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 24 Oct 26 69
First indexed and scored.
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 24 Oct 2026 · Probed https://kolejki.compabase.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kolejki.compabase.com | CN=YE2,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5195c119330732d5598e9460657fca7691d |
| SANs: kolejki.compabase.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kolejki.compabase.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| compabase.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kolejki.compabase.com/mcp | Verified | 200 | |
| http (plaintext) | http://kolejki.compabase.com/mcp | HTTPS enforced | 308 | https://kolejki.compabase.com/mcp |
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 →
data_sources Data sources ~17
Where the data comes from and caveats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_benefits NFZ benefit names ~83
Look up official NFZ benefit names (clinics, wards, tests, procedures) matching a word, e.g. 'rezonans' or 'okulist'. Use the exact name as find_care.benefit.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Word or fragment, e.g. 'kardiolog', 'tomograf', 'zaćm' |
No output schema declared.
No examples provided.
find_care Shortest NFZ waiting times near a place ~319
Where a specialist, diagnostic test or treatment paid by NFZ is available soonest near a place in Poland. Returns clinics and hospitals with NFZ's forecast waiting time, people in the queue, address, phone, distance, accessibility and whether children are seen. service: everyday words (okulista, kardiolog, rezonans, zaćma, rehabilitacja…) or an exact NFZ benefit name from find_benefits. place: town, address or 'lat,lon'.
| Name | Type | Req | Description |
|---|---|---|---|
| benefit | string | – | Exact NFZ benefit name (from find_benefits / 'Inne pasujące świadczenia') – overrides service matching |
| children | boolean | – | Patient is a child – searches paediatric clinics |
| hospital | boolean | – | Hospital ward instead of an outpatient clinic |
| max | integer | – | How many places to list (default 10) |
| place | string | yes | Town, address or 'lat,lon' in Poland |
| radius_km | number | – | Search radius in km (default 30, widened automatically if few results) |
| service | string | yes | What is needed, e.g. 'okulista', 'ortopeda', 'rezonans magnetyczny', 'endoprotezoplastyka stawu biodrowego' |
| sort | string | – | 'wait' (default) = shortest waiting time first, 'distance' = nearest first |
| urgent | boolean | – | Urgent case (referral marked 'pilne'); default false = stable case |
No output schema declared.
No examples provided.
How do I install the io.github.ContentWriterco/kolejki-nfz-mcp server?
io.github.ContentWriterco/kolejki-nfz-mcp is a hosted endpoint at https://kolejki.compabase.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · kolejki.compabase.com
claude mcp add --transport http contentwriterco-kolejki-nfz-mcp 'https://kolejki.compabase.com/mcp'
What is the io.github.ContentWriterco/kolejki-nfz-mcp server?
io.github.ContentWriterco/kolejki-nfz-mcp is listed in the public MCP registry as io.github.ContentWriterco/kolejki-nfz-mcp. NFZ waiting times in Poland: where a specialist, test or treatment is available soonest. This page covers its hosted endpoint (https://kolejki.compabase.com/mcp).
Is the io.github.ContentWriterco/kolejki-nfz-mcp server safe to use?
io.github.ContentWriterco/kolejki-nfz-mcp scores 69 out of 100 on VerifyMCP. 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.ContentWriterco/kolejki-nfz-mcp server expose?
io.github.ContentWriterco/kolejki-nfz-mcp exposes 3 tools: find_care, find_benefits, data_sources. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Does the io.github.ContentWriterco/kolejki-nfz-mcp server require authentication?
No. We connected to io.github.ContentWriterco/kolejki-nfz-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.ContentWriterco/kolejki-nfz-mcp server still maintained?
io.github.ContentWriterco/kolejki-nfz-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.