# io.github.whispernight/doormeter (npm · doormeter-mcp)

Ask about your DoorMeter rental deals: saved deals, Zillow/Redfin searches, offers, notes.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `doormeter-mcp`: 61/100 (this document), [markdown](https://verifymcp.io/servers/whispernight-doormeter/doormeter-mcp.md), [page](https://verifymcp.io/servers/whispernight-doormeter/doormeter-mcp)

## Channel facts

- Registry: `npm`
- Package: `doormeter-mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2006 tokens (~167/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.whispernight/doormeter MCP server?

io.github.whispernight/doormeter runs locally as an npm package, launched with npx -y doormeter-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add whispernight-doormeter -- npx -y doormeter-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "whispernight-doormeter": {
      "command": "npx",
      "args": [
        "-y",
        "doormeter-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "whispernight-doormeter": {
      "command": "npx",
      "args": [
        "-y",
        "doormeter-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add whispernight-doormeter -- npx -y doormeter-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whispernight-doormeter": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "doormeter-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add whispernight-doormeter --command npx --arg -y --arg doormeter-mcp
```

### Hermes

```yaml
mcp_servers:
  whispernight-doormeter:
    command: "npx"
    args: ["-y", "doormeter-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "whispernight-doormeter": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "doormeter-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add whispernight-doormeter -t stdio -c npx -a -y doormeter-mcp
```

### Other

```json
{
  "mcpServers": {
    "whispernight-doormeter": {
      "command": "npx",
      "args": [
        "-y",
        "doormeter-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 61, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 46)

First indexed and scored.

## MCP tools (12)

### `doormeter_status` (~52 tokens)

Returns whether DoorMeter (the Chrome extension) is connected, the pairing code to show the user when it asks for one, the plan, versions and how many deals and profiles are saved. Call this first.

### `list_deals` (~211 tokens)

Returns the user's saved deals, newest first, one line each: address, price, latest price drop, score (0–100), monthly cash flow, cash-on-cash and cap rate (fractions), or for live-in the monthly cost and budget gap, plus status and, when numbers can't be computed, why, and the profile they were computed with. "total" counts all matches before the limit.

Input parameters:

- `limit` (integer): At most this many lines (default 50, max 200).
- `minScore` (number): Only deals scoring at least this.
- `scoreAs`: "saved" (default) computes each deal in the strategy it was saved in; a strategy name computes every deal in that one.
- `site` (string)
- `state` (string): Two-letter US state, e.g. "OH".
- `status` (string): watching, offer (offer made) or passed.
- `strategy` (string): Only deals saved in this strategy.

### `get_deal` (~94 tokens)

Returns one saved deal in full: the page's facts, the user's edits, every computed number, price history and notes.

Input parameters:

- `key` (string, required): A saved deal's key, as list_deals returns it (for example "zillow:12345").
- `scoreAs`: "saved" (default) computes each deal in the strategy it was saved in; a strategy name computes every deal in that one.

### `list_profiles` (~31 tokens)

Returns the user's assumption profiles (loan, expenses, targets and per-strategy settings) and which one is active.

### `analyze_deal` (~208 tokens)

Computes a saved deal again with changes (a what-if) and returns the numbers before and after. Nothing is saved.

Input parameters:

- `changes` (object): Edits laid over the deal's own, never saved. Top-level: price, units, rentPerUnit, taxAnnual, insuranceAnnual, hoaMonthly. Groups: assumptions { interestRate (fraction, 0.0725 = 7.25%), downPaymentPc…
- `key` (string, required): A saved deal's key, as list_deals returns it (for example "zillow:12345").
- `strategy` (string): Strategy the numbers are computed in: buy-and-hold, house-hack, brrrr or live-in (living in it).

### `analyze_home` (~188 tokens)

Computes the numbers for a home that isn't saved, from the inputs given, with DoorMeter's ZIP-based rent, tax and insurance estimates for anything left out. Returns the numbers, or what is missing to compute them.

Input parameters:

- `baths` (number)
- `beds` (number)
- `hoaMonthly` (number)
- `price` (number, required)
- `profileId` (string): A profile id from list_profiles; the active profile when left out.
- `rentPerUnit` (number): Monthly rent per unit; estimated from the ZIP when left out.
- `sqft` (number)
- `strategy` (string): Strategy the numbers are computed in: buy-and-hold, house-hack, brrrr or live-in (living in it).
- `taxAnnual` (number)
- `units` (integer)
- `zip` (string, required): Five-digit ZIP code.

### `open_search` (~186 tokens)

Opens a Zillow or Redfin search in a new, visible tab in the user's Chrome and waits (up to 20 s) until DoorMeter has read its homes. Give a search "url", or "site" and a five-digit "zip" with optional price and bed limits. Redfin applies the limits to the search itself; Zillow's search opens without them, so pass the same minPrice, maxPrice and minBeds to search_results. Returns the tab id and how many homes it has. Then call search_results. Calling it again opens another tab.

Input parameters:

- `maxPrice` (number)
- `minBeds` (number)
- `minPrice` (number)
- `site` (string)
- `url` (string): A Zillow or Redfin search page URL (not a single listing).
- `zip` (string): Five-digit ZIP code to search.

### `search_results` (~301 tokens)

Returns every home on an open Zillow or Redfin search tab (the one open_search opened, else the one the user used last), computed with the user's own profile exactly like DoorMeter's search badges: link, address, price, beds, days on market, whether it's new to the user (never opened or saved), score (0–100), cash flow, cash-on-cash and cap rate, or why it can't be computed from the search page. Best score first; "total" counts all matches before the limit.

Input parameters:

- `limit` (integer): At most this many homes (default 50, max 200).
- `maxPrice` (number)
- `minBeds` (number)
- `minPrice` (number)
- `minScore` (number): Only homes scoring at least this.
- `newOnly` (boolean): Only homes the user has never opened or saved.
- `scoreAs`: Strategy to compute every home in: buy-and-hold for the user's investor targets (cash-on-cash, cash flow per door, cap rate), live-in for a home to live in against their budget, house-hack or brrrr;…
- `tabId` (integer): The tab open_search returned; the most recent search tab when left out.

### `analyze_listing` (~179 tokens)

Opens a Zillow or Redfin listing in a visible tab, reads it exactly like DoorMeter's card (the listing's own HOA, tax, rent and value estimates), computes its numbers with the user's profile (and their saved edits if they saved it), then closes the tab unless keepOpen. Tabs open one at a time, a few seconds apart, without taking focus. Reading a listing counts it as opened (it no longer shows as new in search_results). Use it for homes search_results couldn't compute.

Input parameters:

- `keepOpen` (boolean)
- `strategy` (string): Strategy the numbers are computed in: buy-and-hold, house-hack, brrrr or live-in (living in it).
- `url` (string, required): A Zillow or Redfin listing URL (one home's page, e.g. a "url" from search_results).

### `max_offer` (~297 tokens)

Computes the highest price that still meets the user's own targets, like the Offer tab on DoorMeter's card: for buy-and-hold per target (cash-on-cash, cash flow, DSCR); house-hack and brrrr likewise; for live-in a suggested range and the most their budget allows. For a saved deal ("key", with optional "changes" like analyze_deal) or a listing "url".

Input parameters:

- `changes` (object): Edits laid over the deal's own, never saved. Top-level: price, units, rentPerUnit, taxAnnual, insuranceAnnual, hoaMonthly. Groups: assumptions { interestRate (fraction, 0.0725 = 7.25%), downPaymentPc…
- `key` (string): A saved deal's key, as list_deals returns it (for example "zillow:12345").
- `strategy` (string): Strategy the numbers are computed in: buy-and-hold, house-hack, brrrr or live-in (living in it).
- `url` (string): A Zillow or Redfin listing URL (one home's page, e.g. a "url" from search_results).

### `save_deal` (~143 tokens)

Saves a Zillow or Redfin listing to the user's DoorMeter deals, exactly as the card's Save button does (read from its page in a tab, with the active profile), optionally with a first note. Saving a home that is already saved refreshes its page facts and keeps its notes, status, the user's edits, profile and strategy (unless "strategy" is given).

Input parameters:

- `note` (string)
- `strategy` (string): The strategy to save it in; the profile's starting strategy when left out.
- `url` (string, required): A Zillow or Redfin listing URL (one home's page, e.g. a "url" from search_results).

### `update_deal` (~116 tokens)

Changes a saved deal's status (watching, offer = offer made, passed) and/or its notes: "appendNote" adds a line; "notes" replaces all of the user's notes, so prefer appendNote unless they asked to rewrite them. It never deletes a deal.

Input parameters:

- `appendNote` (string)
- `key` (string, required): A saved deal's key, as list_deals returns it (for example "zillow:12345").
- `notes` (string)
- `status` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/whispernight-doormeter/doormeter-mcp#diagnostics

## Score history

- 2026-11-04: 61
- 2026-11-03: 46

## Common questions

### What is the io.github.whispernight/doormeter MCP server?

io.github.whispernight/doormeter is an MCP server listed in the public MCP registry as io.github.whispernight/doormeter. Ask about your DoorMeter rental deals: saved deals, Zillow/Redfin searches, offers, notes. This page covers its npm package (doormeter-mcp).

### Is the io.github.whispernight/doormeter MCP server safe to use?

io.github.whispernight/doormeter scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 io.github.whispernight/doormeter MCP server expose?

io.github.whispernight/doormeter exposes 12 tools: doormeter_status, list_deals, get_deal, list_profiles, analyze_deal, and 7 more. Their descriptions and schemas cost roughly 2,006 tokens of context every time the server is loaded.

### Is the io.github.whispernight/doormeter MCP server still maintained?

io.github.whispernight/doormeter 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.

### What licence is the io.github.whispernight/doormeter MCP server under?

io.github.whispernight/doormeter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/doormeter-mcp
- Socket report: https://socket.dev/npm/package/doormeter-mcp
- Website: https://doormeter.com/guide#agents
- Changelog RSS feed: https://verifymcp.io/servers/whispernight-doormeter/doormeter-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/whispernight-doormeter/doormeter-mcp.json
- HTML version of this page: https://verifymcp.io/servers/whispernight-doormeter/doormeter-mcp