@pipeworx/mcp-ttab 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,6 @@
1
+ {
2
+ "staged_at": "2026-09-23T21:46:57.313Z",
3
+ "publisher_blob": "da6994091dc9dcc6a7433084251ca4bbd58b4bed",
4
+ "publisher_commit": "1c417b2cfcdac06e2d9210e869265722ef013f20",
5
+ "note": "Written by scripts/publish-pack.sh as its LAST step. Its presence is the ONLY thing that lets stage-unpublished-packs.sh skip this pack. Deleting this dir is the correct way to force a rebuild."
6
+ }
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Mojibake Inc.
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md ADDED
@@ -0,0 +1,165 @@
1
+ # @pipeworx/ttab
2
+
3
+ Trademark disputes before the USPTO Trademark Trial and Appeal Board —
4
+ oppositions, cancellation petitions, extensions of time to oppose, and ex parte
5
+ appeals, with both parties, the marks at issue, and the full docket.
6
+
7
+ Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1669+ live data sources.
8
+
9
+ ## Tools
10
+
11
+ - `ttab_search(party?, other_party?, mark?, correspondent?, serial_or_registration_number?, query?, status?, match_mode?, page?, limit?)` —
12
+ finds proceedings by party name, mark text, correspondent firm, or
13
+ application/registration number. Each result carries the board proceeding
14
+ number, proceeding type, filing date, and both sides with their marks and
15
+ serial/registration numbers. Answers "is anyone opposing this trademark".
16
+ - `ttab_proceeding(proceeding_number, type?)` — one proceeding in full: status
17
+ and status date, interlocutory attorney and paralegal, each party's
18
+ correspondence address and pleaded marks, and the complete prosecution
19
+ history (every docket entry, its date, and any due date).
20
+ - `ttab_party_history(party, status?, match_mode?, max_pages?, limit?)` —
21
+ profiles a company across TTAB: how often it appears as plaintiff (opposing)
22
+ versus defendant (opposed), a breakdown by proceeding type, and every name
23
+ spelling it has been filed under.
24
+
25
+ ## Auth
26
+
27
+ Keyless.
28
+
29
+ ## Data sources
30
+
31
+ - <https://ttabvue.uspto.gov/ttabvue/> — TTABVUE, the Board's inquiry system
32
+ (v2.8.0). Server-rendered HTML; there is no JSON API and no bot wall.
33
+ - `v?qt=adv&...` is the advanced-search endpoint. Parameters: `procstatus`
34
+ (`Pending`/`Terminated`/`All`), `pno` (proceeding number), `propno`
35
+ (application/registration number), `qs` (all words anywhere), `propname` +
36
+ `propnameop` (mark), `pn` + `pop` (party), `pn2` + `pop2` (other party),
37
+ `cn` + `cop` (correspondent), `page` (1-based, 25 rows per page). The `*op`
38
+ operators take `''` (contains all words), `beg` (starts with), or `mat`
39
+ (is exactly).
40
+ - `v?pno=<number>[&pty=<type>]` is the proceeding detail page.
41
+
42
+ ### Things worth knowing before you touch this
43
+
44
+ - **An unknown proceeding number returns HTTP 200 with an empty record page**,
45
+ not a 404. The pack detects the blank `Number:` field and returns
46
+ `{found:false, reason:'proceeding_not_found'}`; do not trust the status code.
47
+ - **Result totals saturate at the literal string `"100+"`** — `result_count` is
48
+ a string, not a number, and the pack says so in `result_count_note`.
49
+ - **`EXT` (extension of time to oppose) and `EXA` (ex parte appeal) are keyed by
50
+ application serial number**, not by an 8-digit board number, so one number can
51
+ name two different records. `pty` disambiguates; omitting it lets TTABVUE
52
+ choose, and asking for the wrong `pty` yields the empty page above.
53
+ - **Party names are stored exactly as filed**, so one company appears under
54
+ several spellings. Names are returned raw, and `ttab_party_history` reports
55
+ the spellings it saw rather than merging them.
56
+ - A proceeding has marks on both sides — the defendant's applications under
57
+ attack and the plaintiff's pleaded registrations. They are kept in separate
58
+ party objects, never merged into one mark list.
59
+ - Search results are three top-level `<td class="p1">` cells per row
60
+ (proceeding / defendant / plaintiff); nested layout tables use bare `<td>`,
61
+ which is what makes the cell split safe.
62
+
63
+ ## Quick Start
64
+
65
+ Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
66
+
67
+ ```json
68
+ {
69
+ "mcpServers": {
70
+ "ttab": {
71
+ "url": "https://gateway.pipeworx.io/ttab/mcp"
72
+ }
73
+ }
74
+ }
75
+ ```
76
+
77
+ ### What this endpoint actually serves
78
+
79
+ `tools/list` at `https://gateway.pipeworx.io/ttab/mcp` returns the tools in the table
80
+ above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
81
+ `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
82
+ gateway-wide set. So the tool count you see is larger than this table: a
83
+ single-pack endpoint currently lists roughly 30 shared tools alongside the
84
+ pack's own. The connection's `initialize` response states its exact scope, and
85
+ is the authoritative answer for a given day.
86
+
87
+ This is deliberate, not multiplexing by accident. The meta-tools are what let a
88
+ scoped connection answer a question this pack does not cover — via
89
+ `ask_pipeworx`, which routes across the whole catalog — without you adding a
90
+ second MCP server. There is currently no way to mount a pack endpoint without
91
+ them; if the extra schemas cost you more context than the routing is worth,
92
+ connect to the full gateway once rather than to several pack endpoints.
93
+
94
+ Or connect to the full Pipeworx gateway to get every pack's tools listed
95
+ directly, instead of just this one's:
96
+
97
+ ```json
98
+ {
99
+ "mcpServers": {
100
+ "pipeworx": {
101
+ "url": "https://gateway.pipeworx.io/mcp"
102
+ }
103
+ }
104
+ }
105
+ ```
106
+
107
+ Both URLs reach the same gateway and the same 1669+ data sources. The
108
+ only difference is which pack's tools are listed **directly**; `ask_pipeworx`
109
+ reaches all of them from either one.
110
+
111
+ ## No MCP client? Call it over HTTP
112
+
113
+ ```bash
114
+ curl -X POST https://gateway.pipeworx.io/v1/tools/ttab_search \
115
+ -H 'Content-Type: application/json' \
116
+ -d '{"party":"Nike, Inc.","limit":5}'
117
+ ```
118
+
119
+ No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/ttab_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
120
+
121
+ ## Standalone (no gateway account)
122
+
123
+ This package also runs as a local stdio MCP server — no Pipeworx account, no
124
+ gateway round-trip:
125
+
126
+ ```json
127
+ {
128
+ "mcpServers": {
129
+ "ttab": {
130
+ "command": "npx",
131
+ "args": ["-y", "@pipeworx/mcp-ttab"]
132
+ }
133
+ }
134
+ }
135
+ ```
136
+
137
+ Or run it directly to confirm it starts:
138
+
139
+ ```bash
140
+ npx -y @pipeworx/mcp-ttab
141
+ ```
142
+
143
+ It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
144
+ for **only** this pack's tools — none of the shared meta-tools the gateway
145
+ connection above adds. Same source, same tools, no ask_pipeworx routing.
146
+
147
+ ## Using with ask_pipeworx
148
+
149
+ Instead of calling tools directly, you can ask questions in plain English —
150
+ this works on the pack endpoint above as well as on the full gateway:
151
+
152
+ ```
153
+ ask_pipeworx({ question: "your question about Ttab data" })
154
+ ```
155
+
156
+ The gateway picks the right tool and fills the arguments automatically.
157
+
158
+ ## More
159
+
160
+ - [Docs and guides](https://pipeworx.io/docs)
161
+ - [pipeworx.io](https://pipeworx.io)
162
+
163
+ ## License
164
+
165
+ MIT
package/bin/cli.js ADDED
@@ -0,0 +1,17 @@
1
+ #!/usr/bin/env node
2
+ //
3
+ // Entry point for `npx @pipeworx/mcp-<slug>`.
4
+ //
5
+ // Packs ship as raw TypeScript (no build step — see publish-pack.sh for why:
6
+ // tsx sidesteps every extensionless-import / bare-JSON-import edge case a
7
+ // per-pack tsc build would have to solve one pack at a time). This file
8
+ // registers tsx's ESM loader programmatically, then hands off to src/server.ts,
9
+ // which wraps the pack's {tools, callTool} export in a stdio MCP server.
10
+ //
11
+ // Copied verbatim into every published pack repo by scripts/publish-pack.sh —
12
+ // edit this file, not a per-pack copy.
13
+ import { register } from 'tsx/esm/api';
14
+
15
+ register();
16
+
17
+ await import('../src/server.ts');
package/package.json ADDED
@@ -0,0 +1,28 @@
1
+ {
2
+ "name": "@pipeworx/mcp-ttab",
3
+ "version": "0.1.0",
4
+ "description": "TTAB (Trademark Trial and Appeal Board) MCP — TTABVUE inquiry system",
5
+ "type": "module",
6
+ "main": "src/index.ts",
7
+ "types": "src/index.ts",
8
+ "bin": {
9
+ "mcp-ttab": "bin/cli.js"
10
+ },
11
+ "keywords": ["mcp", "mcp-server", "model-context-protocol", "pipeworx", "ttab"],
12
+ "license": "MIT",
13
+ "repository": {
14
+ "type": "git",
15
+ "url": "git+https://github.com/pipeworx-io/mcp-ttab.git"
16
+ },
17
+ "scripts": {
18
+ "typecheck": "tsc --noEmit"
19
+ },
20
+ "dependencies": {
21
+ "@modelcontextprotocol/sdk": "^1.30.0",
22
+ "tsx": "^4.19.0"
23
+ },
24
+ "devDependencies": {
25
+ "typescript": "^5.9.3",
26
+ "@cloudflare/workers-types": "^4.20260405.1"
27
+ }
28
+ }
package/server.json ADDED
@@ -0,0 +1,18 @@
1
+ {
2
+ "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
3
+ "name": "io.github.pipeworx-io/ttab",
4
+ "title": "Ttab",
5
+ "description": "TTAB (Trademark Trial and Appeal Board) MCP — TTABVUE inquiry system",
6
+ "version": "0.1.0",
7
+ "websiteUrl": "https://pipeworx.io/packs/ttab",
8
+ "repository": {
9
+ "url": "https://github.com/pipeworx-io/mcp-ttab",
10
+ "source": "github"
11
+ },
12
+ "remotes": [
13
+ {
14
+ "type": "streamable-http",
15
+ "url": "https://gateway.pipeworx.io/ttab/mcp"
16
+ }
17
+ ]
18
+ }