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.

BEEP.rent — car rental in Poland

REMOTE · MCP.BEEP.RENT

Search, price and book rental cars across Poland; the customer confirms on beep.rent.

Available components

+3 this week 66 Trust /100

Last scanned (5 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3577 tokens (~198/item across 18 items; 18 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “resolve_booking_link” rewrote its description, which is the text the model reads security
  • 2 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.

  • 31 Oct 26 +1
    • Tool coverage: 28% → 33% ▲ functional
    • “find_pickup_points” reworded the description of “city” cosmetic
    • “find_pickup_points” reworded the description of “near” cosmetic
    • “search_offers” reworded the description of “filters” cosmetic
    • “search_offers” reworded the description of “options” cosmetic
    • “search_offers” reworded the description of “pickup” cosmetic
  • 29 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 2781 → 3428 ▼ functional
    • Tool coverage: 21% → 28% ▲ functional
    • New tool “request_long_term_offer” functional
    • New tool “search_long_term_offers” functional
  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 61

    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 5 Nov 2026 · Probed https://mcp.beep.rent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.beep.rent CN=YR1,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 RSA 4096 SHA256-RSA 5c650837099ce6a2c4895dda3bce6940f3a
SANs: mcp.beep.rent
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 mcp.beep.rent. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
rent. present 51469, 56632 8, 8 Verified
beep.rent. 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=15768000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.beep.rent/mcp Verified 200
http (plaintext) http://mcp.beep.rent/mcp HTTPS enforced 301 https://mcp.beep.rent/mcp
MCP tools · 18 exposed · ~2,913 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
cancel_reservation ~174

Use when the user asks to cancel: after verify_reservation_management, with its management_id (and the reservation_number when the code was sent for the user's e-mail), or with the reservation_number when the user's BEEP.rent account is connected. First call without confirm: it returns the refund and a confirmation_token and cancels nothing. Show the refund, get the user's explicit yes, then call again with confirm=true and that token. Cancellation is irreversible. Example: {"management_id":"from_verify","confirm":true,"confirmation_token":"from_preview"}.

NameTypeReqDescription
confirmboolean–false previews; true executes the previewed operation.
confirmation_token–––
management_id––From verify_reservation_management.
market–––
reservation_number––The number of one of the user's own reservations.
NameTypeReqDescription
confirmation_token–––
consequences–––
content_language–––
continue_url–––
expires_at–––
links–––
messagesarray––
next_stepsarray––
policies–––
reason–––
refund–––
replayed–––
reservation_number–––
statusstring––

No examples provided.

confirm_reservation_code ~110

Use when the user gives you the 6-digit code they received for a new reservation. Never guess or invent a code. Returns the reservation status: the rental company may still have to accept it. Example: {"reservation_number":"AB12CD34","status_token":"from_reservation","code":"123456"}.

NameTypeReqDescription
codestringyesThe 6-digit code the user received.
market–––
reservation_numberstringyes–
status_tokenstringyes–
NameTypeReqDescription
capabilities–––
confirmation–––
content_language–––
continue_url–––
expires_at–––
has_recovery–––
links–––
messagesarray––
next_stepsarray––
partner_confirmation–––
partner_decision–––
payment–––
policies–––
reason–––
recovery_url–––
reservation–––
reservation_number–––
statusstring––

No examples provided.

create_checkout ~132

Use after get_offer when the user chose an offer: freezes the final price, deposit, options and policies and returns checkout_id and a beep.rent link (continue_url) where the user can finish. Resend every option you applied in get_offer. Does not book anything. Show the user the price, the deposit and the cancellation policy before calling this tool. Example: {"search_id":"from_search","offer_ref":"from_offer","options":{"damage_waiver":true}}.

NameTypeReqDescription
market–––
offer_refstringyes–
options–––
search_idstringyes–
NameTypeReqDescription
candidates–––
checkout_id–––
consents_required–––
content_language–––
continue_url–––
deposit–––
driver–––
expires_at–––
field–––
links–––
messagesarray––
next_stepsarray––
offer–––
optional_customer_fields–––
partner_confirmation–––
payment–––
policies–––
pricing–––
required_customer_fields–––
selected_options–––
statusstring––
trip–––

No examples provided.

create_reservation ~234

Use only after the user explicitly asked to book and, asked in one question of its own, accepted the terms and the privacy policy and answered about marketing messages (a yes to the booking is not a yes to the terms): creates the reservation from checkout_id with the driver's details. The booking is not confirmed until the user enters the code sent to them (confirm_reservation_code) or pays on beep.rent. Calling again with the same checkout returns the same reservation. Show the user the price, the deposit and the cancellation policy before calling this tool. Example: {"checkout_id":"from_checkout","customer":{"first_name":"Anna","last_name":"Nowak","email":"anna@example.com","phone":"+48500600700"},"consents":{"terms":true,"rental_terms":true,"marketing":false}}.

NameTypeReqDescription
accept_changesboolean–Set only after the user accepted the changed terms returned with status requires_review.
checkout_idstringyes–
comment–––
consentsobjectyes–
customerobjectyes–
invoice–––
market–––
NameTypeReqDescription
capabilities–––
changes–––
confirmation–––
content_language–––
continue_url–––
deposit–––
expires_at–––
links–––
messagesarray––
next_stepsarray––
partner_confirmation–––
partner_decision–––
payment–––
policies–––
pricing–––
reason–––
replayed–––
reservation–––
reservation_number–––
statusstring––
status_token–––

No examples provided.

find_pickup_points ~126

Use to find physical pickup desks near a city or location. Reads the shared public snapshot. Do not treat a pickup point as a guarantee of car availability. Examples: {"city":"krakow","radius_m":10000}; {"near":{"lat":50.06,"lng":19.94},"limit":5}.

NameTypeReqDescription
city––A city name. Required when near is omitted; do not supply both.
limitinteger––
market–––
near––Supply exactly one of near or city.
radius_minteger––
NameTypeReqDescription
candidates–––
categories–––
city_id–––
conditions–––
content_language–––
continue_url–––
currency–––
driver–––
expires_at–––
facets–––
field–––
links–––
messagesarray––
meta–––
name–––
next_stepsarray––
offer–––
offers–––
pagination–––
pickup–––
points–––
policies–––
return_location–––
search_id–––
statusstring––
valid_until–––

No examples provided.

get_city_prices ~77

Use for cached price examples before travel dates are chosen. These are dated examples, not live availability. Do not use for a binding quote. Examples: {"city":"Kraków"}; {"city":"wroclaw-krzyki","market":"en-pl"}.

NameTypeReqDescription
citystringyes–
market–––
NameTypeReqDescription
candidates–––
categories–––
city_id–––
conditions–––
content_language–––
continue_url–––
currency–––
driver–––
expires_at–––
facets–––
field–––
links–––
messagesarray––
meta–––
name–––
next_stepsarray––
offer–––
offers–––
pagination–––
pickup–––
points–––
policies–––
return_location–––
search_id–––
statusstring––
valid_until–––

No examples provided.

get_offer ~147

Use after search_offers to read current pricing, deposit, extras and rental policies. Supplied options are applied on top of the search selections; omitted options keep the search values. Options from earlier get_offer calls are not remembered: resend every option you changed. detail "full" adds every photo; "policies" keeps the policies in a concise response. Do not use to book or confirm a reservation. Example: {"search_id":"from_search","offer_ref":"from_offer"}.

NameTypeReqDescription
detailstring––
market–––
offer_refstringyes–
options–––
response_formatstring––
search_idstringyes–
NameTypeReqDescription
candidates–––
categories–––
city_id–––
conditions–––
content_language–––
continue_url–––
currency–––
driver–––
expires_at–––
facets–––
field–––
links–––
messagesarray––
meta–––
name–––
next_stepsarray––
offer–––
offers–––
pagination–––
pickup–––
points–––
policies–––
return_location–––
search_id–––
statusstring––
valid_until–––

No examples provided.

get_reservation_status ~163

Use to check whether a reservation is confirmed, awaits the user's code or payment, or awaits the rental company. Identify it with status_token from create_reservation, with the e-mail used for booking, with the management_id of the user's e-mail, or by its number alone when the user's BEEP.rent account is connected. Never say a reservation is confirmed unless this returns status confirmed. Examples: {"reservation_number":"AB12CD34","status_token":"from_reservation"}; {"reservation_number":"AB12CD34","email":"anna@example.com"}.

NameTypeReqDescription
email–––
management_id––From verify_reservation_management for the user's e-mail.
market–––
reservation_numberstringyes–
status_token–––
NameTypeReqDescription
capabilities–––
confirmation–––
content_language–––
continue_url–––
expires_at–––
has_recovery–––
links–––
messagesarray––
next_stepsarray––
partner_confirmation–––
partner_decision–––
payment–––
policies–––
reason–––
recovery_url–––
reservation–––
reservation_number–––
statusstring––

No examples provided.

list_my_reservations ~169

Use when the user asks about their own BEEP.rent bookings. Lists the reservations of the e-mail the user verified with start_reservation_management (pass its management_id) or of the BEEP.rent account they connected: upcoming ones with the next pickup first, or with include_past the last 365 days, newest first. Each has its number, status, dates, pickup place, car and total. Example: {"management_id": "from_verify", "limit": 5}.

NameTypeReqDescription
include_pastboolean–Also list rentals that ended or were cancelled in the last 365 days.
limitinteger–How many reservations to return.
management_id––From verify_reservation_management for the user's e-mail.
offsetinteger––
NameTypeReqDescription
content_language–––
continue_url–––
expires_at–––
links–––
messagesarray––
next_stepsarray––
pagination–––
policies–––
reservations–––
statusstring––

No examples provided.

quote_extension ~149

Use when the user wants to return the car later, after verify_reservation_management, with its management_id (and the reservation_number when the code was sent for the user's e-mail), or with the reservation_number when the user's BEEP.rent account is connected: prices the extra days. Only a rental in progress can be extended. Changes nothing. Example: {"management_id":"from_verify","new_return_at":"2026-12-10T10:00:00+01:00"}.

NameTypeReqDescription
management_id––From verify_reservation_management.
market–––
new_return_atstringyes–
reservation_number––The number of one of the user's own reservations.
NameTypeReqDescription
content_language–––
continue_url–––
decision–––
expires_at–––
extendableboolean––
links–––
messagesarray––
next_stepsarray––
policies–––
quote–––
reason–––
reservation_number–––
statusstring––

No examples provided.

request_confirmation_code ~88

Use when the user did not receive the 6-digit code for a new reservation or it expired. Sends a new code to the contact given at booking; do not call it unprompted. Example: {"reservation_number":"AB12CD34","status_token":"from_reservation"}.

NameTypeReqDescription
market–––
reservation_numberstringyes–
status_tokenstringyes–
NameTypeReqDescription
capabilities–––
confirmation–––
content_language–––
continue_url–––
expires_at–––
has_recovery–––
links–––
messagesarray––
next_stepsarray––
partner_confirmation–––
partner_decision–––
payment–––
policies–––
reason–––
recovery_url–––
reservation–––
reservation_number–––
statusstring––

No examples provided.

request_extension ~167

Use after quote_extension when the user asked to extend. First call without confirm previews the request and returns confirmation_token; after the user's explicit yes call again with confirm=true, the token and the same new_return_at. The rental company decides; decision says how the user hears back. Example: {"management_id":"from_verify","new_return_at":"2026-12-10T10:00:00+01:00","confirm":true,"confirmation_token":"from_preview"}.

NameTypeReqDescription
confirmboolean–false previews; true executes the previewed operation.
confirmation_token–––
management_id––From verify_reservation_management.
market–––
new_return_atstringyes–
reservation_number––The number of one of the user's own reservations.
NameTypeReqDescription
confirmation_token–––
content_language–––
continue_url–––
decision–––
expires_at–––
extendableboolean––
links–––
messagesarray––
next_stepsarray––
policies–––
quote–––
reason–––
replayed–––
request_id–––
reservation_number–––
statusstring––

No examples provided.

request_long_term_offer ~240

Use when the person wants one long-term package. By default returns use_web_form and continue_url without customer or consents: give the person the form and do not collect contact details. If direct inquiries are enabled, ask for privacy policy and marketing consent before submitting contact details. The office then contacts the person; this is not a booking. Example: {"car_id":"<car_id>","rent_length":"year1","mileage_limit":36000,"customer_type":"business","customer":{"first_name":"Anna","last_name":"Nowak","email":"anna@example.com","phone":"+48500600700"},"consents":{"privacy_policy":true,"marketing":false}}.

NameTypeReqDescription
car_idstringyesAn offer's car_id from search_long_term_offers.
consents––Required only for direct submission after asking the person.
customer––Required only for direct submission, never for a web handoff.
customer_typestring––
market–––
mileage_limit––A package's mileage_limit from the offer; null when it is individually priced.
rent_lengthstringyes–
NameTypeReqDescription
content_language–––
continue_url–––
expires_at–––
inquiry–––
links–––
messagesarray––
next_stepsarray––
policies–––
replayed–––
statusstring––

No examples provided.

resolve_booking_link ~143

Use when the user pastes a beep.rent link to one offer (from an e-mail, a campaign or a short beep.rent/r/ link). Returns search_id and offer_ref for get_offer, priced with the options the link advertised. A beep.rent offer page copied from the browser opens only there: the call then names its car to search for. Example: {"url": "https://beep.rent/pl-pl/wynajem-samochodu/?offer_car=...&pickup_parking=...&pickup_at=..."}.

NameTypeReqDescription
urlstringyesThe beep.rent link to one offer exactly as the user received it.
NameTypeReqDescription
car_title–––
content_language–––
continue_url–––
driver–––
expires_at–––
links–––
messagesarray––
next_stepsarray––
offer_ref–––
policies–––
search_id–––
search_state–––
statusstring––

No examples provided.

search_long_term_offers ~278

Use for a car rented for months or years (1 month renewed monthly to 3 years): monthly prices in PLN per mileage package, excluding VAT for businesses or including VAT for private customers, with the inquiry link of each package. Not for trips with dates: use search_offers. Filters take facets values; facets list them. Examples: {"rent_length":"year2","customer_type":"individual"}; {"brand":"Audi","monthly_cost_max":5000}.

NameTypeReqDescription
body––A value or label from facets.body.
brand––A brand from facets.brand, e.g. Audi.
customer_typestring–business: prices excluding VAT; individual: including VAT.
fuel––A value or label from facets.fuel.
limitinteger––
market–––
monthly_cost_max––PLN per month, in the customer_type's unit (gross for individual).
monthly_cost_min––PLN per month, in the customer_type's unit (gross for individual).
offsetinteger––
ordering–––
production_year_max–––
production_year_min–––
rent_lengthstring–flex = 1 month, renewed monthly; month3, month6; year1, year2, year3.
transmission–––
NameTypeReqDescription
content_language–––
continue_url–––
customer_type–––
expires_at–––
facets–––
links–––
messagesarray––
next_stepsarray––
offers–––
page_url–––
pagination–––
policies–––
price_basis–––
rent_length–––
statusstring––

No examples provided.

search_offers ~291

Use when looking for available cars and full prices in Poland. Supply the whole trip when changing criteria; omitted options reset. Filters and sort are not remembered: repeat them on every page. Do not use for an existing reservation. Examples: {"pickup":{"query":"Kraków"},"pickup_at":"2026-12-01T10:00:00+01:00","return_at":"2026-12-08T10:00:00+01:00","sort":"price"}; {"search_id":"from_previous_result","offset":8,"sort":"price"}.

NameTypeReqDescription
card_typestring––
driver_ageinteger––
filtersobject–A JSON object of filters. Omit it or use {} for no filters; never use [].
license_tenure_monthsinteger––
limitinteger––
market–––
offsetinteger––
optionsobject–A JSON object of rental options. Omit it or use {} for defaults; never use [].
pickup––For a new trip supply pickup, pickup_at and return_at together. For paging supply search_id instead.
pickup_at–––
response_formatstring––
return_at–––
return_location–––
search_id–––
sortstring––
NameTypeReqDescription
candidates–––
categories–––
city_id–––
conditions–––
content_language–––
continue_url–––
currency–––
driver–––
expires_at–––
facets–––
field–––
links–––
messagesarray––
meta–––
name–––
next_stepsarray––
offer–––
offers–––
pagination–––
pickup–––
points–––
policies–––
return_location–––
search_id–––
statusstring––
valid_until–––

No examples provided.

start_reservation_management ~108

Use when the user wants to see, cancel or extend their reservations: e-mails a 6-digit code to the booking's e-mail address and returns management_id. With the reservation number the code unlocks that reservation; without it, every reservation of that e-mail. Examples: {"reservation_number":"AB12CD34","email":"anna@example.com"}; {"email":"anna@example.com"}.

NameTypeReqDescription
emailstringyes–
market–––
reservation_number–––
NameTypeReqDescription
code_expires_in_minutes–––
content_language–––
continue_url–––
expires_at–––
links–––
management_id–––
messagesarray––
next_stepsarray––
policies–––
statusstring––

No examples provided.

verify_reservation_management ~117

Use with the 6-digit code from the management e-mail: unlocks the reservation's summary and its cancellation and extension options or, for a code sent for an e-mail alone, that e-mail's reservations, for this conversation (2 hours). Go on with the management_id it returns. Never guess a code. Example: {"management_id":"from_start","code":"123456"}.

NameTypeReqDescription
codestringyesThe 6-digit code the user received.
management_idstringyes–
market–––
NameTypeReqDescription
capabilities–––
content_language–––
continue_url–––
expires_at–––
links–––
management_id–––
messagesarray––
next_stepsarray––
policies–––
reservation–––
reservations–––
statusstring––

No examples provided.

Install

How do I install the BEEP.rent — car rental in Poland MCP server?

BEEP.rent — car rental in Poland is a hosted endpoint at https://mcp.beep.rent/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 · mcp.beep.rent

# add to Claude Code
claude mcp add --transport http rent-beep-car-rental 'https://mcp.beep.rent/mcp'
Common questions

What is the BEEP.rent — car rental in Poland MCP server?

BEEP.rent — car rental in Poland is an MCP server listed in the public MCP registry as rent.beep/car-rental. Search, price and book rental cars across Poland; the customer confirms on beep.rent. This page covers its hosted endpoint (https://mcp.beep.rent/mcp).

Is the BEEP.rent — car rental in Poland MCP server safe to use?

BEEP.rent — car rental in Poland 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 BEEP.rent — car rental in Poland MCP server expose?

BEEP.rent — car rental in Poland exposes 18 tools: search_offers, get_offer, get_city_prices, find_pickup_points, resolve_booking_link, and 13 more. Their descriptions and schemas cost roughly 2,913 tokens of context every time the server is loaded.

Does the BEEP.rent — car rental in Poland MCP server require authentication?

No. We connected to BEEP.rent — car rental in Poland without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BEEP.rent — car rental in Poland MCP server still maintained?

BEEP.rent — car rental in Poland is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.