Homechecker Guides MCP
Related Servers
Alternatives to Homechecker Guides MCP
No user-submitted related servers found.
Related Servers
- 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.8BSD 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.MIT
- FlicenseNot gradedqualityCmaintenanceProvides read-only MCP tools to query building construction approval lifecycle data, covering project discovery, bidding, contracts, drawing review, permits, and completion records.1-
- AlicenseBqualityDmaintenanceEnables users to search and navigate over 22,500 indexed sections across 16 Canadian building codes and user guides. It supports keyword searches, hierarchy navigation, and optional full-text extraction from user-provided PDF documents.74MIT
- AlicenseAqualityCmaintenanceProvides read access to community-written summaries, scores, and reviews of open-source repositories via the RepoCritics corpus. Enables search and retrieval of wiki pages, reviews, metadata, and AI reports for repositories.710 npmMIT
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.