humanedgepress-mcp-server
OfficialRelated Servers
Alternatives to humanedgepress-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to search a curated catalog of practical AI books and retrieve book records, topics, reading paths, free chapters, glossary definitions, and verified claim citations. It also supports checking claims and generating citations from the catalog’s published free material.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and interact with Shopify store data via the Storefront API, including products, collections, carts, and customer information.9-
- AlicenseAqualityBmaintenanceEnables AI assistants to search and recommend Christian streetwear, faith apparel, trucker hats, and clogs, while providing theological insights, sizing guides, gift suggestions, and direct 1-click Shopify checkout links.9325 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to act as a Shopify shopping assistant and catalog auditor by answering from the live storefront: filtered product search, deals, comparisons, recommendations, policy and page lookups, verified cart permalinks, and a whole-catalog listing-quality audit. All operations are read-only, so nothing is ever written to the store.13MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to search and explore a bookstore catalog including books, authors, categories, stock, prices, and recommendations through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and read a Dutch web shop's public product catalog, variants, CMS pages, blog posts, merchant profile, and contact details through read-only MCP tools.MIT
TDQS
Scored across 15 tools
Several tool pairs overlap: `search_human_edge_books`/`search` and `search_blogs_and_essays`/`search` both retrieve content, while `get_book_details_and_parent_prompts`, `read_blog_or_essay`, and `fetch` are three separate retrieval paths that could easily be confused. The descriptive text does help (search/fetch is clearly a generic delegation layer), but an agent must still decide between a targeted tool and the unified one for nearly every content request.
The set is dominated by a predictable verb_noun snake_case pattern (search_human_edge_books, get_book_details_and_parent_prompts, generate_direct_checkout_link, list_book_series_and_collections). The only deviations are the bare-verb `search` and `fetch` primitives, which are minor and arguably intentional as a generic fallback namespace.
At 15 tools the surface sits at the upper edge of a comfortable range for a single-publisher commerce/content server, and each tool maps to a recognizable job. However, the two generic primitives plus multiple parallel search/detail tools mean a couple of entries are redundant rather than earning their place.
Coverage is broad: discovery, book details, blog reading, developmental science, playbooks, recommendations, series browsing, age roadmap, checkout link generation, FAQ, and mission all have tools. Minor gaps remain around post-purchase concerns such as order status or cart modification, and there is no direct 'list all books' beyond series traversal, but agents can work around both.