Rudko — vertebrologist (Chernivtsi, Ukraine)
REMOTE · RUDKO.SITE · SCANNED SEP 24
Book a Ukrainian-speaking vertebrologist in Chernivtsi, Ukraine: find slots and book for the user.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 687 tokens (~98/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Rudko — vertebrologist (Chernivtsi, Ukraine) MCP server?
Rudko — vertebrologist (Chernivtsi, Ukraine) is a hosted endpoint at https://rudko.site/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 · rudko.site
claude mcp add --transport http site-rudko-vertebrolog 'https://rudko.site/mcp'
{
"mcpServers": {
"site-rudko-vertebrolog": {
"url": "https://rudko.site/mcp"
}
}
} {
"servers": {
"site-rudko-vertebrolog": {
"type": "http",
"url": "https://rudko.site/mcp"
}
}
} [mcp_servers.site-rudko-vertebrolog] url = "https://rudko.site/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"site-rudko-vertebrolog": {
"type": "remote",
"url": "https://rudko.site/mcp",
"enabled": true
}
}
} openclaw mcp add site-rudko-vertebrolog --url 'https://rudko.site/mcp' --transport streamable-http
mcp_servers:
site-rudko-vertebrolog:
url: "https://rudko.site/mcp" {
"McpServers": {
"site-rudko-vertebrolog": {
"Transport": "http",
"Url": "https://rudko.site/mcp"
}
}
} assistant mcp add site-rudko-vertebrolog -t streamable-http -u 'https://rudko.site/mcp'
{
"mcpServers": {
"site-rudko-vertebrolog": {
"type": "http",
"url": "https://rudko.site/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Sept 26 0
- Authorization: fail → unverified ▼ security
- Tool “cancel” no longer declares itself destructive security
- Server version: 0.1.0 → 0.1.2 functional
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 Sept 2026 · Probed https://rudko.site/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rudko.site | CN=YE2,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 57e934de274d271c6842671ea46828772c5 |
| SANs: rudko.site, www.rudko.site | ||||||
| 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 rudko.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| rudko.site. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-a5e645701e504280bd0dadf165e3e323' 'unsafe-inline' https://telegram.org; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-src https://oauth.telegram.org https://telegram.org; frame-ancestors 'self'; base-uri 'self'; object-src 'none'; form-action 'self' https://oauth.telegram.org |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rudko.site/mcp | Verified | 200 | |
| http (plaintext) | http://rudko.site/mcp | HTTPS enforced | 301 | https://rudko.site/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 →
book ~77
REAL action (not a simulation): creates a real appointment with the vertebrologist on the user's behalf. Requires the user's CONSENT — authorization via Telegram (OAuth, scope booking:write). date (YYYY-MM-DD), time (HH:MM). One appointment per day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| time | string | yes | – |
No output schema declared.
No examples provided.
cancel ~126
REAL action: cancels the user's appointment by booking_id (from list_current_bookings) IMMEDIATELY — no confirmation step. If the user said cancel, cancel; do NOT re-ask (repeated confirmations frustrate users — act decisively). On success returns cancelled=true with the booking_id; on failure returns ok=false with a reason (not_found / bad_id). Consent is a one-time Telegram OAuth (scope booking:write), already done — never re-prompt per action. To change the time instead, prefer reschedule.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | – |
No output schema declared.
No examples provided.
get_availability ~58
Free appointment slots for the vertebrologist (Chernivtsi). Optional date (YYYY-MM-DD): without it — all nearest available days. Read-only (does not book).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD (optional) |
No output schema declared.
No examples provided.
get_doctor_info ~40
About the vertebrologist: specialty, what he treats, address, slot length, rules (one appointment per day), and how to book.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_current_bookings ~62
The user's current/upcoming appointments (booking_id, date, time, status), nearest first. Cancelled ones are ALSO shown — tell them apart by the status field ('booked' | 'cancelled'). Needed to reschedule/cancel. Requires authorization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_past_bookings ~69
The user's past appointments (booking_id, date, time, status), most recent first. limit (default 20) and offset for pagination. Cancelled ones are ALSO shown — by the status field. Requires authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
reschedule ~155
REAL action: moves the user's appointment to another free slot the SAME day, ATOMICALLY — if the target slot was just taken, the user KEEPS their current slot (never loses the held slot; that atomic guarantee is the whole point of same-day move). For a DIFFERENT day, just call book instead (a fresh booking; cross-day needs no atomic hold). No confirmation — act on request. Consent is a one-time Telegram OAuth (scope booking:write), already done — never re-prompt per action. date (YYYY-MM-DD), from (HH:MM current), to (HH:MM new).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
What is the Rudko — vertebrologist (Chernivtsi, Ukraine) MCP server?
Rudko — vertebrologist (Chernivtsi, Ukraine) is an MCP server listed in the public MCP registry as site.rudko/vertebrolog. Book a Ukrainian-speaking vertebrologist in Chernivtsi, Ukraine: find slots and book for the user. This page covers its hosted endpoint (https://rudko.site/mcp).
Is the Rudko — vertebrologist (Chernivtsi, Ukraine) MCP server safe to use?
Rudko — vertebrologist (Chernivtsi, Ukraine) scores 78 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 Rudko — vertebrologist (Chernivtsi, Ukraine) MCP server expose?
Rudko — vertebrologist (Chernivtsi, Ukraine) exposes 7 tools: get_availability, get_doctor_info, list_current_bookings, list_past_bookings, book, and 2 more. Their descriptions and schemas cost roughly 587 tokens of context every time the server is loaded.
Does the Rudko — vertebrologist (Chernivtsi, Ukraine) MCP server require authentication?
No. We connected to Rudko — vertebrologist (Chernivtsi, Ukraine) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rudko — vertebrologist (Chernivtsi, Ukraine) MCP server still maintained?
Rudko — vertebrologist (Chernivtsi, Ukraine) is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.