Anahita MCP
OfficialRelated Servers
Alternatives to Anahita MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-capable clients to search team knowledge, browse an integration catalog, and get sourced product answers through deterministic, offline tools.37 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to search, navigate, and read the complete Hermes Agent documentation through a local SQLite FTS5 index, with tools for full-text search, page reading, and browsing documentation structure.MIT
- AlicenseAqualityBmaintenanceEnables agents to perform full-text search and read Hermes Agent documentation offline from a local cache, without scraping the site.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to access and read mdbook documentation, including structure, content, and search.4 npm3MIT

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- AlicenseAqualityCmaintenanceEnables MCP clients to search and read an offline, section-indexed mirror of Formidable Forms documentation, with category browsing, section-level reads, and incremental corpus updates.9MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct action/resource pairing: browse docs (list_docs), read a page (read_doc), search docs (search_docs), browse API services/routes (list_endpoints), read a route (read_endpoint), read a schema (read_shape). List vs. read vs. search are visibly different operations with no realistic misselection risk.
All names follow a strict verb_noun snake_case pattern (list_*, read_*, search_*), with singular nouns for single-item reads and plural for collections. The convention is predictable and readable throughout.
Six tools is well-scoped for a read-only documentation/API reference server — one tool per content type (docs, endpoints, shapes) each with browse/read/search coverage. Nothing feels padded or missing at the structural level.
The docs surface is complete (list, read, search), but the API surface lacks a dedicated search over routes or shapes and no standalone list_shapes, so shapes are only reachable via read_endpoint. Agents can work around this by browsing list_endpoints, so the gap is minor.