# Trademarks (npm · @pipeworx/mcp-trademarks)

Trademarks MCP — US trademark search + record lookup

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-trademarks/trademarks-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-trademarks/trademarks-mcp)
- npm · `@pipeworx/mcp-trademarks`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks.md), [page](https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-trademarks`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-trademarks).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 826 tokens (~206/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Trademarks MCP server?

Trademarks runs locally as an npm package, launched with npx -y @pipeworx/mcp-trademarks. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-trademarks -- npx -y @pipeworx/mcp-trademarks
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-trademarks -- npx -y @pipeworx/mcp-trademarks
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-trademarks": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-trademarks"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-trademarks --command npx --arg -y --arg @pipeworx/mcp-trademarks
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-trademarks:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-trademarks"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-trademarks": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-trademarks"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-trademarks -t stdio -c npx -a -y @pipeworx/mcp-trademarks
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `search_trademarks` (~439 tokens)

Search 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. Also finds every mark held by a company: pass owner (e.g. "Nike") to list the trademark portfolio of a brand owner. Covers the full USPTO register (the Trademark Search system 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, owners of record with role and entity type, attorney of record, filing dates, and data_as_of (when USPTO last loaded each record). 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).

Input parameters:

- `international_class` (string): Optional Nice class filter. Accepts "35", 35, "IC 035", or "035". Common: 9 (software), 35 (advertising/business/retail), 42 (SaaS/tech services).
- `limit` (number): Results per page, 1-50 (default 20).
- `live_only` (boolean): If true, return only live marks (registered or pending) — the set that can actually block a new application. Default false (includes dead/abandoned/cancelled).
- `offset` (number): Pagination offset (default 0).
- `owner` (string): Owner-name filter (e.g. "Nike", "Mondelez"). Pass owner alone (no query) to list that owner's whole portfolio.
- `query` (string): Mark text to screen (e.g. "TenderBrief"). Matches the wordmark field. Required unless owner is given. Advanced: pass fielded Lucene (e.g. 'wordmark:apple AND ownerName:"Apple Inc"') and it is used ve…

### `get_trademark_by_serial` (~144 tokens)

Look up one US trademark by its 8-digit serial (application) number: mark text, current status and live flag, registration number, owners of record, attorney of record, filing/registration/publication/renewal dates, filing basis, international classes and goods/services, with data_as_of. Keyless. Optional api_key switches to USPTO's TSDR case-status record instead.

Input parameters:

- `api_key` (string): Optional USPTO TSDR API key (free at account.uspto.gov/api-manager). Omit for the keyless register record.
- `serial_number` (string, required): USPTO serial number (e.g., "79153306")

### `get_trademark_by_registration` (~132 tokens)

Look up one US trademark by its registration number (e.g. "4872338"): mark text, serial number, current status and live flag, owners of record, attorney of record, registration/renewal/cancellation dates, international classes and goods/services, with data_as_of. Keyless. Optional api_key switches to USPTO's TSDR case-status record instead.

Input parameters:

- `api_key` (string): Optional USPTO TSDR API key. Omit for the keyless register record.
- `registration_number` (string, required): USPTO registration number (e.g., "4872338")

### `get_trademark_documents` (~59 tokens)

Get the prosecution history (office actions, responses, etc.) for a trademark by serial number. Requires USPTO API key.

Input parameters:

- `api_key` (string): USPTO API key
- `serial_number` (string, required): USPTO serial number

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### What is the Trademarks MCP server?

Trademarks is an MCP server listed in the public MCP registry as io.github.pipeworx-io/trademarks. Trademarks MCP, US trademark search + record lookup. This page covers its npm package (@pipeworx/mcp-trademarks).

### Is the Trademarks MCP server safe to use?

Trademarks scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Trademarks MCP server expose?

Trademarks exposes 4 tools: search_trademarks, get_trademark_by_serial, get_trademark_by_registration, get_trademark_documents. Their descriptions and schemas cost roughly 774 tokens of context every time the server is loaded.

### Is the Trademarks MCP server still maintained?

Trademarks is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Trademarks MCP server under?

Trademarks declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Trademarks MCP server?

VerifyMCP ran 16 checks on Trademarks, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-trademarks
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-trademarks
- Repository: https://github.com/pipeworx-io/mcp-trademarks
- Website: https://pipeworx.io/packs/trademarks
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-trademarks/pipeworx-mcp-trademarks