Trademarks

io.github.pipeworx-iov0.1.2更新於 Sep 30, 2026

Trademarks MCP — US trademark search + record lookup

已驗證Streamable HTTP可網頁執行Web Search & ScrapingBusiness & Commerce

概覽

AI 產生的概覽

讓助理依商標文字檢索美國聯邦商標，並依序號或註冊號查詢紀錄。

功能
提供四個商標工具：search_trademarks 依文字商標查找已註冊與審查中的美國商標，可依國際類別與有效/失效狀態篩選；get_trademark_by_serial 與 get_trademark_by_registration 回傳狀態、持有人、日期、商品/服務及分類；get_trademark_documents 回傳審查歷程，例如審查意見與答辯。檢索涵蓋完整 USPTO 註冊資料庫且不需金鑰。遠端閘道端點還會額外列出 Pipeworx 共用中繼工具，包括 ask_pipeworx 路由與 remember/recall。
適用情境
適合在採用某個名稱前做品牌清查與初步排查，檢查擬用商標是否與現有美國商標衝突，以及依已知序號或註冊號取得詳細資料或審查歷程。
執行需求
遠端方式：透過 streamable HTTP 連線閘道網址，最初幾次呼叫不需帳號。本機方式：以 npx 執行該 npm 套件，需要 Node.js。依編號查詢與文件這三個工具需要 account.uspto.gov 提供的免費 USPTO API 金鑰；search_trademarks 不需金鑰。
安裝前請注意
遠端端點除本套件工具外還會列出約 30 個 Pipeworx 共用中繼工具，會增加上下文，並把查詢路由到更廣的目錄；initialize 回應會說明確切範圍。USPTO API 金鑰是查詢與文件工具需要提供的憑證。檢索結果僅供參考，不構成法律意見。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Trademarks，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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

來源：README.md，提交 7f81975

工具

0
工具後設資料尚未被收錄。

版本歷史

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