Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trademarks

NPM · @PIPEWORX/MCP-TRADEMARKS · 2 COMPONENTS

Trademarks MCP — US trademark search + record lookup

+3 this week 82 Trust /100

Last scanned (7 hours ago)

Scores higher than 72% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-trademarks). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-trademarks@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-trademarks
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-trademarks/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3560513549
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:89515f0b84e63256ebfcc9d8eb4e0093e283a06711bec592fb0b63ad0f27d44fe586496533724f668aee8a49906b6ee1d34a850a247416878e2f0dd87

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~774 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_trademark_by_registration ~132

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.

NameTypeReqDescription
api_keystring–Optional USPTO TSDR API key. Omit for the keyless register record.
registration_numberstringyesUSPTO registration number (e.g., "4872338")

No output schema declared.

No examples provided.

get_trademark_by_serial ~144

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.

NameTypeReqDescription
api_keystring–Optional USPTO TSDR API key (free at account.uspto.gov/api-manager). Omit for the keyless register record.
serial_numberstringyesUSPTO serial number (e.g., "79153306")

No output schema declared.

No examples provided.

get_trademark_documents ~59

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

NameTypeReqDescription
api_keystring–USPTO API key
serial_numberstringyesUSPTO serial number

No output schema declared.

No examples provided.

search_trademarks ~439

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).

NameTypeReqDescription
international_classstring–Optional Nice class filter. Accepts "35", 35, "IC 035", or "035". Common: 9 (software), 35 (advertising/business/retail), 42 (SaaS/tech services).
limitnumber–Results per page, 1-50 (default 20).
live_onlyboolean–If true, return only live marks (registered or pending) — the set that can actually block a new application. Default false (includes dead/abandoned/cancelled).
offsetnumber–Pagination offset (default 0).
ownerstring–Owner-name filter (e.g. "Nike", "Mondelez"). Pass owner alone (no query) to list that owner's whole portfolio.
querystring–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…

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-trademarks

# add to Claude Code
claude mcp add pipeworx-io-trademarks -- npx -y @pipeworx/mcp-trademarks
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.