# Ttab (npm · @pipeworx/mcp-ttab)

TTAB (Trademark Trial and Appeal Board) MCP — TTABVUE inquiry system

- Trust score: 78/100 (medium)
- Change this week: 0
- 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-ttab/ttab-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ttab/ttab-mcp)
- npm · `@pipeworx/mcp-ttab`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ttab/pipeworx-mcp-ttab.md), [page](https://verifymcp.io/servers/pipeworx-io-ttab/pipeworx-mcp-ttab)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ttab`
- 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-ttab).
  - 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**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 882 tokens (~294/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

Ttab runs locally as an npm package, launched with npx -y @pipeworx/mcp-ttab. 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-ttab -- npx -y @pipeworx/mcp-ttab
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `ttab_search` (~382 tokens)

Searches USPTO Trademark Trial and Appeal Board (TTAB) proceedings — trademark oppositions, cancellation petitions, extensions of time to oppose, and ex parte appeals — by party name, mark text, correspondent law firm, or application/registration number. Answers "is anyone opposing this trademark", "who has petitioned to cancel this registration", "which brands does this company fight", "what TTAB disputes involve this mark". Each result carries the board proceeding number, proceeding type (opposition, cancellation, extension of time, ex parte appeal), filing date, and both sides — defendant and plaintiff, each with their marks and serial/registration numbers. Sourced live from USPTO TTABVUE.

Input parameters:

- `correspondent` (string): Correspondent (law firm or attorney of record) name.
- `limit` (number): Max proceedings to return from the page, 1-25. Default 25.
- `mark` (string): Trademark text being fought over, e.g. "JUST DO IT".
- `match_mode` (string): How party/mark/correspondent text is matched. Default contains.
- `other_party` (string): Second party name — use with `party` to find proceedings between two specific companies.
- `page` (number): 1-based page; TTABVUE returns 25 proceedings per page, newest first.
- `party` (string): Party name as filed, e.g. "Nike, Inc." or just "Nike". Matches either side of the proceeding.
- `query` (string): All these words anywhere in the record — proceeding number, application/registration number, parties, or marks.
- `serial_or_registration_number` (string): Application serial number, registration number, or expungement/reexamination number the proceeding is about.
- `status` (string): Proceeding status filter. Default all.

### `ttab_proceeding` (~220 tokens)

Returns one USPTO TTAB proceeding in full: its type (opposition, cancellation, extension of time to oppose, ex parte appeal), status and status date, filing date, interlocutory attorney and paralegal, both parties with their correspondence addresses and every pleaded mark (serial number, registration number, application status), and the complete prosecution history — every docket entry with its date, text, and any due date. Answers "what happened in TTAB proceeding 91308065", "is this opposition still pending", "what is the answer deadline", "which marks were pleaded". Sourced live from USPTO TTABVUE.

Input parameters:

- `proceeding_number` (string, required): 8-digit board proceeding number (91xxxxxx opposition, 92xxxxxx cancellation), or the application serial number for an extension of time / ex parte appeal.
- `type` (string): Proceeding type. Only needed to disambiguate an extension of time (EXT) from an ex parte appeal (EXA), which share the application serial-number space.

### `ttab_party_history` (~227 tokens)

Profiles one company or person across USPTO TTAB proceedings: how many times they appear as plaintiff (the one opposing or petitioning to cancel) versus defendant (the one being opposed), a breakdown by proceeding type, every name spelling they have been filed under, and the proceedings themselves. Answers "how often does this company oppose other trademarks", "is this brand an aggressive TTAB litigant", "who has this company been in TTAB disputes with". Reads several result pages. Sourced live from USPTO TTABVUE.

Input parameters:

- `limit` (number): Max proceedings to return in the list, up to 125. Default 50.
- `match_mode` (string): How the party name is matched. Default contains.
- `max_pages` (number): How many 25-row pages to read, 1-5. Default 2.
- `party` (string, required): Party name as filed, e.g. "Monster Energy Company". A distinctive word matches more reliably than a full legal name.
- `status` (string): Proceeding status filter. Default all.

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Ttab MCP server?

Ttab is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ttab. TTAB (Trademark Trial and Appeal Board) MCP, TTABVUE inquiry system. This page covers its npm package (@pipeworx/mcp-ttab).

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

Ttab scores 78 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 Ttab MCP server expose?

Ttab exposes 3 tools: ttab_search, ttab_proceeding, ttab_party_history. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.

### Is the Ttab MCP server still maintained?

Ttab 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 Ttab MCP server under?

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

## Links

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