Ttab
NPM · @PIPEWORX/MCP-TTAB · 2 COMPONENTS
TTAB (Trademark Trial and Appeal Board) MCP — TTABVUE inquiry system
Available components
Last scanned (4 hours ago)
Scores higher than 58% of npm servers
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-ttab). 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 Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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-ttab@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-ttab |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ttab/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560581473 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0a834b84c9a5dc034d401e8bbdbcac886409cd6aafcd21d94f2ee18f9ab4fbe06d1d5dad394a50db510ba98a45f01044a3cc1f7ddaf7a161086fbaac7 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ttab_party_history ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
ttab_proceeding ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| proceeding_number | string | yes | 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. |
No output schema declared.
No examples provided.
ttab_search ~382
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-ttab
claude mcp add pipeworx-io-ttab -- npx -y @pipeworx/mcp-ttab
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.