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.

Inside Airbnb

NPM · @PIPEWORX/MCP-INSIDE-AIRBNB · 2 COMPONENTS

inside-airbnb -- short-term rental listings by city (fleet #2973).

+3 this week 82 Trust /100

Last scanned (6 hours ago)

Scores higher than 72% of npm servers

Category E-commerce

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-inside-airbnb). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 772 tokens (~257/item across 3 items; 3 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    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 · Analysed npm/@pipeworx/mcp-inside-airbnb@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-inside-airbnb
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-inside-airbnb/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637445167
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:96277d60a5d0d855b59af00b67e430d05ea4beafc7c2e2a2bfd1c1356e25ebb3a0bf4945dc6e39ace2efaa1cfb57dc9a001b23e1bfbe262d630720726

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~717 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
list_str_cities ~144

Every city this pack has short-term rental (Airbnb) data for, from Inside Airbnb. Returns, per city: display name, country, currency the price fields are IN (prices are never converted -- each city's own local currency, e.g. CZK for Prague, not USD), how many listings are loaded, the overall median nightly price, and that city's OWN scrape date (data_as_of) -- coverage dates differ city to city because Inside Airbnb scrapes each one independently. Call this first if unsure whether a city is covered; str_city_summary and str_listings refuse an uncovered city by naming the covered set, but this is the smaller way to check.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

str_city_summary ~207

City-wide short-term rental summary for one city, from Inside Airbnb: total listings, overall median nightly price (in that city's own local currency -- see the `currency` field, e.g. CZK for Prague, never converted), a breakdown by room type (entire home/apt, private room, shared room, hotel room -- each with its own count and median price), and the top neighbourhoods by listing count (each with its own listing count and median price). Pass a city name (e.g. "Paris", "NYC", "San Francisco") or its slug (e.g. "new-york-city"). Returns data_as_of = that city's own Inside Airbnb scrape date. An uncovered city is refused by name, listing every covered city rather than returning an empty result -- call list_str_cities to browse the full set.

NameTypeReqDescription
citystringyesCity name or slug, e.g. "Paris", "NYC", "san-francisco".

No output schema declared.

No examples provided.

str_listings ~366

Listing-level short-term rental rows for one city, from Inside Airbnb: listing id, public listing URL, listing title, neighbourhood, room type, nightly price (in that city's own local currency -- see the response's `currency` field, never converted; min_price/max_price filter in that same currency), minimum nights, review counts, last review date, availability_365, and the host's total listing count (a bare number -- no host name, no host id, no host profile link; see the pack's "Personal data" note). Pass city plus any combination of neighbourhood, room_type ("Entire home/apt", "Private room", "Shared room", "Hotel room", or a loose match like "apartment"), min_price, max_price to narrow. Rows beyond `limit` are reported via truncated/total_matching rather than silently dropped -- narrow the filters or page with limit/offset to see the rest. An uncovered city is refused by name, listing every covered city.

NameTypeReqDescription
citystringyesCity name or slug, e.g. "Paris", "NYC", "san-francisco".
limitnumber–Max rows to return, 1-200. Default 50. A truncated response carries truncated:true and total_matching.
max_pricenumber–Optional: maximum nightly price.
min_pricenumber–Optional: minimum nightly price.
neighbourhoodstring–Optional: filter to one neighbourhood (case-insensitive exact match).
offsetnumber–Pagination offset. Default 0.
room_typestring–Optional: "Entire home/apt", "Private room", "Shared room", "Hotel room" (loose matches like "apartment" or "house" also work).

No output schema declared.

No examples provided.

Install

How do I install the Inside Airbnb MCP server?

Inside Airbnb runs locally as an npm package, launched with npx -y @pipeworx/mcp-inside-airbnb. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-inside-airbnb

# add to Claude Code
claude mcp add pipeworx-io-inside-airbnb -- npx -y @pipeworx/mcp-inside-airbnb
Common questions

What is the Inside Airbnb MCP server?

Inside Airbnb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/inside-airbnb. inside-airbnb -- short-term rental listings by city (fleet #2973). This page covers its npm package (@pipeworx/mcp-inside-airbnb).

Is the Inside Airbnb MCP server safe to use?

Inside Airbnb scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Inside Airbnb MCP server expose?

Inside Airbnb exposes 3 tools: list_str_cities, str_city_summary, str_listings. Their descriptions and schemas cost roughly 717 tokens of context every time the server is loaded.

Is the Inside Airbnb MCP server still maintained?

Inside Airbnb 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.

What licence is the Inside Airbnb MCP server under?

Inside Airbnb declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.