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.

heidi.living furnished stays

REMOTE · HEIDI.LIVING

Furnished monthly stays in Los Angeles: regions, application links, answers. Read-only, no sign-in.

Available components

0 this week 71 Trust /100

Last scanned (22 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 325 tokens (~108/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 7 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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.

  • 30 Oct 26 0
    • Stability: 0.03 → fail ▼ security
    • Tool “booking_link” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “faq” rewrote its description, which is the text the model reads security
    • Tool “list_regions” rewrote its description, which is the text the model reads security
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “application_link” functional
    • Tool “faq” changed its title: Questions about booking → Questions about applying cosmetic
  • 29 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 71

    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 4 Nov 2026 · Probed https://heidi.living/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=heidi.living CN=YE2,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 535bbcaf7dd17b20cb1c1b7457fcd7ac2b0
SANs: heidi.living
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of heidi.living. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
living. present 5373 13 Verified
heidi.living. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://heidi.living/mcp Verified 200
http (plaintext) http://heidi.living/mcp HTTPS enforced 301 https://heidi.living/mcp
MCP tools · 3 exposed · ~232 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
application_link ~133

A link to heidi.living's application page, filled in with a guest's area, move-in date, length of stay and number of guests. The guest opens it, signs in and applies; every value stays editable there.

NameTypeReqDescription
areastring–A service area's slug, as list_regions gives it (e.g. venice).
guestsinteger–Number of guests, 1 to 6.
monthsinteger–Length of stay in months, 1 to 6. Needs move_in_date.
move_in_datestring–Move-in day, YYYY-MM-DD.

No output schema declared.

No examples provided.

faq ~48

heidi.living's answers to the questions guests ask before applying: what it is, what applying needs, how long a stay is, signing, paying rent, and what happens to a driver's license.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_regions ~51

Where heidi.living has furnished monthly homes in Los Angeles: each region with its page, its description, and its neighborhoods, saying which have an application search on heidi.living and which are coming soon.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the heidi.living furnished stays MCP server?

heidi.living furnished stays is a hosted endpoint at https://heidi.living/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · heidi.living

# add to Claude Code
claude mcp add --transport http living-heidi-stays 'https://heidi.living/mcp'
Common questions

What is the heidi.living furnished stays MCP server?

heidi.living furnished stays is an MCP server listed in the public MCP registry as living.heidi/stays. Furnished monthly stays in Los Angeles: regions, application links, answers. Read-only, no sign-in. This page covers its hosted endpoint (https://heidi.living/mcp).

Is the heidi.living furnished stays MCP server safe to use?

heidi.living furnished stays scores 71 out of 100 on VerifyMCP. 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 heidi.living furnished stays MCP server expose?

heidi.living furnished stays exposes 3 tools: list_regions, application_link, faq. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.

Does the heidi.living furnished stays MCP server require authentication?

No. We connected to heidi.living furnished stays without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the heidi.living furnished stays MCP server still maintained?

heidi.living furnished stays is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.