← ClaudeAtlas

markmeshlisted

Manage a trademark portfolio through MarkMesh's MCP server — list trademarks, filings and deadlines, run cross-office searches and conflict research for clearance, import or refresh filings from national offices, and register watches that report what changed. Every record carries provenance (source office, fetch time, citable office URL). Use when a user asks about their trademarks, filings, renewal deadlines or clients, wants to search/import a mark from an office (USPTO, EUIPO, DPMA, etc.), wants to check whether a proposed name conflicts with existing marks, or wants to monitor a filing for changes.
team-markmesh/mark_mesh_skill · ★ 6 · AI & Automation · score 76
Install: claude install-skill team-markmesh/mark_mesh_skill
# MarkMesh — trademark portfolio over MCP This skill drives the **MarkMesh MCP server**. MarkMesh is a multi-tenant trademark-management platform; this server exposes a customer's portfolio (trademarks, filings, deadlines, clients) plus live trademark-office search/import as MCP tools, scoped to the API key's organisation. If the MarkMesh MCP tools are **not** available in this session, the server isn't configured — point the user to `SETUP.md` (get an API key from the MarkMesh app, add the connector to Claude Desktop, restart). Don't invent a local fallback; there is no local data. ## How auth & scoping work (read this first) - Every tool runs as the **API key's organisation**. You only ever see that org's data — never assume you can reach another firm's or client's records. - Two key types: **`mm_live_*`** → real production portfolio; **`mm_test_*`** → sandbox. Tell the user which one is active if it matters. The sandbox isolates the **portfolio** (trademarks, filings, clients, watches), NOT office search: `search_office` and `search_conflicts` read the same public register corpus either way, so a sandbox search returns real marks. Do not tell a user their sandbox search results are fake. - Calls count against the key's rate limit (live ~300/min, test ~60/min) — the same budget as the REST API. Don't poll in tight loops; batch your reasoning and make deliberate calls. - Authorisation is enforced server-side by org policies. A tool returning an empty