Skip to main content
Glama
elibonk

MyDramaList MCP

by elibonk

Related Servers

Alternatives to MyDramaList MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching ClinicalTrials.gov studies, fetching full protocol records and posted results, discovering valid API field names and values, and matching patient demographics and conditions to candidate recruiting trials. Runs over STDIO or Streamable HTTP as a public, read-only service requiring no authentication.
      1,881 npm
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude and Cursor to read timelines, search statuses, and look up users or conversations, plus optionally post, delete, favorite, and follow with explicit confirmation. It supports both local stdio launches and remote HTTP hosting with per-user authorization.
      15
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching the ClinicalTrials.gov registry, retrieving full study records and posted results, discovering valid field names and values, and matching patient demographics to candidate recruiting trials. Runs over STDIO or Streamable HTTP with no authentication required.
      1,881 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing a personal media collection of films, series, animation, books, and games via MCP, including adding, searching, filtering, updating, deleting, and retrieving statistics.
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides access to The Movie Database (TMDB) API for searching movies, retrieving movie details, cast information, and browsing current, upcoming, popular, and top-rated films, as well as searching for actors and directors.
      76 npm
      -

    TDQS

    C2.8/5.0

    Scored across 89 tools

    Disambiguation4/5

    Most tools have distinct resource+action semantics (e.g. mdl_reviews_submit vs mdl_reviews_edit vs mdl_reviews_delete), and namespaces like titles_/users_/custom_lists_ keep domains separated. A few boundaries are fuzzy, notably mdl_comments_like vs mdl_feeds_like vs mdl_articles_like (like operations across content types) and the get/fetch pairs (mdl_feeds_get vs mdl_feeds_fetch, mdl_watchlist_fetch vs mdl_watchlist_fetch_page), but descriptions mostly disambiguate.

    Naming Consistency5/5

    Every tool follows the same namespace_verb_noun convention (mdl_<domain>_<action>), with consistent snake_case and a predictable verb vocabulary (get, list, fetch, create, edit, delete, like, add, remove). No camelCase mixing or irregular verb styles across all 89 tools.

    Tool Count2/5

    89 tools is far beyond the 15-25 range that keeps a surface navigable for an agent. While the server covers a rich multi-domain API (titles, users, reviews, comments, lists, feeds, notifications, account), the sheer count creates selection and context-loading overhead that undermines usability.

    Completeness5/5

    Coverage is exceptionally thorough: full CRUD for reviews, comments, custom lists, feeds, and watchlist; read paths for titles, users, explore, articles, groups, awards, calendar, leaderboard, plus account/profile management and auth-aware operations. Almost no obvious domain gap remains, with server_status and capabilities providing introspection.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues