Skip to main content
The Signa MCP server exposes 60 tools across search, trademark research, party intelligence, proceedings, reference data, account/usage, and monitoring. Your client lists them automatically (tools/list) with full input schemas — you rarely need to call a tool by name. This page is the map of what’s available and the scope each requires.
Most tools are org-scoped to your authenticated session. Org context comes from your token or API key — never from a tool argument — so an agent can’t read or change another organization’s data. Reference-data tools (offices, jurisdictions, classifications, rules) are global public data — they aren’t org-scoped, but still require the trademarks:read scope like other reads. Read tools need a read, search, or trademarks:read scope; account/usage tools need billing:read; watch writes need portfolios:manage. See Authentication & security.
ToolWhat it doesScopeRead/Write
search_trademarksSearch global registrations by name, owner, Nice class, jurisdiction, or status. Exact, phonetic, fuzzy, and prefix matching across 21 offices.readRead
suggestQuick typeahead across trademarks, owners, attorneys, and firms — compact results for disambiguation.readRead

Trademarks

ToolWhat it doesScopeRead/Write
get_trademarkFull detail for one mark by ID — owners, attorneys, classifications, events, media.readRead
list_trademarksList marks with filtering and sorting (use search_trademarks for text search).readRead
get_trademark_historyProsecution event timeline for a mark (filings, publications, registrations, status changes).readRead
get_trademark_changesVersion-level field diffs — what changed between ingested versions, and when.readRead
get_trademark_relatedMark-to-mark relationships: Madrid designations, divisionals, seniority claims, transformations.readRead
get_trademark_proceedingsProceedings involving a mark (oppositions, cancellations), each with its parties.readRead
get_trademark_coverageJurisdictional coverage — Madrid designation territories and protection status.readRead
get_trademark_sourceRaw-record provenance: source office, observation date, and source format.readRead
batch_get_trademarksFetch full detail for up to 100 marks by ID in one call, with a not_found list.readRead

Owners & entities

ToolWhat it doesScopeRead/Write
get_ownerOwner (applicant/registrant) detail with portfolio statistics.readRead
list_ownersSearch and list owners — find companies or individuals who hold marks.readRead
get_owner_trademarksAn owner’s trademarks (summary tier) with filtering and sorting.readRead
get_owner_relatedOwners related via the GLEIF corporate hierarchy (parent/child).readRead
get_entityA resolved entity: the cross-office identity over per-office owner clusters, with link evidence and public-company facts.readRead
list_entitiesSearch resolved entities (one company across all offices), filterable by public-company facts.readRead
get_entity_trademarksA resolved entity’s trademarks fanned across all member owners.readRead
get_entity_familyA resolved entity’s direct GLEIF corporate family (parent + direct subsidiaries).readRead

Attorneys & firms

ToolWhat it doesScopeRead/Write
get_attorneyDetail for an attorney/representative of record.readRead
list_attorneysSearch and list attorneys/representatives.readRead
get_attorney_trademarksAn attorney’s trademarks (summary tier) with filtering and sorting.readRead
get_attorney_clientsOwners an attorney represents, each with a shared-mark count.readRead
get_firmLaw-firm detail, including portfolio and attorneys.readRead
list_firmsSearch and list law firms, ranked by portfolio size or attorney count.readRead
get_firm_attorneysA firm’s attorneys, each with portfolio stats.readRead
get_firm_trademarksTrademarks handled by a firm’s attorneys (summary tier).readRead

Proceedings

ToolWhat it doesScopeRead/Write
get_proceedingDetail for one proceeding (opposition, cancellation, etc.) by ID.readRead
list_proceedingsList TTAB oppositions, cancellations, and other proceedings with filtering.readRead

Reference data

