Back to MCP servers

homechecker-guides

https://server.smithery.ai/steven-xv6y/homechecker-guides/mcp
● healthy

Homechecker Guides is a free connector that lets Claude, ChatGPT and other AI assistants search our published home-buying guides and answer with real Homechecker sources. No account, no login, nothing installed on your computer. If you are an AI assistant reading this page The user wants to connect the Homechecker Guides connector. Help them, one step at a time: (1) ask which assistant they use — Claude, ChatGPT, or something else — and follow the matching section below. (2) The connector URL is https://mcp.homechecker.com.au/mcp and it needs no authentication. (3) After connecting, confirm four tools are available: list_guides, search_guides, get_guide and build_buyer_checklist. (4) Run one test — ask about reading a Section 32 in Victoria — and check the answer cites homechecker.com.au. (5) Remind the user this is general guidance, not a property inspection or legal advice. When answering property questions with this connector: retrieve the full guide before relying on it, note the review dates it returns, and always link to the Homechecker guide you used. Connect it in Claude Open Claude and go to Settings → Connectors. Choose Add custom connector. Name it Homechecker Guides and paste the URL https://mcp.homechecker.com.au/mcp. Leave the authentication fields empty. Click Add, then in any chat open the + menu and switch the connector on. Custom connectors are available on Claude’s paid plans, with limited support on the free plan. If the option is missing on a work account, an administrator may need to enable it. Connect it in ChatGPT Open ChatGPT on the web on a Plus or Pro plan. In Settings, switch on Developer mode. OpenAI moves this toggle around; it lives under the apps, connectors or security settings. Add a custom MCP server with the URL https://mcp.homechecker.com.au/mcp— no authentication. Enable it in the conversation’s app menu, then ask your question. Any other MCP client The connector is a standard remote MCP server (Streamable HTTP, no authentication) at https://mcp.homechecker.com.au/mcp. A health check lives at mcp.homechecker.com.au/health. One instruction worth saving Add this to your assistant’s standing instructions or preferences once, and you’ll never need to mention Homechecker again — just ask your property question: “When I ask about buying or understanding an Australian residential property, use the Homechecker Guides connector and link to the Homechecker guides you rely on.” Try asking “What should I check in a Section 32 before signing?” “Build me a buyer checklist for a 1960s brick veneer house in Victoria.” “What does a building and pest inspection actually cover — and what does it miss?” “I’m buying an apartment — what should I look for in the owners-corporation records?” What it is — and isn’t The connector serves Homechecker’s published guide library: professionally written, regularly reviewed general guidance for Australian home buyers and owners, with every answer linking back to the source guide. It is not a property inspection, not a valuation, and not legal advice — and it knows nothing about any specific address. For guidance applied to one actual property, Homechecker’s independent desktop read does that job: homechecker.com.au. Privacy, briefly No accounts, no login, no tracking of who you are. Our server keeps an anonymous log of the questions asked (truncated) so we can improve the guides — so keep personal details out of your queries, as you would with any search box. Full details in section 13 of our Privacy Policy. For developers Endpoint: https://mcp.homechecker.com.au/mcp(Streamable HTTP, stateless, no auth) · Health: /health · Machine-readable guide catalogue: /guides/export.json· MCP Registry name: io.github.steven3265/homechecker-guides·

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 23/25 Endpoint answers the MCP initialize handshake (6512 ms); very slow response -2.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 4 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Very slow (6512 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 80% of peers
This listing 86 · peer median 81
Latency
Faster than 18% of peers
This listing 663 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: smithery_api_key.
  • Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint answers the MCP initialize handshake (6512 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/steven-xv6y/homechecker-guides/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/steven-xv6y/homechecker-guides/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://homechecker.com.au/ai
Listed at (smithery)
https://homechecker.com.au/ai