Trademarks logo

Trademarks

Search US federal trademarks by mark text or retrieve USPTO records, classifications, and prosecution documents over MCP.

Install Trademarks

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "trademarks": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-trademarks"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 4 tools correctly (5d ago).

Overview

Trademarks MCP server searches US federal trademark records and retrieves detailed USPTO data through MCP tools. Use mark-text searches for clearance checks, with optional filters for international class and live status, or look up records by serial or registration number. Record and document lookups require a USPTO API key, while mark searches are keyless. Connect through the Pipeworx gateway or run the package locally as a stdio MCP server.

Use cases

  • Search proposed brand names for potentially conflicting US marks
  • Filter trademark results by international class and live status
  • Retrieve USPTO records by serial or registration number
  • Review office actions and responses in a trademark prosecution history

Key features

  • Mark-text search across US federal trademarks
  • Filtering by international class and live status
  • Lookup by USPTO serial number
  • Lookup by USPTO registration number
  • Prosecution-history document retrieval
  • Gateway, HTTP, and local stdio access

Tools4

What Trademarks lets your agent do. Expand a tool for its parameters.

Verified live~726 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

What it can do

From the 4 tools this server returned when we ran it.

Handles credentials · 3Read-only tools · 4
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age184 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-trademarks (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads464Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Trademarks works

What Trademarks MCP server does

The Trademarks MCP server provides agent access to US federal trademark search and record data. It is suited to preliminary brand-name research, record verification, and inspection of a trademark’s prosecution history. Search results can include the wordmark, serial and registration numbers, status, live flag, international classes, goods and services, owner, and filing dates.

The mark search is intended for clearance or knockout searches. An agent can search by wordmark without knowing a USPTO serial or registration number, then narrow results by international class and whether the mark is live. This can help identify potentially relevant registered or pending marks before deeper legal review.

How it works

The gateway exposes the pack at https://gateway.pipeworx.io/trademarks/mcp. A client can use that URL as an MCP connection, or connect to the full Pipeworx gateway at https://gateway.pipeworx.io/mcp. The scoped endpoint also exposes shared Pipeworx meta-tools, so its tools/list response contains more tools than the four trademark-specific tools. The standalone package exposes only the trademark tools.

A local installation communicates over stdin and stdout. The gateway also provides HTTP tool endpoints, including POST /v1/tools/search_trademarks, for clients or applications that do not use MCP directly. The gateway can route natural-language requests through ask_pipeworx and select a suitable tool, but direct tool calls are available as well.

Setup and configuration

For a remote MCP connection, add the gateway URL to an MCP client configuration. No account is needed for the first gateway calls described in the documentation.

For a local connection, run the package with npx -y @pipeworx/mcp-trademarks and configure the client to launch that command. This local mode does not use a Pipeworx account or gateway round trip. It serves the same trademark-specific tools over stdio.

The search tool is keyless. get_trademark_by_serial, get_trademark_by_registration, and get_trademark_documents require a USPTO API key, available through account.uspto.gov.

Tools and capabilities

  • search_trademarks searches by mark text and can filter by live status and international class. Classes mentioned in the documentation include 35 for advertising and business, 42 for software and SaaS, and 9 for downloadable software.
  • get_trademark_by_serial retrieves a record using a US trademark serial number, including status, owner, dates, goods and services, and classification.
  • get_trademark_by_registration retrieves a record using its registration number, including status, owner, mark text, goods and services, and classification.
  • get_trademark_documents returns prosecution-history materials such as office actions and responses for a serial number.

Limitations and notes

A live-only result filter identifies records marked live in the search data, but the tool is not described as a substitute for legal clearance work.

The gateway’s pack endpoint currently adds shared Pipeworx tools to the advertised trademark tools, and its exact scope may change. Use the standalone package when an agent should see only the four trademark tools. Serial, registration, and document lookups depend on USPTO API access, while the mark-text search does not require that key.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Trademarks

Trademarks is an MCP server that connects AI agents to US federal trademark data from USPTO search and record systems. Its main tools search marks by text, retrieve records by serial or registration number, and fetch prosecution documents such as office actions and responses. Mark-text search is keyless; other lookups require a USPTO API key.

Install it locally with `npx -y @pipeworx/mcp-trademarks` and configure an MCP client to launch that command. You can instead connect to `https://gateway.pipeworx.io/trademarks/mcp` as a remote MCP server.

Yes, Trademarks works with Cursor through the Pipeworx MCP endpoint. Add `https://gateway.pipeworx.io/trademarks/mcp` to Cursor’s MCP configuration, or run the package locally over stdio.

Only some lookups require a USPTO API key. Serial-number, registration-number, and prosecution-document tools require a key from account.uspto.gov; the mark-text search is described as keyless.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTrademarks AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/trademarks?style=directory)](https://allmcps.com/mcp/trademarks)
HTML Embed
<a href="https://allmcps.com/mcp/trademarks"><img src="https://allmcps.com/api/badge/trademarks?style=directory" alt="Trademarks on AllMCPs" /></a>