Homechecker Guides MCP
Related Servers
Alternatives to Homechecker Guides MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that enables AI apps to list, search, and read a set of publicly published guides hosted as Google Docs, without authentication. It exposes list_guides, search_guides, and get_guide tools from a Cloudflare Worker endpoint, caching guide text for about an hour.MIT
- AlicenseAqualityBmaintenanceProvides construction-supervision tools for small-to-medium building projects, including stage guidance, inspection checklists, progress tracking, next-stage recommendations, and quotation analysis. It enables local, standards-based MCP interaction over stdio without third-party MCP SDKs.5MIT
- AlicenseAqualityBmaintenanceProvides read-only access to iFixit repair guides, device information, repairability scores, categories, search, media, and contributor profiles via MCP tools.81BSD Zero Clause
- AlicenseNot gradedqualityBmaintenanceProvides read-only search and context-pack creation over a local source library, letting AI assistants retrieve relevant excerpts and audit cited quotations.20MIT

XTend hosted MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables XTend developers and agents to search and retrieve canonical XTend documentation, recipes, and kit resources through read-only MCP tools, resources, and prompts served over stateless HTTP.Apache 2.0- FlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools to query building construction approval lifecycle data, covering project discovery, bidding, contracts, drawing review, permits, and completion records.1-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list_guides enumerates the catalogue, search_guides answers natural-language questions, get_guide retrieves a specific canonical guide by slug, and build_buyer_checklist assembles a deterministic checklist. There is no meaningful overlap or ambiguity between any pair of tools.
All four tools follow a consistent verb_noun pattern (list_guides, search_guides, get_guide, build_buyer_checklist) with descriptive action verbs and their target object. The naming is fully predictable and uniform.
Four tools is an appropriate, well-scoped set for a knowledge-documentation server covering catalogue browsing, search, retrieval, and synthesis. Each tool earns its place and there is no redundancy.
The surface covers the full lifecycle of interacting with the guide corpus: discover contents (list), query by question (search), retrieve details (get), and generate derived artifacts (build checklist). No obvious gaps for the stated purpose of a documentation/knowledge server.