Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
BEEP.rent — car rental in Poland is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Search, price and book rental cars across Poland; the customer confirms on beep.rent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http beep-rent-car-rental-in-poland-mcp https://mcp.beep.rent/mcp
# 2 — ask your agent for something these tools do
# search_offers, get_offer, get_city_prices and 13 more
BEEP.rent — car rental in Poland costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BEAll 2 servers
beep2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http beep-rent-car-rental-in-poland-mcp https://mcp.beep.rent/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pickup | no | — | |
| return_location | no | — | |
| pickup_at | no | — | |
| return_at | no | — | |
| driver_age | integer | no | — |
| license_tenure_months | integer | no | — |
| card_type | string | no | — |
| options | object | no | — |
| filters | object | no | — |
| sort | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
| search_id | no | — | |
| market | no | — | |
| response_format | string | no | — |
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 reser
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_id | string | yes | — |
| offer_ref | string | yes | — |
| options | no | — | |
| detail | string | no | — |
| market | no | — | |
| response_format | string | no | — |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | — |
| market | no | — |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| near | no | — | |
| city | no | — | |
| radius_m | integer | no | — |
| limit | integer | no | — |
| market | no | — |
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. Example: {"url": "https://beep.rent/pl-pl/wynajem-samochodu/?offer_car=...&pickup_parking=...&pickup_at=..."}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The beep.rent link to one offer exactly as the user received it. |
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"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_id | string | yes | — |
| offer_ref | string | yes | — |
| options | no | — | |
| market | no | — |
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 bee
| Parameter | Type | Required | Notes |
|---|---|---|---|
| checkout_id | string | yes | — |
| customer | object | yes | — |
| consents | object | yes | — |
| invoice | no | — | |
| comment | no | — | |
| accept_changes | boolean | no | Set only after the user accepted the changed terms returned with status requires_review. |
| market | no | — |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_number | string | yes | — |
| status_token | string | yes | — |
| market | no | — |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_number | string | yes | — |
| status_token | string | yes | — |
| market | no | — | |
| code | string | yes | The 6-digit code the user received. |
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. Exampl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_number | string | yes | — |
| status_token | no | — | |
| no | — | ||
| management_id | no | From verify_reservation_management for the user's e-mail. | |
| market | no | — |
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| management_id | no | From verify_reservation_management for the user's e-mail. | |
| limit | integer | no | How many reservations to return. |
| offset | integer | no | — |
| include_past | boolean | no | Also list rentals that ended or were cancelled in the last 365 days. |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_number | no | — | |
| string | yes | — | |
| market | no | — |
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"}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| management_id | string | yes | — |
| market | no | — | |
| code | string | yes | The 6-digit code the user received. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| management_id | no | From verify_reservation_management. | |
| reservation_number | no | The number of one of the user's own reservations. | |
| market | no | — | |
| confirm | boolean | no | false previews; true executes the previewed operation. |
| confirmation_token | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| management_id | no | From verify_reservation_management. | |
| reservation_number | no | The number of one of the user's own reservations. | |
| market | no | — | |
| new_return_at | string | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| management_id | no | From verify_reservation_management. | |
| reservation_number | no | The number of one of the user's own reservations. | |
| market | no | — | |
| confirm | boolean | no | false previews; true executes the previewed operation. |
| confirmation_token | no | — | |
| new_return_at | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BEEP.rent — car rental in Poland or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest6860ee694e6cbe515b059108dd21cc103ddd394ec1a1f75a5dbd736e34b4d0ed
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_offers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_offer | no tags | |
| get_city_prices | no tags | |
| find_pickup_points | no tags | |
| resolve_booking_link | no tags | |
| create_checkout | state-write | state-write: declares readOnlyHint: false |
| create_reservation | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| request_confirmation_code | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| confirm_reservation_code | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_reservation_status | no tags | |
| list_my_reservations | no tags | |
| start_reservation_management | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| verify_reservation_management | state-write | state-write: declares readOnlyHint: false |
| cancel_reservation | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| quote_extension | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| request_extension | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest6860ee694e6cbe51
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BEEP.rent — car rental in Poland can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.