tools/list) with full input schemas, you rarely need to call one by name. This page is the map of what’s available, the scope each requires, and how calls are metered.
Every tool is 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, not org-scoped, but still require a scope like other reads.
Search
Trademarks
Owners & entities
Attorneys & firms
Proceedings
Reference data
Global, public reference data. Not org-scoped, but still requires a read scope, and is logged but not billed.Account & usage
Utility tools for your own org’s account and consumption. Neither billed nor counted against quota.Monitoring
Watches, alerts, and webhooks. Billed at zero request-level cost; watch capacity itself is capped by your plan.Webhook secrets are never exposed through MCP,
signa_webhooks_list and signa_webhooks_retrieve always redact them. Manage secrets via the REST API instead.Scopes
Most clients request
trademarks:read by default, which covers every data and reference tool. Add billing:read if you want your agent to inspect usage and account details, and portfolios:manage only if you want it to read or change watches, alerts, and webhooks. If a tool needs a scope your session lacks, the call returns a clear error naming the required scope, and the rest of the session keeps working.
Metering
MCP tool calls are metered like REST requests: each call counts against your plan’s quota and appears in your usage and request logs, classified the same way its REST counterpart is (search, read, monitoring, and so on). Search and read tools cost 1 unit;suggest_goods_services costs 2; batch_get_trademarks costs 1 unit per ID (up to 100). Reference-data tools are logged but not billed. Account and usage tools are neither billed nor counted. Over-quota calls return a clear error naming the limit that was hit and when it resets, instead of running the tool. The initialize and tools/list handshake calls are never metered.
Rate limits
MCP requests share a dedicated rate-limit tier of 1,000 requests per minute, separate from your plan’s per-endpoint-type limits. See Rate limits for the full header semantics. If you hit the limit, the response includes aRetry-After header.
Security
- Org isolation. Org context is resolved from your token or API key on every request, never from a tool argument. An agent cannot read or modify another organization’s data, even if prompted to.
- Least privilege. Scopes are enforced per tool. For read-only use, issue an API key without
portfolios:manageso the watch, alert, and webhook write tools are unavailable. - Review tool calls. Most MCP clients let you approve tool calls before they run. Keep approval on for any agent with
portfolios:manage, and treat tool results as data an untrusted prompt could try to act on.
Troubleshooting
401: Access token missing org_id claim
401: Access token missing org_id claim
Your Signa account has not completed onboarding. Log in at app.signa.so and create an organization first.
401: Invalid or expired access token
401: Invalid or expired access token
Your token has expired. Most MCP clients handle refresh automatically. If the error persists, remove and re-add the connection to re-authenticate.
429: Rate limited
429: Rate limited
You are sending more than 1,000 MCP requests per minute. Wait for the
Retry-After period or reduce request frequency.