# TerraVue (remote · api.terravue.app)

Analyze any US home: buy vs rent Monte Carlo, affordability, and ZIP-level appreciation data.

- Trust score: 69/100 (medium)
- Change this week: +11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `api.terravue.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/app-terravue-terravue/api.md), [page](https://verifymcp.io/servers/app-terravue-terravue/api)

## Channel facts

- Endpoint: `https://api.terravue.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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

Scored 2026-09-28.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2655 tokens (~442/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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.

## Install

### How do I install the TerraVue MCP server?

TerraVue is a hosted endpoint at https://api.terravue.app/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.

### Claude

```bash
claude mcp add --transport http app-terravue-terravue 'https://api.terravue.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-terravue-terravue": {
      "url": "https://api.terravue.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-terravue-terravue": {
      "type": "http",
      "url": "https://api.terravue.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-terravue-terravue]
url = "https://api.terravue.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-terravue-terravue": {
      "type": "remote",
      "url": "https://api.terravue.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-terravue-terravue --url 'https://api.terravue.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-terravue-terravue:
    url: "https://api.terravue.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-terravue-terravue": {
      "Transport": "http",
      "Url": "https://api.terravue.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-terravue-terravue -t streamable-http -u 'https://api.terravue.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-terravue-terravue": {
      "type": "http",
      "url": "https://api.terravue.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-28 (score 69, +8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 61, +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.

### 2026-09-25 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-20 (score 58)

First indexed and scored.

## MCP tools (6)

### `analyze_address` (~157 tokens)

Look up a US address (or bare 5-digit ZIP): ZIP-level home-price appreciation
    forecast (FHFA data back to 1975), estimated market rent, and neighborhood signals
    (schools, walkability, water quality, grocery/dining/outdoors proximity).

    For a full street address this also returns sub-ZIP `nbhd*` fields describing the
    specific census tract - how its prices, incomes and build era compare to the rest of
    the ZIP. That is POSITION, not a neighborhood forecast; see _units.

    property_type: sfr | condo | townhome | multi

Input parameters:

- `address` (string, required)
- `bedrooms` (integer)
- `property_type` (string)

### `request_capability` (~133 tokens)

Record a question TerraVue could not answer, so it can be built. Call this whenever
    a user asks for something outside the current tools' coverage (rental metrics, Airbnb
    modeling, valuations, move-vs-stay, non-US, anything else), then tell the user their
    request was captured. Keep `description` to the capability needed — no names, emails,
    or other personal details.

    category: rental_metrics | str_airbnb | valuation | move_vs_stay | data_coverage | other

Input parameters:

- `category` (string)
- `description` (string, required)

### `buy_vs_rent` (~268 tokens)

Should someone buy this home or keep renting? Runs the TerraVue engine: a
    deterministic 30-year simulation plus a 500-scenario Monte Carlo over correlated
    market paths. Returns the probability buying wins, the breakeven hold period, and
    net-worth outcomes.

    monthly_rent = what the person would pay to rent THE SAME HOME to live in — an
    owner-occupant buy-vs-rent decision, NOT rental income they'd collect as a landlord
    (this tool does not model rental cash flow; that lens lives on terravue.app). A rent
    far out of line with home_price is almost certainly a misunderstanding — confirm it
    before trusting the verdict. If `address` is given, the ZIP's real appreciation forecast
    and regional tax/insurance defaults are used (explicit parameters still win).

Input parameters:

- `address`
- `analysis_years` (integer)
- `down_payment_pct` (number)
- `fixed_rate` (number)
- `hoa_monthly` (number)
- `home_appreciation_rate`
- `home_price` (number, required)
- `investment_return_rate` (number)
- `monthly_rent` (number, required)
- `property_tax_rate`

### `affordability` (~285 tokens)

Can this buyer afford this home? Returns the monthly PITI payment, front-end and
    back-end debt-to-income ratios (what a lender qualifies on), the income needed at a
    28% front-end ratio, estimated after-tax money left over each month, the cash cushion
    left after closing, and a plain Comfortable / Qualifiable-tight / Stretch verdict.

    monthly_debts = recurring debt obligations a lender counts (car, student loan, minimum
    credit-card) — NOT living costs; this feeds DTI. monthly_expenses = living costs (food,
    utilities, childcare) used ONLY for the 'left over each month' life check, never DTI.
    Pass `address` to ground property tax + insurance in the ZIP's real rates. Pass
    `liquid_savings` to get the post-closing cash cushion (months of payment covered).

Input parameters:

- `address`
- `annual_income` (number, required)
- `down_payment_pct` (number)
- `fixed_rate` (number)
- `hoa_monthly` (number)
- `home_price` (number, required)
- `insurance_rate`
- `liquid_savings`
- `marginal_tax_rate` (number)
- `monthly_debts` (number)
- `monthly_expenses` (number)
- `property_tax_rate`

### `compare_areas` (~149 tokens)

Analyze and RANK 2-12 ZIPs or addresses side by side on the signals TerraVue has:
    home-price appreciation forecast (and how each compares to the national average),
    school rating, walkability, education level, and water quality. Returns the correct
    city name per ZIP, so locations are never guessed or mislabeled.

    Use for "which areas have the best appreciation / schools / upside." TerraVue has no
    listing inventory and cannot discover ZIPs on its own — to scan a metro, pass that
    metro's ZIP codes (the ranking then covers exactly what you passed).

Input parameters:

- `addresses` (array, required)
- `bedrooms` (integer)

### `affordable_price` (~300 tokens)

What's the most this buyer can afford? The reverse of `affordability` — 'what price
    can I afford?' instead of 'can I afford this specific home?'. Solves for the maximum
    home price under standard lender limits: a front-end DTI cap (default 28% = housing /
    gross income) and a back-end cap (default 36% = housing + other debts / gross income).
    If `liquid_savings` is given, also caps by the cash available for down payment + closing
    and reports which limit binds. Returns the affordable price, the PITI and DTIs at that
    price, and the cash to close. Pass `address` to ground property tax + insurance in the
    ZIP's real rates.

    This is a lender-limit ceiling, not a comfort recommendation — feed the result into
    `affordability` (or buy_vs_rent) to check monthly slack and whether buying pencils.

Input parameters:

- `address`
- `annual_income` (number, required)
- `back_end_dti_pct` (number)
- `down_payment_pct` (number)
- `fixed_rate` (number)
- `front_end_dti_pct` (number)
- `hoa_monthly` (number)
- `insurance_rate`
- `liquid_savings`
- `monthly_debts` (number)
- `property_tax_rate`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-terravue-terravue/api#diagnostics

## Score history

- 2026-09-28: 69
- 2026-09-27: 61
- 2026-09-26: 61
- 2026-09-25: 60
- 2026-09-24: 60
- 2026-09-23: 59
- 2026-09-22: 59
- 2026-09-21: 58
- 2026-09-20: 58

## Common questions

### What is the TerraVue MCP server?

TerraVue is an MCP server listed in the public MCP registry as app.terravue/terravue. Analyze any US home: buy vs rent Monte Carlo, affordability, and ZIP-level appreciation data. This page covers its hosted endpoint (https://api.terravue.app/mcp).

### Is the TerraVue MCP server safe to use?

TerraVue scores 69 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 TerraVue MCP server expose?

TerraVue exposes 6 tools: analyze_address, request_capability, buy_vs_rent, affordability, compare_areas, affordable_price. Their descriptions and schemas cost roughly 1,292 tokens of context every time the server is loaded.

### Does the TerraVue MCP server require authentication?

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

### Is the TerraVue MCP server still maintained?

TerraVue is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.terravue.app/mcp
- Website: https://www.terravue.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-terravue-terravue/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-terravue-terravue/api.json
- HTML version of this page: https://verifymcp.io/servers/app-terravue-terravue/api