Trademarks

io.github.pipeworx-iov0.1.2Updated Sep 30, 2026

Trademarks MCP — US trademark search + record lookup

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search US federal trademarks by mark text and look up records by serial or registration number.

What it does
Provides four trademark tools: search_trademarks finds registered and pending US marks by wordmark, with filters for international class and live/dead status; get_trademark_by_serial and get_trademark_by_registration return status, owner, dates, goods/services and classification; get_trademark_documents returns prosecution history such as office actions and responses. Search covers the full USPTO register and is keyless. The remote gateway endpoint also exposes shared Pipeworx meta-tools, including ask_pipeworx routing and remember/recall.
When to use it
Useful for brand-name clearance and knockout searches before adopting a name, for checking whether a proposed mark conflicts with existing US trademarks, and for pulling details or prosecution history on a known serial or registration number.
Requirements
Remote option: connect to the gateway URL over streamable HTTP; no account is needed for the first calls. Local option: run the npm package with npx, which requires Node.js. The three lookup-by-number and documents tools require a free USPTO API key from account.uspto.gov; search_trademarks is keyless.
Before you install
The remote endpoint lists roughly 30 shared Pipeworx meta-tools alongside the pack's own tools, which adds context and routes queries across the wider catalog; the initialize response states the exact scope. The USPTO API key is a credential to supply for the lookup and documents tools. Search results are informational and not legal advice.

Installation

In SourceWeft

  1. Open Trademarks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "trademarks": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/trademarks/mcp"
    }
  }
}

README

mcp-trademarks

Trademarks MCP — US trademark search + record lookup

Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.

Tools

ToolDescription
search_trademarksSearch US federal trademarks by mark text — the clearance/knockout-search path. Find registered and pending marks by wordmark without knowing a serial or registration number, then filter by international class and live/dead status to see which marks are actually enforceable. Covers the full USPTO register (the tmsearch.uspto.gov Elasticsearch backend that replaced TESS). Keyless. Use this to check whether a proposed brand name conflicts with existing US trademarks. Returns wordmark, serial and registration numbers, status, live flag, international classes, goods/services, owner, and filing dates. For a name-availability check, set live_only:true and pass the relevant class (e.g. 35 for advertising/business, 42 for software/SaaS, 9 for downloadable software).
get_trademark_by_serialLook up a US trademark by serial number. Returns status, owner, filing/registration dates, goods/services, and classification. Requires USPTO API key (free at account.uspto.gov).
get_trademark_by_registrationLook up a US trademark by registration number. Returns status, owner, mark text, goods/services, and classification. Requires USPTO API key.
get_trademark_documentsGet the prosecution history (office actions, responses, etc.) for a trademark by serial number. Requires USPTO API key.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "trademarks": {      "url": "https://gateway.pipeworx.io/trademarks/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/trademarks/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

json
{  "mcpServers": {    "pipeworx": {      "url": "https://gateway.pipeworx.io/mcp"    }  }}

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

bash
curl -X POST https://gateway.pipeworx.io/v1/tools/search_trademarks \  -H 'Content-Type: application/json' \  -d '{"query":"TenderBrief","live_only":true,"international_class":"35"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_trademarks. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

json
{  "mcpServers": {    "trademarks": {      "command": "npx",      "args": ["-y", "@pipeworx/mcp-trademarks"]    }  }}

Or run it directly to confirm it starts:

bash
npx -y @pipeworx/mcp-trademarks

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Trademarks data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Source: README.md at commit 7f81975

Tools

0
Tool metadata has not been indexed yet.

Version history

3
  1. v0.1.2LatestSep 27, 2026
  2. v0.1.1Sep 25, 2026
  3. v0.1.0Sep 16, 2026