Skip to main content
Glama
riemannzeta

USPTO Patent MCP Server

by riemannzeta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to USPTO Patent MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      47 npm
      MIT

    • Priorbit

      Lawless-Inc
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and screen US intellectual property — granted patents with full claims, published applications, trademarks in every status, owners, inventors, USPTO documents, prosecution file wrappers, PTAB trials, and e-commerce product pages. Supports freedom-to-operate screenings, knockout trademark searches, and patent status/expiry/ownership checks through a single authenticated remote connection.
      1
      MIT

    • Patent by Ouroboros Apps

      LAHutchins91
      A
      license
      Not graded
      quality
      B
      maintenance
      Patent by Ouroboros Apps (https://ouroborosapps.com). USPTO patent search and prior art lookup: search public patent records, fetch a patent, list citations, and run a prior-art search. Not legal advice. USPTO only. Connect by pasting https://patent-mcp.vercel.app/mcp into Claude, Cursor, Grok, or ChatGPT developer mode (OAuth). Docs: https://ouroborosapps.com/docs/patent
      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.7/5.0

    Scored across 42 tools

    Disambiguation4/5

    Descriptions do real work separating near-neighbors: ppubs_search_patents vs ppubs_search_applications vs odp_search_applications, and tm_get_trademark vs tsdr_get_trademark_status explicitly say which to prefer. A few pairs remain easy to confuse (odp_get_application vs odp_get_application_metadata, get_status_code vs get_trademark_status_code, odp_get_documents vs tsdr_list_trademark_documents), but they are scoped to different resources or domains.

    Naming Consistency4/5

    The dominant pattern is domain-prefix + verb_noun (odp_, ppubs_, ptab_, tsdr_, tm_) with consistent verbs (get_, search_, list_, download_). The deviation is a set of bare get_/check_ tools (get_cpc_info, get_status_code, get_office_action_citations, get_office_action_rejections, check_api_status) that break the prefix convention even though some of them clearly belong to the ODP family.

    Tool Count3/5

    42 tools is heavy and above the comfortable band, though the server genuinely spans five distinct USPTO data domains (ODP applications, PPUBS patents, PTAB, TSDR/trademarks, classification lookups). Most tools cover a distinct endpoint, but redundancy (two application-search tools, application vs application-metadata, tm_get_trademark vs tsdr_get_trademark_status) means not every tool clearly earns its slot.

    Completeness4/5

    Coverage is broad: search/get/download across patents, applications, office actions, petitions, PTAB trials/appeals, trademarks, assignments, CPC and status codes, plus dataset and API-status tools. Minor gaps remain — patent assignment lookup is only by application number, PTAB document bodies lack a direct download path, and maintenance-fee/expiration lifecycle data is only partially covered via PTA.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources