hadathna-mcp
Related Servers
Alternatives to hadathna-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables fetching and searching canonical hadith texts (Arabic and English) with cross-references and citation-safe URLs for assistants, built on FastMCP.3GPL 3.0
- 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.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for retrieving hadith text and metadata from auditable sources, providing exact references, Arabic text, English translations, and source-attributed grading.MIT
- 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
- AlicenseAqualityBmaintenanceRead-only MCP server for searching and citing Quran, Hadith, Tafsir and dua sources, with Arabic text, translations, hadith grades and exact references.7MIT
- 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
TDQS
Scored across 6 tools
Search vs. fetch pairs are clearly separated (search_hadiths/get_hadith, search_narrators/get_narrator), and list_topics is unambiguous. The one soft boundary is get_narrator vs get_narrator_biography: get_narrator already reports rank/reliability, while the biography tool covers classical-source material on 'life or reliability', so an agent may hesitate between them, though the descriptions give a usable rule of thumb.
Every tool follows a clean verb_noun snake_case pattern: search_*, get_*, list_*. The singular get_hadith vs plural search_hadiths is a deliberate semantic distinction (fetch one number vs. search many), not an inconsistency.
Six tools is a tight, well-scoped set for a single-collection hadith corpus: two search tools, two fetch tools, a biography lookup, and a topic directory. It is on the lean side — nothing for browsing books/chapters directly — but each tool clearly earns its place.
Core lifecycles are covered: discover via search (hadith, narrator, topic), then retrieve full entries with sanad/matn/chains and narrator details. The notable gap is that topics get a list_topics discovery helper for exact-name matching, but 'book' is also a search filter with no equivalent listing tool, so agents must guess book names; a book/chapter listing would close the loop.