Skip to main content
Glama
AiAgentKarl

patent-intelligence-mcp-server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to patent-intelligence-mcp-server

No user-submitted related servers found.

    Related Servers

    • patent-agent

      iStoryOfSpring
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables conversational patent data analysis through a set of tools for trend analysis, clustering, word cloud generation, and more. Allows natural language queries to explore patent datasets with structured results and visualizations.
      1
      AGPL 3.0

    • USPTO Patent MCP Server

      riemannzeta
      A
      license
      B
      quality
      A
      maintenance
      Provides access to USPTO patent and patent application data through multiple APIs, enabling search, retrieval, and analysis of patents, PTAB proceedings, and litigation data via natural language.
      61
      151 PyPI
      79
      MIT

    • mcp-patents

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving US patent records and published applications via keyword, assignee, inventor, or patent number, with full details such as claims, citations, and patent family.
      3 npm
      MIT

    • PatSnap MCP Server

      KunihiroS
      A
      license
      A
      quality
      D
      maintenance
      Enables collection of patent-related information from PatSnap's API for trend analysis and reporting, providing tools for patent trends, word clouds, innovation wheels, and identification of top inventors, assignees, and litigated patents.
      10
      8 npm
      7
      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

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. The overlapping tools like analyze_patent_landscape and get_patent_landscape are differentiated by structured analysis vs raw data. search_by_classification and search_by_cpc use different classification systems. No two tools perform the same function.

    Naming Consistency4/5

    Tool names follow a mostly consistent verb_noun pattern with underscores. Names like search_by_assignee and search_by_classification use a 'by' preposition, while search_patents and analyze_technology_trends do not, introducing minor inconsistency. Overall pattern is clear.

    Tool Count5/5

    15 tools is ideal for a patent intelligence server. The scope covers searching, analysis, comparison, and detailed patent retrieval without being overwhelming. Each tool adds value and the count matches typical user needs.

    Completeness4/5

    The tool set covers core patent intelligence operations: searching by various criteria, detailed patent data retrieval (claims, citations, family), landscape analysis, and portfolio comparison. Minor gaps like legal status or patent valuation are missing, but the domain is well-served overall.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources