Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Stayport 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.
What it does
Hostex PMS via MCP: properties, reservations, availability, messages, reviews, and webhooks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user stayport-mcp '--' npx -y @reneturcios/stayport mcp
# 2 — ask your agent for something these tools do
# hostex_list_properties, hostex_list_room_types, hostex_list_reservations and 20 more
Stayport costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Stayport as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user stayport-mcp '--' npx -y @reneturcios/stayport mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
23 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List properties from your Hostex account. Returns property details including ID, title, address, channels, and location coordinates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | number | no | Number of records to skip, for paging. |
| limit | number | no | Maximum number of properties to return. |
| id | number | no | Property id filter; return only the property with this id. |
List room types from your Hostex account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | number | no | Number of records to skip, for paging. |
| limit | number | no | Maximum number of room types to return. |
List and search reservations with filters like status, dates, property ID, etc.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_code | string | no | Reservation code filter. |
| property_id | number | no | Property id filter. |
| status | string | no | Reservation status filter: wait_accept, wait_pay, accepted, cancelled, denied, or timeout. |
| start_check_in_date | string | no | Earliest check-in date to include, YYYY-MM-DD. |
| end_check_in_date | string | no | Latest check-in date to include, YYYY-MM-DD. |
| start_check_out_date | string | no | Earliest check-out date to include, YYYY-MM-DD. |
| end_check_out_date | string | no | Latest check-out date to include, YYYY-MM-DD. |
| order_by | string | no | Sort field for the results. |
| offset | number | no | Number of records to skip, for paging. |
| limit | number | no | Maximum number of reservations to return. |
Create a direct booking reservation in Hostex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property_id | string | yes | Property id to book. |
| custom_channel_id | number | yes | Custom channel id for the direct booking. |
| check_in_date | string | yes | Check-in date, YYYY-MM-DD. |
| check_out_date | string | yes | Check-out date, YYYY-MM-DD. |
| guest_name | string | yes | Guest name. |
| currency | string | yes | Currency code for the amounts. |
| rate_amount | number | yes | Booking rate amount. |
| commission_amount | number | yes | Commission amount. |
| received_amount | number | yes | Amount received. |
| income_method_id | number | yes | Income method id. |
| number_of_guests | number | no | Number of guests. |
| string | no | Guest email address. | |
| mobile | string | no | Guest mobile number. |
| remarks | string | no | Remarks recorded with the reservation. |
Cancel a direct booking reservation (channel bookings not supported).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_code | string | yes | Reservation code of the direct booking to cancel. |
Update the lock code for a stay.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stay_code | string | yes | Stay code to update the lock code for. |
| lock_code | string | yes | New lock code. |
Get custom fields for a stay.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stay_code | string | yes | Stay code to get custom fields for. |
Update custom fields for a stay. Custom fields can be used in automated messages using {{cf.field_name}} syntax.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stay_code | string | yes | Stay code to update custom fields for. |
| custom_fields | object | yes | Custom fields object, keyed by field name. |
Query property availability for date ranges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property_ids | string | yes | Property ids to query, comma-separated. |
| start_date | string | yes | Start of the date range, YYYY-MM-DD. |
| end_date | string | yes | End of the date range, YYYY-MM-DD. |
Update property availability status for specific dates or date ranges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property_ids | array | yes | Property ids to update. |
| start_date | string | no | Start of the date range to update, YYYY-MM-DD. |
| end_date | string | no | End of the date range to update, YYYY-MM-DD. |
| dates | array | no | Specific dates to update, as an array. |
| available | boolean | yes | Whether the properties are available on the given dates. |
List guest conversations and inquiries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | number | no | Number of records to skip, for paging. |
| limit | number | no | Maximum number of conversations to return. |
Get conversation details including all messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_id | string | yes | Conversation id to fetch. |
Send a text or image message to a guest.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_id | string | yes | Conversation id to send the message in. |
| message | string | no | Text message to send. |
| jpeg_base64 | string | no | Image to send, as a base64-encoded JPEG. |
Query reviews with filters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_code | string | no | Reservation code filter. |
| property_id | number | no | Property id filter. |
| review_status | string | no | Review status filter. |
| start_check_out_date | string | no | Earliest check-out date to include, YYYY-MM-DD. |
| end_check_out_date | string | no | Latest check-out date to include, YYYY-MM-DD. |
| offset | number | no | Number of records to skip, for paging. |
| limit | number | no | Maximum number of reviews to return. |
Create a review or reply for a reservation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_code | string | yes | Reservation code the review applies to. |
| host_review_score | number | no | Host review score for the guest. |
| host_review_content | string | no | Host review text. |
| host_reply_content | string | no | Host reply text to an existing review. |
Post a comprehensive guest review with category ratings (requires login via email/password config). This posts reviews as they appear on the Hostex web app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_order_code | string | yes | Reservation order code the review applies to. |
| content | string | yes | Review text. |
| recommend | string | yes | Whether the host recommends the guest: 0 or 1. |
| overall_rating | string | yes | Overall rating, 1 to 5. |
| cleanliness | string | yes | Cleanliness rating, 1 to 5. |
| cleanliness_content | string | no | Comment on the cleanliness rating. |
| respect_of_house_rules | string | yes | Respect-of-house-rules rating, 1 to 5. |
| respect_house_rules_content | string | no | Comment on the house-rules rating. |
| communication | string | yes | Communication rating, 1 to 5. |
| communication_content | string | no | Comment on the communication rating. |
List configured webhooks.
No parameter schema on file.
Create a new webhook.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Webhook endpoint URL. |
Delete a webhook (only manageable ones).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| webhook_id | number | yes | Webhook id to delete. |
Get calendar information for multiple listings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | Start of the calendar range, YYYY-MM-DD. |
| end_date | string | yes | End of the calendar range, YYYY-MM-DD. |
| listings | array | yes | Listing ids to get calendar information for. |
Update listing prices for channel listings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel_type | string | yes | Channel type of the listing. |
| listing_id | string | yes | Listing id to update prices for. |
| prices | array | yes | Price entries to apply, as an array. |
Get custom channels from Custom Options Page.
No parameter schema on file.
Get income methods from Custom Options Page.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Stayport or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| hostex_list_properties | no tags | |
| hostex_list_room_types | no tags | |
| hostex_list_reservations | no tags | |
| hostex_create_reservation | no tags | |
| hostex_cancel_reservation | no tags | |
| hostex_update_lock_code | no tags | |
| hostex_get_custom_fields | no tags | |
| hostex_update_custom_fields | no tags | |
| hostex_list_availabilities | no tags | |
| hostex_update_availabilities | no tags | |
| hostex_list_conversations | no tags | |
| hostex_get_conversation | no tags | |
| hostex_send_message | external-sink | external-sink: keyword "send_message" |
| hostex_list_reviews | no tags | |
| hostex_create_review | no tags | |
| hostex_post_guest_review | no tags | |
| hostex_list_webhooks | no tags | |
| hostex_create_webhook | external-sink | external-sink: keyword "webhook" |
| hostex_delete_webhook | external-sink | external-sink: keyword "webhook", parameter "webhook" |
| hostex_get_listing_calendar | no tags | |
| hostex_update_listing_prices | no tags | |
| hostex_list_custom_channels | no tags | |
| hostex_list_income_methods | no tags |
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish Stayport can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.