Global, public reference data — not org-scoped, but requires the trademarks:read scope like other reads. These tools are logged but not billed.
ToolWhat it doesScopeRead/Write
list_officesSupported trademark offices (live connectors) with jurisdiction and update cadence.trademarks:readRead
get_officeA single office by its lowercase office code (e.g. uspto, euipo, wipo).trademarks:readRead
list_jurisdictionsSupported jurisdictions (ISO-2 plus regional/WIPO codes), with Madrid membership and live-office coverage.trademarks:readRead
get_jurisdictionA single jurisdiction by code, including Madrid membership and member jurisdictions.trademarks:readRead
get_deadline_rulesMaintenance/renewal deadline rules with statutory citations; optionally per jurisdiction.trademarks:readRead
get_opposition_rulesOpposition window rules with citations, duration, and time zone; optionally per jurisdiction.trademarks:readRead
list_classificationsNice classification classes (the 45-class WIPO standard), filterable by category or keyword.trademarks:readRead
suggest_classificationsSuggest Nice classes for a natural-language description, ranked with confidence and rationale.readRead
list_goods_servicesBrowse/search the curated goods & services term catalog.trademarks:readRead
suggest_goods_servicesDraft filing-ready goods/services wording per Nice class from a description.readRead
list_design_codesVienna classification design codes (figurative-element taxonomy for logos/devices).trademarks:readRead
get_design_codeA single Vienna design code with notes and its child codes.trademarks:readRead
list_event_typesPer-office event-type mappings (raw office codes → canonical Signa event types).trademarks:readRead

Account & usage

Utility tools for your own org’s account and consumption. They require the billing:read scope and are neither billed nor counted against quota.
ToolWhat it doesScopeRead/Write
get_usageCurrent billing-period usage plus the per-endpoint-type quota and rate-limit matrix.billing:readRead
get_usage_summaryDaily usage breakdown (requests, billed units, errors, avg latency) from rollups.billing:readRead
get_accountOrg identity (id/name, plan, key scopes + rate-limit tier) with the plan quota breakdown.billing:readRead

Monitoring

Watch and alert reads are read-only. Creating or changing watches — and the watch-scoped diagnostics, preview, and alert lookups — requires the portfolios:manage scope.
ToolWhat it doesScopeRead/Write
signa_watches_listList monitoring watches for your org (cursor-paginated).readRead
signa_watches_retrieveRetrieve a single watch by ID.readRead
signa_watches_createCreate a watch (same validation as POST /v1/watches).portfolios:manageWrite
signa_watches_updateUpdate a watch (PATCH semantics — omitted fields unchanged).portfolios:manageWrite
signa_watches_deleteSoft-delete a watch (sets deleted_at; row retained).portfolios:manageWrite
pause_watchPause a watch (stops new alerts).portfolios:manageWrite
resume_watchResume a paused watch.portfolios:manageWrite
preview_watchDry-run a watch query: estimate matches and preview marks. No watch is created.portfolios:manageRead
get_watch_diagnosticsAudit-mode provenance trace for one (watch, trademark) pair.portfolios:manageRead
signa_alerts_listList monitoring alerts for your org.readRead
signa_alerts_retrieveRetrieve a single alert by ID.readRead
list_alerts_for_watchList alerts emitted by a single watch (cursor-paginated).portfolios:manageRead
lookup_alertBulk-fetch up to 100 alerts by ID (polling pattern).portfolios:manageRead
signa_webhooks_listList webhook endpoints (secrets are never returned).readRead
signa_webhooks_retrieveRetrieve one webhook endpoint (secret redacted).readRead
Webhook secrets are never exposed through MCP — signa_webhooks_* tools always redact them. Manage secrets via the REST API.

Metering

MCP tool calls are metered just like REST requests — each call counts against your plan quota and shows up in your usage and request logs. Reference-data tools are logged but not billed; account/usage tools are neither billed nor counted. See Usage & metering.

Trying tools

You don’t invoke tools directly — describe what you want and your agent maps it to the right calls. See Use cases for prompts that exercise each area.