A
licenseA
qualityC
maintenanceSearch and retrieve Devanagari Hindi shayari from an owner-authorized, provenance-tracked corpus, with audit and research-only inspection capabilities via stdio.
4
MIT
ramayana-mcp
by svenkatreddy
Related Servers
Alternatives to ramayana-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLM clients to perform read-only scripture study with verbatim, provenance-tagged verse lookups and complete-or-fail concordance across Greek NT, Hebrew OT, and Septuagint editions.MIT
- AlicenseNot gradedqualityCmaintenanceSemantic search and comparative retrieval over a multi-tradition corpus of sacred and foundational texts, exposed as an MCP server.MIT
- AlicenseNot gradedqualityAmaintenanceProvides source-grounded Christian research material with exact passages, provenance, and stable citations via a REST API.MIT
- AlicenseAqualityCmaintenanceEnables source-labelled Christian Scripture evidence lookup and comparison, including BSB/WEB verse retrieval, passage context, cross-references, keyword search, and topic guides, through a hosted read-only MCP server.11MIT
- AlicenseNot gradedqualityAmaintenanceEnables users to look up, search, decode, compare, and explore contemporary internet English, texting shorthand, regional expressions, and clearly labeled non-graphic adult vocabulary through a remote, zero-auth Streamable HTTP endpoint.MIT
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool targets a clearly distinct granularity of the same corpus: listing kandas, fetching one verse, fetching one sarga, full-text search, and a deterministic daily pick. verse_of_the_day vs get_verse could superficially touch the same data, but the descriptions make the boundaries obvious.
Naming Consistency4/5
Four tools follow a clean verb_noun pattern (list_kandas, get_verse, get_sarga, search_verses) with consistent snake_case. verse_of_the_day breaks the pattern as a bare noun phrase with no verb, though it is still readable and unambiguous.
Tool Count5/5
Five tools is well-scoped for a scripture-browsing server: structure listing, two retrieval granularities, search, and a novelty feature. No tool feels redundant or padded.
Completeness4/5
Core lifecycle for corpus navigation is covered: browse structure, fetch verse/chapter, search, and a daily highlight. A gap remains at the kanda level — there is no way to list the sargas belonging to a kanda, so agents must guess chapter numbers before calling get_sarga.
Maintenance
ActivityMaintained
ResponsivenessNo issues