Ttab MCP server

@pipeworx/ttab

Trademark disputes before the USPTO Trademark Trial and Appeal Board — oppositions, cancellation petitions, extensions of time to oppose, and ex parte appeals, with both parties, the marks at issue, and the full docket.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

finds proceedings by party name, mark text, correspondent firm, or application/registration number. Each result carries the board proceeding number, proceeding type, filing date, and both sides with their marks and serial/registration numbers. Answers "is anyone opposing this trademark".

• ttabsearch(party?, otherparty?, mark?, correspondent?, serialorregistrationnumber?, query?, status?, matchmode?, page?, limit?) —

and status date, interlocutory attorney and paralegal, each party's correspondence address and pleaded marks, and the complete prosecution history (every docket entry, its date, and any due date).

• ttabproceeding(proceedingnumber, type?) — one proceeding in full: status

profiles a company across TTAB: how often it appears as plaintiff (opposing) versus defendant (opposed), a breakdown by proceeding type, and every name spelling it has been filed under.

• ttabpartyhistory(party, status?, matchmode?, maxpages?, limit?) —

Auth

Keyless.

Data sources

(v2.8.0). Server-rendered HTML; there is no JSON API and no bot wall.

• — TTABVUE, the Board's inquiry system

(Pending/Terminated/All), pno (proceeding number), propno (application/registration number), qs (all words anywhere), propname + propnameop (mark), pn + pop (party), pn2 + pop2 (other party), cn + cop (correspondent), page (1-based, 25 rows per page). The *op operators take '' (contains all words), beg (starts with), or mat (is exactly).

• v?qt=adv&... is the advanced-search endpoint. Parameters: procstatus

• v?pno=[&pty=] is the proceeding detail page.

Things worth knowing before you touch this

not a 404. The pack detects the blank Number: field and returns {found:false, reason:'proceedingnotfound'}; do not trust the status code.

• An unknown proceeding number returns HTTP 200 with an empty record page,

a string, not a number, and the pack says so in resultcountnote.

• Result totals saturate at the literal string "100+" — result_count is

application serial number**, not by an 8-digit board number, so one number can name two different records. pty disambiguates; omitting it lets TTABVUE choose, and asking for the wrong pty yields the empty page above.

• **EXT (extension of time to oppose) and EXA (ex parte appeal) are keyed by

several spellings. Names are returned raw, and ttabpartyhistory reports the spellings it saw rather than merging them.

• Party names are stored exactly as filed, so one company appears under

attack and the plaintiff's pleaded registrations. They are kept in separate party objects, never merged into one mark list.

• A proceeding has marks on both sides — the defendant's applications under

(proceeding / defendant / plaintiff); nested layout tables use bare , which is what makes the cell split safe.

• Search results are three top-level cells per row

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "ttab": {
      "url": "https://gateway.pipeworx.io/ttab/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.