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.

HOUSINGFAX

REMOTE · HOUSINGFAX.COM

Immediate home report for a building or flat in Spain: 22 checks from official public sources.

Available components

0 this week 84 Trust /100

Last scanned (10 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

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 Security77
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2527 tokens (~315/item across 8 items; 8 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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.97 → pass security
  • 29 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 25 Oct 26 0
    • Tool “create_free_report” rewrote its description, which is the text the model reads security
    • Tool “get_products” rewrote its description, which is the text the model reads security
    • Server version: 1.2.0 → 1.3.0 functional
  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

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 5 Nov 2026 · Probed https://housingfax.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=housingfax.com CN=YE2,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 5165e9d9069de62e931f64618ef0292d524
SANs: *.housingfax.com, housingfax.com
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 secure

Validation of housingfax.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
housingfax.com. present 2371 13 Verified
housingfax.com. Verified address RRset verified with the apex keys
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
content-security-policy default-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://*.js.stripe.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://bat.bing.com https://bat.bing.net https://connect.facebook.net https://*.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://images.unsplash.com https://*.stripe.com https://*.link.com https://*.google-analytics.com https://*.googletagmanager.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://pagead2.googlesyndication.com https://www.google.com https://www.google.es https://bat.bing.com https://bat.bing.net https://www.facebook.com https://www.ign.es https://ovc.catastro.meh.es; font-src 'self'; connect-src 'self' https://api.stripe.com https://checkout.stripe.com https://link.com https://*.link.com https://*.google-analytics.com https://*.analytics.google.com https://*.go
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self), payment=(self "https://js.stripe.com" "https://checkout.stripe.com"), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://housingfax.com/mcp Verified 200
http (plaintext) http://housingfax.com/mcp HTTPS enforced 308 https://housingfax.com/mcp
MCP tools · 8 exposed · ~2,184 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
check_coverage ~227

Says whether HOUSINGFAX can produce a report for a province (name or two-digit INE code) and, optionally, finds the municipality in the official street directory. Status covered, not_yet_covered (Navarra: foral adapter pending) or unrecognized; not_yet_covered never means no risk. In the Basque Country (Araba, Bizkaia, Gipuzkoa) the report covers the whole building, not a single flat. municipalityLookup unavailable means the directory did not answer: unknown, not missing. Call it before search_address when you are not sure the place is covered.

NameTypeReqDescription
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
municipalitystring–Optional municipality name; it is looked up in the official street directory of the province.
provincestring–Spanish province by name (Madrid, València, Bizkaia…) or two-digit INE code (28). Omit both fields to list every province.
NameTypeReqDescription
contractstringyes–
coverageNotestringyes–
languagestringyes–
municipalities–yes–
municipalityLookupstringyes–
provincesarrayyes–

No examples provided.

create_free_report ~402

Queues the report for the building resolved with resolve_building and returns a private link (previewUrl) and a statusToken for get_report_status. Every report is free: it is the full report with PDF, with the building condition assessment when the building has an IEE/ITE record, generated in minutes. CONSENT: before calling, show the person the consent text returned by get_products (consent.text, same language) with its terms and privacy links, and set consent=true only if the person has explicitly accepted it in this conversation; pass consent.statementSha256 as consentStatementSha256. Never accept on the person's behalf. The email is optional (ready notice with the link and the PDF) and only with the person's permission. If the answer is CHANNEL_AT_CAPACITY or CLIENT_LIMIT, wait the retryAfterSeconds it gives and try again. The link is private: give it only to the person, never publish it. Always tell the person: it is a preliminary, automated report built from public records, not a technical inspection, valuation, certificate, safety assessment or legal advice; probabilities are given as words (very low to very high), never as percentages; a check without data (○) means unknown, not negative or safe; Navarra is not covered yet; the report is only available as a private link.

NameTypeReqDescription
consentbooleanyestrue only if the person explicitly accepted the consent text from get_products.
consentStatementSha256stringyesconsent.statementSha256 from get_products for the same language.
emailstring–Optional email of the person for the ready notice with the link and the PDF, only with their permission.
languagestring–Language of the report and of the texts: es, en, de, nl or fr. Default es. Must be the language of the consent text shown.
resolutionTokenstringyesresolutionToken returned by resolve_building (valid 15 minutes).
NameTypeReqDescription
contractstringyes–
emailNoticebooleanyes–
jobIdstringyes–
languagestringyes–
noticestringyes–
pollAfterSecondsintegeryes–
previewUrlstringyes–
statusstringyes–
statusTokenstringyes–

No examples provided.

get_products ~218

Returns the HOUSINGFAX report for a home in Spain (productMode free): a single product, the full report with web view and PDF, free of charge, with the building condition assessment when the building has an IEE/ITE record. Also returns the capacity limits of the channel (no daily cap) and the consent text (with its SHA-256) that the person must accept before create_free_report. Use it when someone asks what HOUSINGFAX offers or before ordering. Always tell the person: it is a preliminary, automated report built from public records, not a technical inspection, valuation, certificate, safety assessment or legal advice; probabilities are given as words (very low to very high), never as percentages; a check without data (○) means unknown, not negative or safe; Navarra is not covered yet; the report is only available as a private link.

NameTypeReqDescription
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
NameTypeReqDescription
capacityobject––
checksCountintegeryes–
consentobjectyes–
contractstringyes–
currencystringyes–
disclaimerstringyes–
exampleReportUrlstringyes–
freeReportLimitsobject––
languagestringyes–
orderUrlstringyes–
priceNotestringyes–
pricingUrlstringyes–
productModestring––
productsarrayyes–
upgrade–––
vatIncludedbooleanyes–

No examples provided.

get_report_status ~148

Returns the status of a report created with create_free_report: queued, in_progress, ready, failed or expired, with the private link when ready. Wait pollAfterSeconds between calls. withLimitations=true means some source did not answer and its check shows ○ no data with the reason (unknown, not negative). Give the link only to the person.

NameTypeReqDescription
jobIdstringyesjobId returned by create_free_report or purchase_report.
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
statusTokenstringyesstatusToken returned by create_free_report or purchase_report.
NameTypeReqDescription
contractstringyes–
errorCodestring––
estimatedSecondsinteger––
jobIdstringyes–
languagestringyes–
noticestringyes–
paymentobject––
pollAfterSecondsinteger––
previewUrlstring––
queuePositioninteger––
stage–yes–
statusstringyes–
withLimitationsboolean––

No examples provided.

list_checks ~182

Lists the 22 numbered checks of the report (title, question it answers and whether its source is integrated yet) and the meaning of the ✓ / ⚠ / ○ marks. Use it to explain what the report looks at. Checks marked pending_integration show as ○ no data, never as a negative result. Always tell the person: it is a preliminary, automated report built from public records, not a technical inspection, valuation, certificate, safety assessment or legal advice; probabilities are given as words (very low to very high), never as percentages; a check without data (○) means unknown, not negative or safe; Navarra is not covered yet; the report is only available as a private link.

NameTypeReqDescription
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
NameTypeReqDescription
checksarrayyes–
contractstringyes–
countintegeryes–
languagestringyes–
methodologyUrlstringyes–
semaphoreobjectyes–

No examples provided.

purchase_report ~395

Not available: every report is free; use create_free_report. This tool stays in the contract for compatibility and answers NOT_FOR_SALE without creating anything.

NameTypeReqDescription
acceptTermsbooleanyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
consentbooleanyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
consentStatementSha256stringyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
emailstringyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
freeReportobject–Kept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
resolutionTokenstring–Kept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
termsVersionstringyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
tierstringyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
waiveWithdrawalRightbooleanyesKept for compatibility with contract 1.1.0; not used while every report is free (purchase_report answers NOT_FOR_SALE).
NameTypeReqDescription
agentContractingTermsUrlstringyes–
checkoutExpiresAtstringyes–
checkoutUrlstringyes–
contractstringyes–
currencystringyes–
jobIdstringyes–
languagestringyes–
namestringyes–
noticestringyes–
orderIdstringyes–
pollAfterSecondsintegeryes–
pricestringyes–
priceCentsintegeryes–
reportUrlstringyes–
statusstringyes–
statusTokenstringyes–
termsVersionstringyes–
tierstringyes–
vatIncludedbooleanyes–

No examples provided.

resolve_building ~321

Identifies the building from an address found with search_address (object address) or from a cadastral reference (14 characters = building or plot; 18 or 20 = a single flat). Give either cadastralReference or address, not both. status resolved returns a resolutionToken (valid 15 minutes) for create_free_report, the building's public cadastral data and whether an IEE/ITE record exists (ieeAvailability; unverified means the registry did not answer, not that there is none), which decides whether the report includes the building condition assessment. status select_unit lists the units: ask the person which flat, or repeat with the 14-character reference and scope=building for the whole building. Only non-protected cadastral data is returned. Do not publish the address or reference.

NameTypeReqDescription
addressobject–Coded address from search_address (provinceCode, municipalityDgcCode, municipalityIneCode, streetTypeCode, streetCode, number; localityId in the Basque Country; optional block, stair, floor, door). U…
cadastralReferencestring–Cadastral reference: 14 characters (building or plot), 18 or 20 (a flat). Use instead of address.
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
scopestring–Only with a 14-character cadastralReference: building to report on the whole building.
NameTypeReqDescription
availableNumbersarray––
availableTiersarrayyes–
building–yes–
candidatesarrayyes–
contractstringyes–
evaluationScope–yes–
ieeAvailability–yes–
languagestringyes–
noticestringyes–
resolutionExpiresInSeconds–yes–
resolutionToken–yes–
statusstringyes–

No examples provided.

search_address ~291

Two steps to build an address. kind=municipality with provinceCode and q returns municipalities and their codes. kind=street with provinceCode, municipalityDgcCode, municipalityIneCode (from the first step) and q returns streets with streetTypeCode and streetCode (and localityId in the Basque Country). Pass the chosen street, the house number and the codes to resolve_building. Only for places check_coverage reports as covered. Do not store or publish the address.

NameTypeReqDescription
kindstringyesmunicipality (step 1) or street (step 2).
languagestring–Language of the texts in the answer (and of the report): es, en, de, nl or fr. Default es.
municipalityDgcCodestring–Only with kind=street: municipalityDgcCode from step 1.
municipalityIneCodestring–Only with kind=street: municipalityIneCode from step 1.
provinceCodestringyesTwo-digit INE province code (e.g. 28 Madrid, 08 Barcelona).
qstringyesText to search: municipality name, or street name optionally followed by the number ("Colón, 5").
streetTypeCodestring–Only with kind=street, optional: street type code to narrow the search (CL, AV, PZ…).
NameTypeReqDescription
contractstringyes–
kindstringyes–
languagestringyes–
numberHintstring––
options–yes–

No examples provided.

Install

How do I install the HOUSINGFAX MCP server?

HOUSINGFAX is a hosted endpoint at https://housingfax.com/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 · housingfax.com

# add to Claude Code
claude mcp add --transport http com-housingfax-mcp 'https://housingfax.com/mcp'
Common questions

What is the HOUSINGFAX MCP server?

HOUSINGFAX is an MCP server listed in the public MCP registry as com.housingfax/mcp. Immediate home report for a building or flat in Spain: 22 checks from official public sources. This page covers its hosted endpoint (https://housingfax.com/mcp).

Is the HOUSINGFAX MCP server safe to use?

HOUSINGFAX scores 84 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 HOUSINGFAX MCP server expose?

HOUSINGFAX exposes 8 tools: get_products, list_checks, check_coverage, search_address, resolve_building, and 3 more. Their descriptions and schemas cost roughly 2,184 tokens of context every time the server is loaded.

Does the HOUSINGFAX MCP server require authentication?

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

Is the HOUSINGFAX MCP server still maintained?

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