Skip to content
Publisher listing

Inside Airbnb

io.github.pipeworx-io/inside-airbnb

Publisher-submitted data · not independently verified

Listed as active Hybrid v0.2.1
NEXIP / MCP RADAR · EVIDENCE No independent test

Independent technical evidence

No independent observations

Evidence applies only to the current published endpoint. HTTP response does not prove MCP compatibility. A successful MCP discovery result does not prove tools, security, uptime or future availability. No third-party checks run when you open this page.

Not an uptime or safety score.
Verification history and method 0

No allowed third-party observations yet. Unchecked does not mean offline.

Owner-allowlisted server/discover requests only. No credentials, tool execution, arbitrary URL scans, or security certification. Only results for the current published Registry URL are shown.

Profile facts from the publisher

  • Registry identity: io.github.pipeworx-io/inside-airbnb
  • Published format: mixed/other
  • Publisher-declared transport: streamable-http
  • Package identifier: @pipeworx/mcp-inside-airbnb
  • Listed version: 0.2.1

These facts are from the Registry; they do not constitute independent validation of any MCP tools.

About this server

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

Independent technical monitoring is under development.

Authorization: not independently verified
Available tools: not independently verified

Publisher connection options

These endpoints and packages are publisher declarations, not validated integration instructions.

Copy only a published identifier or HTTPS endpoint; follow the client and publisher documentation before connecting. Credentials and approval steps can differ.

Remote URL
https://gateway.pipeworx.io/inside-airbnb/mcp
streamable-http
Package
@pipeworx/mcp-inside-airbnb
stdio npm Package version: 0.2.1

Connection examples for MCP clients

Copy an example only for a publisher-declared HTTPS address and known transport. Review the endpoint, publisher, and client documentation first. Authentication and permissions may require additional setup.

Declared transport: http https://gateway.pipeworx.io/inside-airbnb/mcp
Cursor · mcp.json 
{
    "mcpServers": {
        "inside-airbnb-92947285c891": {
            "url": "https://gateway.pipeworx.io/inside-airbnb/mcp"
        }
    }
}
VS Code · .vscode/mcp.json 
{
    "servers": {
        "inside-airbnb-92947285c891": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/inside-airbnb/mcp"
        }
    }
}

Examples are generated from Registry metadata, not a successful connection test. Do not commit tokens, passwords or private configuration files to a repository.

Cursor MCP setup ↗ VS Code MCP setup ↗

Package identifiers are not install commands. Review the package and publisher before running any code.

Connection readiness / publisher metadata

Before you connect

Example available to copy

A prepared example is not a successful MCP connection. The Registry listing alone does not confirm tool compatibility, uptime, authentication or safety.

1Remote endpoints with supported transport
0Remote endpoints requiring review
1Local packages
Authentication Unknown — may require OAuth, an API key or another sign-in method

Publisher-supplied requirements may be shown below when available. Missing declarations are not evidence of anonymous access. OAuth is not verified.

No published credential fields in this index

The developer may require OAuth, a key or other permissions even when the Registry has no declared header fields. The metadata scan may also be incomplete.

Recommended steps

  1. Check the publisher website and repository before connecting or installing anything.
  2. Confirm the transport, HTTPS URL and client version. Template URLs with {variables} need publisher-specific values.
  3. Configure authentication in your trusted MCP client using the publisher instructions. Never paste secrets into NexIP.
  4. Test within the client with the minimum necessary permissions. Review all tool access requests.

If connection fails

HTTP 401 / 403 — authentication or access may be required

Check the client OAuth flow, account access and publisher-provided header requirements. A 401 alone does not prove OAuth is configured correctly.

HTTP 404 — check the published URL and endpoint path

Check whether the publisher changed the MCP path or requires a tenant-specific URL. Do not guess private API endpoints.

HTTP 405 — GET may not be supported

A valid MCP HTTP endpoint need not accept a browser GET. Use a compatible MCP client and the declared transport.

Timeout or TLS issue

Check client/network conditions and the publisher service status; do not disable TLS validation to make an untrusted server connect.

NexIP Radar / R4

Independent HTTP observations

Publisher listing ≠ Independent HTTP observations

No independent checks have been run yet.

HTTP results do not verify MCP protocol compatibility, security or available tools. Synthetic tests are never displayed.

Published versions

Cached history from the official Registry; coverage may be incomplete until a separate import runs.

Version history not loaded yet.