Skip to main content
Glama
alirezas

iranketab-mcp

by alirezas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to iranketab-mcp

No user-submitted related servers found.

    Related Servers

    • reknihy-mcp

      birosrichard
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only search and retrieval of the public Reknihy.cz book catalog, including filtering, sorting, ISBN lookup, category browsing, and access to product details such as price, availability, and images.
      4
      ISC

    • kvartirabooks-mcp

      KathrynV
      A
      license
      A
      quality
      B
      maintenance
      Enables searching and retrieving book details from the Kvartirabooks store/library catalog, including availability for purchase or borrowing.
      2
      MIT

    • catalogue-api

      ibraheemmawwal
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides a read-only API over a book catalogue, offering tools to search books, retrieve book details and series, and inspect provenance and source agreement data.
      -

    • mcp-books

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching for books by title, author, or keyword, retrieving edition details by ISBN, and accessing author profiles and canonical work records through the Open Library API.
      128 npm
      MIT

    • gutenberg-mcp

      Awzy11
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables search and reading of Project Gutenberg books with tools for searching by title/author/subject and fetching word-range slices of book text.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action: search, name resolution, book-level details, edition-level data, comments, related books, and tag/person/publisher listings. The only potentially adjacent pair is book_details and book_editions, but their descriptions clearly separate summary-level from per-edition data.

    Naming Consistency4/5

    Names are uniformly lowercase snake_case and mostly resource-focused (book_details, book_editions, person_books, publisher_books). A few action-led names like search_books, browse_tag, and find_author_publisher_or_tag break the strict noun-first pattern, but the inconsistency is minor and does not hurt readability.

    Tool Count5/5

    Nine tools is an appropriate size for a bookstore catalogue server: search, discovery, and entity-specific lookups are each represented without redundant clutter. It stays comfortably within the ideal 3-15 tool range.

    Completeness4/5

    The tool surface covers the main discovery workflow: search and tag/person/publisher browsing, book-level details, edition comparison, and comments. Minor gaps exist, such as no search pagination, no direct list of all tags, and no separate author/publisher profile info, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources