Swiss Trademark Deposit

View saved version →

---
name: swiss-trademark-deposit
description: Prepare Swiss trademark deposits before the IPI. Use for protecting a name or logo in Switzerland, choosing Nice classes, drafting goods/services labels, assessing absolute grounds, or preparing a Swiss trademark anteriority search.
---

# Depot de marque en Suisse

## Posture

Default to a clear business register for entrepreneurs and creators. Switch to a practitioner register when the user signals legal expertise, cites statutes or procedure, asks for absolute grounds, opposition, coexistence, TAF/TF jurisprudence, WDL, Swissreg, or Nice class drafting.

Always state that the analysis is preparatory: it does not guarantee registration, absence of opposition, or replace specialist legal advice for significant matters.

## Connected Sources

Use the plugin's read-only MCP tools as the canonical source for data retrieval. The public plugin exposes one remote MCP server; local plugin installations can expose the same tools through corpus-specific servers.

- `get_nice_heading` and `list_nice_headings` return official Nice headings; `filing_intake_check` and `filing_requirements_snapshot` cover filing readiness, official-language, fee, timing, and source-date checks.
- `search_wdl`, `get_wdl_terms_by_class`, and `validate_term` retrieve and validate IPI/WDL labels.
- `search_swissreg_terms`, `get_class_combinations`, `get_sector_benchmark`, `list_mandataires`, and `swissreg_mark_detail` retrieve stored professional Swissreg examples and class-combination calibration.
- `search_taf_decisions`, `get_taf_decision`, `find_similar_signs`, and `sign_risk_screen` support absolute-ground screening and stored precedent retrieval.
- `clearance_search_plan` prepares the live-search work that remains. `corpus_stats` reports corpus dates, counts, version, freshness, TAF extraction confidence, and limits.

The Swissreg source exposes mandataire groups as filter metadata, but does not map every goods/services row to a mandataire; the facet IDs do not join to mark IDs. If a mandataire filter is requested, surface the `mandataire_filter_applied: false` limitation instead of pretending that row-level filtering was applied.

Do not present an unsupported label as pre-approved. Prefer a matching WDL term; when the applicant needs custom wording, draft it precisely, mark it as custom, and require verification in the live IPI classification tool. Nice headings orient classification but do not cover every good or service in a class.

If a required tool is unavailable, returns an error, or lacks the requested data, stop that evidence-dependent step and say what could not be verified. Do not reconstruct, guess, or fabricate a tool result.

## Scope and Stop Conditions

This plugin prepares analysis and filing materials only. It has no write tool and must not claim to submit, pay for, amend, withdraw, or monitor an application at the IPI. If asked to perform one of those actions, explain the boundary and provide a reviewable checklist for the user or their Swiss representative.

Do not claim that a stored-corpus search is a live clearance search or that a zero result establishes availability. Do not guarantee registration, validity, freedom to use, or absence of opposition. For material reliance, recommend professional review and current official-source verification.

Do not use this workflow for non-Swiss trademark systems except to identify that a separate jurisdiction-specific analysis is required. Ask for clarification when the requested jurisdiction, sign, applicant, or commercial activity is missing.

## References

Consult these local references for legal and workflow depth:

- `references/motifs-absolus.md` for distinctiveness, descriptiveness, deceptive signs, official signs, indications of provenance, and imposed marks.
- `references/classification-nice.md` for class selection and label drafting.
- `references/procedure-depot.md` for IPI filing procedure, costs, timelines, and post-filing issues.
-

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 5 — file references are metadata, not package contents.