hostaway-kit
NPM · HOSTAWAY-KIT · SCANNED SEP 24
Read-only Hostaway MCP: listings, calendar, inbox, reports. Fixtures, no key. By STYLABS.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 815 tokens (~74/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 30% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the hostaway-kit MCP server?
hostaway-kit runs locally as an npm package, launched with npx -y hostaway-kit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · hostaway-kit
claude mcp add stylabs-hostaway-kit -- npx -y hostaway-kit
{
"mcpServers": {
"stylabs-hostaway-kit": {
"command": "npx",
"args": [
"-y",
"hostaway-kit"
]
}
}
} {
"servers": {
"stylabs-hostaway-kit": {
"command": "npx",
"args": [
"-y",
"hostaway-kit"
]
}
}
} codex mcp add stylabs-hostaway-kit -- npx -y hostaway-kit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stylabs-hostaway-kit": {
"type": "local",
"command": [
"npx",
"-y",
"hostaway-kit"
],
"enabled": true
}
}
} openclaw mcp add stylabs-hostaway-kit --command npx --arg -y --arg hostaway-kit
mcp_servers:
stylabs-hostaway-kit:
command: "npx"
args: ["-y", "hostaway-kit"] {
"McpServers": {
"stylabs-hostaway-kit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"hostaway-kit"
]
}
}
} assistant mcp add stylabs-hostaway-kit -t stdio -c npx -a -y hostaway-kit
{
"mcpServers": {
"stylabs-hostaway-kit": {
"command": "npx",
"args": [
"-y",
"hostaway-kit"
]
}
}
} 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.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 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.
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 24 Sept 2026 · Analysed npm/hostaway-kit@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
draft_reply ~88
Suggested reply grounded in THAT listing's fields, house rules, amenityId values, and calendar prices. Never invent rates (use calendar or say unknown). Never include wifi or door codes. Never POSTs a message — send is always false and there is no send endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | integer | yes | – |
| question | string | – | Optional focus question; defaults to the latest incoming message |
No output schema declared.
No examples provided.
get_calendar ~95
Retrieve listing calendar via GET /v1/listings/{id}/calendar?includeResources=1. Each day has status (available/blocked/reserved/pending), isAvailable, and price (null means unknown — do not invent a rate). Nested reservations are denylist-stripped.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | Y-m-d |
| listingId | integer | yes | – |
| startDate | string | yes | Y-m-d |
No output schema declared.
No examples provided.
get_listing ~68
Retrieve one listing via GET /v1/listings/{id}?includeResources=1. House rules, check-in hours (0–23), amenityId values, and photos are included. wifiPassword, door codes, and invoicing contacts are stripped.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | integer | yes | – |
No output schema declared.
No examples provided.
inbox_triage ~71
Unanswered / SLA view Hostaway's inbox does not compute. A thread is unanswered when the latest message is incoming (or hasUnreadMessages with no later host reply). Default SLA is 2 hours. Does not send replies.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | integer | – | – |
| slaHours | number | – | – |
No output schema declared.
No examples provided.
list_conversations ~50
List inbox threads via GET /v1/conversations?includeResources=1. Nested Reservation objects are denylist-stripped.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | integer | – | – |
| reservationId | integer | – | – |
No output schema declared.
No examples provided.
list_listings ~161
List Hostaway listings. Defaults to GET /v1/listings?specialStatus[]=active. Optional availabilityDateStart/End + availabilityGuestNumber filter the list the same way Hostaway does. Amenities are amenityId values, not free-text names. Check-in/out hours are 0–23. Denylisted access and invoicing fields are stripped.
| Name | Type | Req | Description |
|---|---|---|---|
| availabilityDateEnd | string | – | Y-m-d, exclusive departure for fixture stays |
| availabilityDateStart | string | – | Y-m-d, passed to Hostaway listings list |
| availabilityGuestNumber | integer | – | – |
| city | string | – | – |
| includeArchived | boolean | – | If true, omit specialStatus[]=active |
| match | string | – | Search by listing name |
No output schema declared.
No examples provided.
list_messages ~42
List messages in a thread via GET /v1/conversations/{id}/messages. Read-only. There is no send tool.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | integer | yes | – |
No output schema declared.
No examples provided.
list_reservations ~79
List reservations via GET /v1/reservations. Read-only. doorCode / doorCodeVendor / doorCodeInstruction are stripped. Create reservation is not implemented.
| Name | Type | Req | Description |
|---|---|---|---|
| arrivalEndDate | string | – | – |
| arrivalStartDate | string | – | – |
| listingId | integer | – | – |
| match | string | – | Guest name search |
No output schema declared.
No examples provided.
report_completeness ~42
Listing completeness from reads: missing photos, missing house rules, missing amenities (empty listingAmenities). Not a financial report.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | integer | – | – |
No output schema declared.
No examples provided.
report_inbox ~44
Unanswered thread counts by listing, computed from conversation reads. Not a Hostaway owner statement.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | integer | – | – |
| slaHours | number | – | – |
No output schema declared.
No examples provided.
report_occupancy ~75
Occupancy and blocked holes computed from calendar reads. Occupancy = reserved nights / (reserved + available). Blocked holes are consecutive blocked/hardBlock days. Not an owner statement. No financials.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | – |
| listingId | integer | – | – |
| startDate | string | yes | – |
No output schema declared.
No examples provided.
What is the hostaway-kit MCP server?
hostaway-kit is an MCP server listed in the public MCP registry as io.github.stylabs/hostaway-kit. Read-only Hostaway MCP: listings, calendar, inbox, reports. Fixtures, no key. By STYLABS. This page covers its npm package (hostaway-kit).
Is the hostaway-kit MCP server safe to use?
hostaway-kit scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 hostaway-kit MCP server expose?
hostaway-kit exposes 11 tools: list_listings, get_listing, get_calendar, list_reservations, list_conversations, and 6 more. Their descriptions and schemas cost roughly 815 tokens of context every time the server is loaded.
Is the hostaway-kit MCP server still maintained?
hostaway-kit is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the hostaway-kit MCP server under?
hostaway-kit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.