SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server
pl.szuruszuru/bookingszuruszuru.plstreamable-httpv1.1.0Scanned
Quote, check slots and book on-site upholstery, carpet and mattress cleaning in Pomorskie, Poland.
13 tools: 2 can delete or cancel things, 2 do something that can't be undone, 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 4
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server can do
The SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server is published by szuruszuru.pl, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (2 tools: reschedule_booking and cancel_booking), do things that cannot be undone, such as sending, paying or publishing (check_availability and resend_confirmation_code) and create or change data (6 tools: check_service_area, calculate_quote, prepare_booking, create_booking and 2 more). 3 tools only read.
4 tools can send data out of your system (check_availability, prepare_booking, resend_confirmation_code and 1 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 2Claude Code: deny
cancel_bookingPURPOSE: Cancels the verified customer's existing booking.No findings
Why it is in this group
- The name "cancel_booking" says "cancel": a word for removing or ending something.
- The description says "Irreversible".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it PURPOSE: Cancels the verified customer's existing booking. Irreversible. WHEN TO USE: Only after the customer explicitly confirmed they want to cancel this specific booking (reference and date read back to them). WHEN NOT TO USE: Not to change the date (use reschedule_booking), never on an unclear request. REQUIRED: booking_reference, customer_grant (or a signed-in customer). reason and idempotency_key optional. SIDE EFFECTS: cancels the booking and notifies the customer by SMS/e-mail. Repeating the same call returns the same result.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Anuluj rezerwację
reschedule_bookingPURPOSE: Moves the verified customer's existing booking to a new slot.No findings
Why it is in this group
- The name "reschedule_booking" says "reschedule": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it PURPOSE: Moves the verified customer's existing booking to a new slot. Price and services stay the same. WHEN TO USE: Only after check_availability(booking_reference) and after the customer explicitly confirmed the new date and time. WHEN NOT TO USE: Not for new bookings, not to change services or price. REQUIRED: booking_reference, slot_id (from check_availability with that booking_reference), customer_grant (or a signed-in customer). idempotency_key optional. SIDE EFFECTS: changes the booking and notifies the customer by SMS/e-mail. Repeating the same call returns the same result.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- title: Zmień termin
Can't be undone 2Claude Code: ask
check_availabilityPURPOSE: Returns real, currently free appointment slots for a quote_id (new booking) or for an existing booking_reference (rescheduling, needs customer_grant).Can send data out1 finding
Why it is in this group
- The input addresses people (input.wanted.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.wanted.to): what the tool writes goes there.
Findings
- Warn
The server marks "check_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The input addresses people (input.wanted.to): what it sends cannot be taken back.
Description, as the server wrote it PURPOSE: Returns real, currently free appointment slots for a quote_id (new booking) or for an existing booking_reference (rescheduling, needs customer_grant). WHEN TO USE: When the customer asks when we can come, after calculate_quote. wanted.type: asap (earliest), date (one day), range (from-to), preferred (a day + nearby days, sorted by preferred_time); optional part_of_day. If type is omitted it follows the fields given (date -> date, from/to -> range, nothing -> asap). WHEN NOT TO USE: Never to book - it reserves nothing and holds no slot. REQUIRED: quote_id (or booking_reference + customer_grant). Dates as YYYY-MM-DD, Polish time. SIDE EFFECTS: none (read-only; slot_id values are valid ~15 minutes). RESULT: slots found -> success=true, slots[]. None in the requested period -> success=false, error="no_availability", next_available (date or null) and alternative_slots[] - offer those. Past date -> error date_in_past; beyond the online booking horizon -> error date_out_of_range. Never invent a slot.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Sprawdź terminy
resend_confirmation_codePURPOSE: Re-sends the SMS code of a prepared booking.Can send data outNo findings
Why it is in this group
- The name "resend_confirmation_code" says "resend": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "resend_confirmation_code" says "resend": it sends or publishes something to other people.
Description, as the server wrote it PURPOSE: Re-sends the SMS code of a prepared booking. WHEN TO USE: Only when the customer says the SMS from prepare_booking did not arrive. WHEN NOT TO USE: Not after a wrong code (ask the customer to re-type it) and not to start a new booking. REQUIRED: confirmation_id. SIDE EFFECTS: sends one SMS (max 1 per minute, 3 per 30 minutes per phone; otherwise error rate_limited with retry_after).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Wyślij kod ponownie
Changes things 6Claude Code: ask
calculate_quotePURPOSE: Calculates the price of an order (unit prices, quantity discounts, add-ons, travel fee, minimum order) for a postal code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it PURPOSE: Calculates the price of an order (unit prices, quantity discounts, add-ons, travel fee, minimum order) for a postal code. Returns quote_id (valid 30 minutes). WHEN TO USE: Whenever the customer asks how much a cleaning costs and you know the service(s), quantity and postal code. Also the first step before check_availability. WHEN NOT TO USE: Not for checking dates and never as a booking - it reserves nothing. REQUIRED: postal_code; items[] with service (id from list_upholstery_services) and quantity. Add-ons optional (names from the catalog; close spellings are matched, unknown ones return error unsupported_addon with allowed_addons). If postal code, service or quantity is unknown, ask the customer - do not guess. SIDE EFFECTS: none for the customer (stores a 30-minute quote only). CONSTRAINTS: Report total_from exactly; never estimate or adjust prices. Area not served -> error unsupported_postcode. below_min_order=true -> ask the customer to add a service before booking.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Wycena
check_service_areaPURPOSE: Checks whether SzuruSzuru serves a Polish postal code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it PURPOSE: Checks whether SzuruSzuru serves a Polish postal code. WHEN TO USE: When the customer asks whether we come to their town/postal code. WHEN NOT TO USE: Not needed before calculate_quote (calculate_quote checks the area itself). Never use it to reserve anything. REQUIRED: postal_code (NN-NNN). SIDE EFFECTS: none (read-only). RESULT: served -> success=true, available=true, city. Not served -> success=false, error="unsupported_postcode", available=false - tell the customer we do not serve this code; do not continue to quote or booking.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Sprawdź obszar
create_bookingPURPOSE: Step 2 of 2 of booking.No findings
Why it is in this group
- The name "create_booking" says "create": a word for a change.
Description, as the server wrote it PURPOSE: Step 2 of 2 of booking. Creates the real, confirmed SzuruSzuru booking for a confirmation_id from prepare_booking, using the 6-digit SMS code the customer received. WHEN TO USE: Only after prepare_booking succeeded and the customer has typed the SMS code in the conversation. WHEN NOT TO USE: Never to check price or availability, never without a code from the customer, never with a guessed or example code. REQUIRED: confirmation_id, sms_code. idempotency_key optional. Missing data -> error missing_required_fields; nothing is created. SIDE EFFECTS: creates a booking (a technician is scheduled) and sends SMS/e-mail confirmation to the customer. Idempotent: repeating the call with the same confirmation_id and code returns the SAME booking - it never creates a second one. RESULT: success=true, booking_id, status, date, time (Polish time), price, currency. Give these to the customer. Wrong code -> error verification_failed with attempts_left.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Potwierdź rezerwację
prepare_bookingPURPOSE: Step 1 of 2 of booking.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.customer.phone): what the tool writes goes there.
Description, as the server wrote it PURPOSE: Step 1 of 2 of booking. Holds the chosen slot for 10 minutes and sends a 6-digit SMS code to the customer's Polish mobile. Returns confirmation_id and a summary to show verbatim. Does NOT create a booking. WHEN TO USE: Only after the customer explicitly said they want to book THIS slot, gave first and last name, street address with number and mobile phone, and accepted the terms. WHEN NOT TO USE: Not for price or date questions, not when the customer says "maybe" or only asks how much / when. Never guess or invent missing data - ask. REQUIRED: quote_id, slot_id (from check_availability), customer.name, customer.address, customer.phone, terms_accepted=true. Missing data -> error missing_required_fields with missing_fields[]. SIDE EFFECTS: one SMS to the phone + 10-minute slot hold. The identical call repeated returns the same confirmation_id, no new SMS. NEXT: ask the customer for the SMS code, then call create_booking.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Przygotuj rezerwację
start_phone_verificationPURPOSE: Sends an SMS code to a Polish mobile number to prove the customer owns it, before showing, rescheduling or cancelling their EXISTING bookings.Can send data outNo findings
Why it is in this group
- The name "start_phone_verification" says "start": a word for a change.
What it can reach
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it PURPOSE: Sends an SMS code to a Polish mobile number to prove the customer owns it, before showing, rescheduling or cancelling their EXISTING bookings. WHEN TO USE: When the customer asks about their existing booking(s) and no customer_grant is available yet. WHEN NOT TO USE: Not for a new booking (prepare_booking sends its own code). REQUIRED: phone. SIDE EFFECTS: sends one SMS (a repeated call within 60 s returns the same verification_id without a new SMS). The response is the same whether or not the number is known.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Weryfikacja numeru
verify_phone_codePURPOSE: Exchanges the SMS code from start_phone_verification for a customer_grant (valid 60 minutes) that gives access to this customer's own bookings.No findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it PURPOSE: Exchanges the SMS code from start_phone_verification for a customer_grant (valid 60 minutes) that gives access to this customer's own bookings. WHEN TO USE: Right after the customer types the code from start_phone_verification. WHEN NOT TO USE: Not for the booking code from prepare_booking (that one goes to create_booking). REQUIRED: verification_id, code. SIDE EFFECTS: none besides issuing the grant. Pass customer_grant to get_my_bookings, check_availability(booking_reference), reschedule_booking and cancel_booking.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- title: Potwierdź kod
Only reads 3Show 3 read-only tools
get_my_bookingsPURPOSE: Lists the verified customer's bookings from the last 90 days (or one booking by booking_reference): reference, services, date, time, price, status, can_reschedule, can_can…No findings
Why it is in this group
- The name "get_my_bookings" says "get": a word for reading.
Description, as the server wrote it PURPOSE: Lists the verified customer's bookings from the last 90 days (or one booking by booking_reference): reference, services, date, time, price, status, can_reschedule, can_cancel. WHEN TO USE: When the customer asks about their existing booking(s). WHEN NOT TO USE: Not for new bookings. Without customer_grant it returns error verification_required - then run start_phone_verification -> verify_phone_code. REQUIRED: customer_grant (or a signed-in customer). SIDE EFFECTS: none (read-only). Never shows other customers' data.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Moje rezerwacje
get_service_requirementsPURPOSE: Returns the details of ONE service: unit (piece / m2 / mattress side), allowed quantity, add-on names and prices, short description and FAQ.No findings
Why it is in this group
- The name "get_service_requirements" says "get": a word for reading.
Description, as the server wrote it PURPOSE: Returns the details of ONE service: unit (piece / m2 / mattress side), allowed quantity, add-on names and prices, short description and FAQ. WHEN TO USE: When the request is ambiguous (e.g. which corner sofa size, carpet area in m2, which add-ons exist for this service). WHEN NOT TO USE: Not for prices of an order (use calculate_quote) or availability. REQUIRED: service (id from list_upholstery_services). SIDE EFFECTS: none (read-only).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Wymagania usługi
list_upholstery_servicesPURPOSE: Lists SzuruSzuru services (mobile upholstery, corner sofa, armchair, carpet, rug and mattress cleaning at the customer's home, Pomeranian region, Poland) with service ids,…No findings
Why it is in this group
- The name "list_upholstery_services" says "list": a word for reading.
Description, as the server wrote it PURPOSE: Lists SzuruSzuru services (mobile upholstery, corner sofa, armchair, carpet, rug and mattress cleaning at the customer's home, Pomeranian region, Poland) with service ids, unit prices in PLN, units and add-on names. WHEN TO USE: To find the service id and exact add-on names before calculate_quote, or when the customer asks what is offered. WHEN NOT TO USE: Not for a price of a concrete order (use calculate_quote), not for coverage (check_service_area) or dates (check_availability). REQUIRED: nothing. SIDE EFFECTS: none (read-only). CONSTRAINTS: Prices come only from this catalog and calculate_quote - never estimate a price.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Lista usług SzuruSzuru
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (2 destructive, 2 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://agent.szuruszuru.pl/mcp: tools/list returned 13 tools to an anonymous client, including reschedule_booking (destructive), cancel_booking (destructive), check_availability (irreversible), resend_confirmation_code (irreversible), check_service_area (write) and 5 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The input addresses people (input.wanted.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:list_upholstery_servicesOnly readsinputSchema
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http booking https://agent.szuruszuru.pl/mcpclaude mcp add --transport http booking https://agent.szuruszuru.pl/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__booking__list_upholstery_services",
"mcp__booking__get_service_requirements",
"mcp__booking__get_my_bookings"
],
"ask": [
"mcp__booking__check_service_area",
"mcp__booking__calculate_quote",
"mcp__booking__check_availability",
"mcp__booking__prepare_booking",
"mcp__booking__resend_confirmation_code",
"mcp__booking__create_booking",
"mcp__booking__start_phone_verification",
"mcp__booking__verify_phone_code"
],
"deny": [
"mcp__booking__reschedule_booking",
"mcp__booking__cancel_booking"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as booking. Review it before you use it.
Capability tags behind 4 rules
- mcp__booking__check_availability outbound
- mcp__booking__prepare_booking outbound
- mcp__booking__resend_confirmation_code outbound
- mcp__booking__start_phone_verification outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/pl.szuruszuru/booking/verify?hash=851b4dd8dc7bf3635aeabefb46e3077ca88e602f16472371544c608adb9d651e" | jq -e '.changed == false'Pinned hash 851b4dd8dc7b, from Nov 19, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/pl.szuruszuru/booking/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/pl.szuruszuru/booking)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 10 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: reschedule_booking and cancel_booking.
Can the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: check_availability and resend_confirmation_code.
What tools does the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server have?
- 13 tools: 2 destructive, 2 irreversible, 6 write, 3 read. reschedule_booking, cancel_booking, check_availability, resend_confirmation_code, check_service_area, calculate_quote, prepare_booking, create_booking and 5 more.
Does the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_availability, prepare_booking, resend_confirmation_code and start_phone_verification.
Has the SzuruSzuru – rezerwacja czyszczenia tapicerki MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.