Skip to main content
Glama
aa0101181514

tw-patent-mcp

by aa0101181514
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to tw-patent-mcp

No user-submitted related servers found.

    Related Servers

    • io.github.xhighhongo41/patent

      xhighhongo41
      A
      license
      Not graded
      quality
      A
      maintenance
      Fetches and normalizes public patent data from EPO OPS and Google Patents, providing search, bibliographic records, claims, legal status, and patent family information for prior-art exploration.
      1,108 PyPI
      Apache 2.0

    • patentmcp

      Raw1mage
      A
      license
      Not graded
      quality
      D
      maintenance
      Patent data retrieval and file delivery engine that searches multiple patent databases via a unified API and delivers documents as verifiable artifacts.
      2
      MIT

    • patent-api

      describug
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Desktop and Claude Code to query Korean KIPRIS Plus and European EPO OPS patent data for bibliographic details, family members, legal status, claims, descriptions, abstracts, and search results using each user's own free API keys.
      MIT

    • Patent Big Data MCP Server

      handaas
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables comprehensive patent information queries and analytics including fuzzy company search, patent search by various criteria (name, application number, applicant), and statistical analysis of patent portfolios including status distribution, application trends, and patent type classification.
      30
      -
    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

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    The set is clearly split into Taiwan GPSS and EPO OPS namespaces, and most tools target distinct operations such as search, single-record retrieval, legal status, family, fulltext, images, and PDF download. Minor overlap exists between gpss_search/ops_search for Taiwan publications and between ops_biblio/ops_register for EP bibliographic data, but the descriptions generally make the intended use clear.

    Naming Consistency4/5

    All names use a consistent prefix plus snake_case convention (gpss_* and ops_*), which makes the tool family easy to identify. However, the suffixes mix verb-style and noun-style names (e.g. ops_search vs ops_biblio), so it is not a uniform verb_noun pattern throughout.

    Tool Count5/5

    With 12 tools, the server is well scoped for a patent search and retrieval system covering two data sources. Each tool has a distinct role, including the helper gpss_build_url and the paired ops_images/ops_download_pdf workflow.

    Completeness5/5

    The surface covers the main patent research lifecycle: searching, browsing codes/fields, retrieving single records, bibliographic data, legal status, families, fulltext, register data, image lists, and PDF downloads. There are no obvious dead ends for the stated Taiwan GPSS plus EPO OPS retrieval purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources