TerraVue
REMOTE · API.TERRAVUE.APP
Analyze any US home: buy vs rent Monte Carlo, affordability, and ZIP-level appreciation data.
Available components
Last scanned (16 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3932 tokens (~655/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.
Endpoint address
- Registry says
https://api.terravue.app/mcp- Package shows
https://api.terravue.app/mcp/
The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 12 Oct 26 0
- Schema quality: 442 → 655 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- “affordability” reworded the description of “address” cosmetic
- “affordability” reworded the description of “annual_income” cosmetic
- “affordability” reworded the description of “down_payment_pct” cosmetic
- “affordability” reworded the description of “fixed_rate” cosmetic
- “affordability” reworded the description of “hoa_monthly” cosmetic
- “affordability” reworded the description of “home_price” cosmetic
- “affordability” reworded the description of “insurance_rate” cosmetic
- “affordability” reworded the description of “liquid_savings” cosmetic
- “affordability” reworded the description of “marginal_tax_rate” cosmetic
- “affordability” reworded the description of “monthly_debts” cosmetic
- “affordability” reworded the description of “monthly_expenses” cosmetic
- “affordability” reworded the description of “property_tax_rate” cosmetic
- “affordable_price” reworded the description of “address” cosmetic
- “affordable_price” reworded the description of “annual_income” cosmetic
- “affordable_price” reworded the description of “back_end_dti_pct” cosmetic
- “affordable_price” reworded the description of “down_payment_pct” cosmetic
- “affordable_price” reworded the description of “fixed_rate” cosmetic
- “affordable_price” reworded the description of “front_end_dti_pct” cosmetic
- “affordable_price” reworded the description of “hoa_monthly” cosmetic
- “affordable_price” reworded the description of “insurance_rate” cosmetic
- “affordable_price” reworded the description of “liquid_savings” cosmetic
- “affordable_price” reworded the description of “monthly_debts” cosmetic
- “affordable_price” reworded the description of “property_tax_rate” cosmetic
- “analyze_address” reworded the description of “address” cosmetic
- “analyze_address” reworded the description of “bedrooms” cosmetic
- “analyze_address” reworded the description of “property_type” cosmetic
- “buy_vs_rent” reworded the description of “address” cosmetic
- “buy_vs_rent” reworded the description of “analysis_years” cosmetic
- “buy_vs_rent” reworded the description of “down_payment_pct” cosmetic
- “buy_vs_rent” reworded the description of “fixed_rate” cosmetic
- “buy_vs_rent” reworded the description of “hoa_monthly” cosmetic
- “buy_vs_rent” reworded the description of “home_appreciation_rate” cosmetic
- “buy_vs_rent” reworded the description of “home_price” cosmetic
- “buy_vs_rent” reworded the description of “investment_return_rate” cosmetic
- “buy_vs_rent” reworded the description of “monthly_rent” cosmetic
- “buy_vs_rent” reworded the description of “property_tax_rate” cosmetic
- “compare_areas” reworded the description of “addresses” cosmetic
- “compare_areas” reworded the description of “bedrooms” cosmetic
- “request_capability” reworded the description of “category” cosmetic
- “request_capability” reworded the description of “description” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://api.terravue.app/mcp/ · Declared URL https://api.terravue.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.terravue.app | CN=WR3,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 7015949f46f20a781230e3a0d967193e |
| SANs: api.terravue.app | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.terravue.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| terravue.app. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.terravue.app/mcp | Redirected | 307 | https://api.terravue.app/mcp/ |
| streamable-http · followed | https://api.terravue.app/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.terravue.app/mcp | HTTPS enforced | 302 | https://api.terravue.app/mcp |
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 →
affordability ~654
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Full US street address, or a bare 5-digit ZIP. Pass it whenever it is known: it grounds property tax, insurance and the appreciation forecast in that ZIP's real figures instead of national defaults. |
| annual_income | number | yes | Gross household income before tax, in whole US dollars per year, e.g. 140000. |
| down_payment_pct | number | – | Down payment as a PERCENT of price: 20 means 20%. Not a fraction (not 0.20). |
| fixed_rate | number | – | Mortgage interest rate as an annual PERCENT: 6.75 means 6.75%. Not a decimal (not 0.0675). |
| hoa_monthly | number | – | HOA or condo fee in US dollars per month. 0 for most single-family homes. |
| home_price | number | yes | Purchase price in whole US dollars, e.g. 650000 (not 650 or 650k). |
| insurance_rate | – | – | Annual homeowners insurance as a PERCENT of home value: 0.45 means 0.45%/yr. Leave unset to use the regional default. |
| liquid_savings | – | – | Cash available for down payment and closing costs, in US dollars. Supplying it adds the post-closing cash cushion and the cash-limited price check. |
| marginal_tax_rate | number | – | Marginal federal income tax rate as a PERCENT: 24 means 24%. Used only to estimate after-tax take-home for the monthly-slack figure. |
| monthly_debts | number | – | Recurring DEBT obligations a lender counts, in dollars per month: car payment, student loan, minimum credit-card payment. This feeds DTI. Do NOT put groceries, utilities or childcare here. |
| monthly_expenses | number | – | Ordinary living costs in US dollars per month — food, utilities, childcare. Used ONLY for the 'left over each month' life check and NEVER for DTI. Keep these separate from `monthly_debts`, which is t… |
| property_tax_rate | – | – | Annual property tax as a PERCENT of home value: 0.55 means 0.55%/yr. Leave unset to use the ZIP's real rate when `address` is given. |
No output schema declared.
No examples provided.
affordable_price ~639
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Full US street address, or a bare 5-digit ZIP. Pass it whenever it is known: it grounds property tax, insurance and the appreciation forecast in that ZIP's real figures instead of national defaults. |
| annual_income | number | yes | Gross household income before tax, in whole US dollars per year, e.g. 140000. |
| back_end_dti_pct | number | – | Back-end DTI cap as a PERCENT: housing plus other debts, divided by gross income. The lender standard is 36. Only change it if the user names a different limit. |
| down_payment_pct | number | – | Down payment as a PERCENT of price: 20 means 20%. Not a fraction (not 0.20). |
| fixed_rate | number | – | Mortgage interest rate as an annual PERCENT: 6.75 means 6.75%. Not a decimal (not 0.0675). |
| front_end_dti_pct | number | – | Front-end DTI cap as a PERCENT: housing cost divided by gross income. The lender standard is 28. Only change it if the user names a different limit. |
| hoa_monthly | number | – | HOA or condo fee in US dollars per month. 0 for most single-family homes. |
| insurance_rate | – | – | Annual homeowners insurance as a PERCENT of home value: 0.45 means 0.45%/yr. Leave unset to use the regional default. |
| liquid_savings | – | – | Cash available for down payment and closing costs, in US dollars. Supplying it adds the post-closing cash cushion and the cash-limited price check. |
| monthly_debts | number | – | Recurring DEBT obligations a lender counts, in dollars per month: car payment, student loan, minimum credit-card payment. This feeds DTI. Do NOT put groceries, utilities or childcare here. |
| property_tax_rate | – | – | Annual property tax as a PERCENT of home value: 0.55 means 0.55%/yr. Leave unset to use the ZIP's real rate when `address` is given. |
No output schema declared.
No examples provided.
analyze_address ~231
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
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full US street address, or a bare 5-digit ZIP. Pass it whenever it is known: it grounds property tax, insurance and the appreciation forecast in that ZIP's real figures instead of national defaults. |
| bedrooms | integer | – | Bedroom count, used to select the matching market-rent estimate for the ZIP. Defaults to 2. |
| property_type | string | – | One of: sfr (single-family), condo, townhome, multi. |
No output schema declared.
No examples provided.
buy_vs_rent ~633
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Full US street address, or a bare 5-digit ZIP. Pass it whenever it is known: it grounds property tax, insurance and the appreciation forecast in that ZIP's real figures instead of national defaults. |
| analysis_years | integer | – | Hold period in years. Use the horizon the person actually stated — if they say 'about five years', pass 5. Only default to 30 when no horizon was given. |
| down_payment_pct | number | – | Down payment as a PERCENT of price: 20 means 20%. Not a fraction (not 0.20). |
| fixed_rate | number | – | Mortgage interest rate as an annual PERCENT: 6.75 means 6.75%. Not a decimal (not 0.0675). |
| hoa_monthly | number | – | HOA or condo fee in US dollars per month. 0 for most single-family homes. |
| home_appreciation_rate | – | – | Annual home appreciation as a PERCENT: 3.5 means 3.5%/yr. Prefer leaving this unset and passing `address` instead, so the ZIP's FHFA-derived forecast is used rather than a guess. |
| home_price | number | yes | Purchase price in whole US dollars, e.g. 650000 (not 650 or 650k). |
| investment_return_rate | number | – | Annual return the renter earns on invested cash, as a PERCENT: 9.5 means 9.5%/yr, roughly long-run equities. This assumption drives the result more than any other — drop it to about 4.5 if the altern… |
| monthly_rent | number | yes | What this person would pay per month, in US dollars, to rent THE SAME HOME to live in. This is an owner-occupant comparison — it is NOT rental income they would collect as a landlord. |
| property_tax_rate | – | – | Annual property tax as a PERCENT of home value: 0.55 means 0.55%/yr. Leave unset to use the ZIP's real rate when `address` is given. |
No output schema declared.
No examples provided.
compare_areas ~225
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).
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | 2 to 12 US addresses or bare 5-digit ZIPs to rank side by side. TerraVue has no listing inventory and cannot discover ZIPs on its own — to scan a metro, pass that metro's ZIP codes explicitly, and th… |
| bedrooms | integer | – | Bedroom count, used to select the matching market-rent estimate for the ZIP. Defaults to 2. |
No output schema declared.
No examples provided.
request_capability ~187
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
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of: rental_metrics, str_airbnb, valuation, move_vs_stay, data_coverage, other. |
| description | string | yes | What the user asked for that TerraVue could not do, in one or two sentences. The capability only — never names, emails, addresses or other personal details. |
No output schema declared.
No examples provided.
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.
remote · api.terravue.app
claude mcp add --transport http app-terravue-terravue 'https://api.terravue.app/mcp'
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 82 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 2,569 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TerraVue MCP server?
VerifyMCP ran 13 checks on TerraVue, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.