Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Szülni Jó – services and appointments

REMOTE · SZULNIJO.HU

Public services and available appointments at Szülni Jó, Hungary. Online or telephone booking links.

Available components

+4 this week 66 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 406 tokens (~203/item across 2 items; 2 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +11
    • Transport: fail → pass ▲ security
  • 16 Nov 26 −10
    • Transport: pass → fail ▼ security
    • Server version: 1.2.0 → 1.3.0 functional
  • 15 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 62

    First indexed and scored.

Diagnostics

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 · Probed https://szulnijo.hu/wp-json/szulnijo-mcp/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=webdisk.szulnijo.hu CN=YR1,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 RSA 2048 SHA256-RSA 65b2538804912bae33201bc3d9d6061edee
SANs: autoconfig.szulnijo.hu, autodiscover.szulnijo.hu, cpanel.szulnijo.hu, cpcalendars.szulnijo.hu, cpcontacts.szulnijo.hu, mail.szulnijo.hu, szulnijo.hu, webdisk.szulnijo.hu, webmail.szulnijo.hu, www.szulnijo.hu
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of szulnijo.hu. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
hu. DS published 46162 8 Verified
szulnijo.hu. No DS 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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://szulnijo.hu/wp-json/szulnijo-mcp/v1/mcp Verified 200
http (plaintext) http://szulnijo.hu/wp-json/szulnijo-mcp/v1/mcp Inconclusive 405
MCP tools · 2 exposed · ~294 tokens

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 →

Tool Tokens
get_available_appointments ~192

Az adott szolgáltatás szabad, jövőbeli időpontjai. Előbb kérd le a service_id értéket. online módnál termékoldali linket, phone módnál telefonszámot és Csak telefonon foglalható jelölést mutass. A lekérdezés nem foglal és nem tart fenn időpontot.

NameTypeReqDescription
date_fromstring–YYYY-MM-DD, legkorábban ma (Europe/Budapest). Alapérték: ma.
date_tostring–YYYY-MM-DD, legfeljebb ma +119 nap. Alapérték: a kezdőnaptól 30 napos időszak.
limitinteger––
offsetinteger––
service_idstringyesA list_booking_services által visszaadott azonosító.

No output schema declared.

No examples provided.

list_booking_services ~102

Online foglalható WooCommerce-szolgáltatások és WooCommerce-termék nélküli, csak telefonon foglalható szolgáltatások. Név, foglalási mód, online ár és link vagy telefonszám. Ezzel keresd meg a service_id értéket; ne találj ki azonosítót.

NameTypeReqDescription
querystring–Opcionális keresés a szolgáltatás vagy szakember nevében.

No output schema declared.

No examples provided.

Install

How do I install the Szülni Jó – services and appointments MCP server?

Szülni Jó – services and appointments is a hosted endpoint at https://szulnijo.hu/wp-json/szulnijo-mcp/v1/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 · szulnijo.hu

# add to Claude Code
claude mcp add --transport http hu-szulnijo-booking 'https://szulnijo.hu/wp-json/szulnijo-mcp/v1/mcp'
Common questions

What is the Szülni Jó – services and appointments MCP server?

Szülni Jó – services and appointments is an MCP server listed in the public MCP registry as hu.szulnijo/booking. Public services and available appointments at Szülni Jó, Hungary. Online or telephone booking links. This page covers its hosted endpoint (https://szulnijo.hu/wp-json/szulnijo-mcp/v1/mcp).

Is the Szülni Jó – services and appointments MCP server safe to use?

Szülni Jó – services and appointments scores 66 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 Szülni Jó – services and appointments MCP server expose?

Szülni Jó – services and appointments exposes 2 tools: list_booking_services, get_available_appointments. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.

Does the Szülni Jó – services and appointments MCP server require authentication?

No. We connected to Szülni Jó – services and appointments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Szülni Jó – services and appointments MCP server still maintained?

Szülni Jó – services and appointments 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 did VerifyMCP test on the Szülni Jó – services and appointments MCP server?

VerifyMCP ran 12 checks on Szülni Jó – services and appointments, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Szülni Jó – services and appointments: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.