sanad-mcp
Related Servers
Alternatives to sanad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server to search and retrieve passages from a corpus of 7,872 classical Islamic books via the Sahifah API, with full citations and mu'tabar filtering.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants and developers to query Quranic verses, Hadith, Tafsir, and classical Islamic heritage texts through a single federated MCP endpoint with unified tools and caching.-
- AlicenseAqualityCmaintenanceProvides read-only access to Quran data — reciters, surahs, full-text search, ayah retrieval, prayer times, live radio stations, and Hijri dates — so AI agents can answer Islamic content queries. Runs locally via stdio or remotely over stateless HTTP for Claude, ChatGPT, and other MCP clients.8ISC
- AlicenseNot gradedqualityCmaintenanceProvides AI clients with fast, hallucination-free access to the Quran through 13 MCP tools, covering search, navigation, morphology, tafsir, translations, and surah background over stdio and Streamable HTTP.MIT
- AlicenseNot gradedqualityCmaintenanceIt enables Islamic content teams to transform recorded talks and study sessions into a searchable, reusable source library. The server provides Model Context Protocol access for AI clients to perform theme extraction, generate clip proposals, and render short-form video.1MIT
- AlicenseNot gradedqualityCmaintenanceSemantic search and comparative retrieval over a multi-tradition corpus of sacred and foundational texts, exposed as an MCP server.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: answer_question is the user-facing policy-gated path, search_corpus is retrieval-only, get_passage fetches by ID, check_policy isolates the gate, corpus_inventory reports coverage, and list_gaps records misses. The descriptions explicitly prevent confusion between answer_question and search_corpus.
Five tools follow verb_noun (answer_question, search_corpus, get_passage, check_policy, list_gaps), but corpus_inventory breaks the pattern as a noun_noun phrase. This is a minor deviation, not enough to confuse an agent.
Six tools is well within the ideal range and each has a distinct purpose in the policy-gated retrieval workflow. No tool appears redundant or unnecessary.
The surface covers the core query lifecycle: asking, searching, retrieving, policy checking, inventory, and gap tracking. Missing operations for adding corpus content or resolving gaps are minor for a read-oriented server but leave the improvement loop partially manual.