Trademark filing monitor across 40+ countries - detect filings that resemble your brand.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 5 tools
Each tool targets a distinct domain area: alerts, conflicts, billing, pricing, and settings. There is minor potential confusion between billing's 'rate' operation and getPricingList, since both relate to pricing, but the descriptions make the difference clear.
Four tools follow a simple single-word lowercase noun pattern (alert, billing, conflict, settings), while getPricingList breaks the pattern with camelCase and a verb prefix. The naming is readable but not fully consistent.
Five tools is a well-scoped set for a trademark monitoring service. Each tool covers a necessary functional area without unnecessary redundancy or bloat.
The set covers the main lifecycle needs: alert CRUD, conflict management, billing visibility, pricing discovery, and account settings. Minor gaps exist, such as no direct tool for managing monitored territories, but core workflows are supported.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
autoblogautoblogconflict9 fields changedInput schema / descriptionPrevious value: -"List, read, or update IP Defender conflict records (conflicting trademark applications detected by an alert). The 'op' field selects the operation; 'id' is required for 'read' and 'update'; 'alertId' optionally filters 'list' to a single alert."New value: +"List, read, update, or delete IP Defender conflict records (conflicting trademark applications detected by an alert). The 'op' field selects the operation; 'id' is required for 'read', 'update', and 'delete'; 'alertId' optionally filters 'list' to a single alert."Input schema / properties / alertId / descriptionPrevious value: -"Alert ID. When provided with op='list', only conflicts belonging to this alert are returned. Ignored for 'read' and 'update'."New value: +"Alert ID. When provided with op='list', only conflicts belonging to this alert are returned. Ignored for 'read', 'update', and 'delete'."Input schema / properties / data / descriptionPrevious value: -"Conflict payload. Required for 'update'. Ignored for 'list' and 'read'."New value: +"Conflict payload. Required for 'update'. Ignored for 'list', 'read', and 'delete'."Input schema / properties / id / descriptionPrevious value: -"Conflict ID. Required for 'read' and 'update'. Ignored for 'list'."New value: +"Conflict ID. Required for 'read', 'update', and 'delete'. Ignored for 'list'."Input schema / properties / op / descriptionPrevious value: -"Operation to perform: 'list' returns all conflicts for the user (or for a single alert when 'alertId' is given); 'read' returns one conflict with its parent alert; 'update' changes the state of one conflict."New value: +"Operation to perform: 'list' returns all conflicts for the user (or for a single alert when 'alertId' is given); 'read' returns one conflict with its parent alert; 'update' changes the state of one conflict; 'delete' removes one conflict."Input schema / properties / op / enumPrevious value: -[
- "list",
- "read",
- "update"
-]New value: +[
+ "list",
+ "read",
+ "update",
+ "delete"
+]Output schema / descriptionPrevious value: -"Raw structured payload for the conflict MCP tool. Wrapped by the MCP gateway in { content, isError, structuredContent }. The 'data' field is always present; 'baseURL' is present for op='list', 'read', and 'update'; 'counts' is present for op='list'; 'alert' is present for op='read'."New value: +"Raw structured payload for the conflict MCP tool. Wrapped by the MCP gateway in { content, isError, structuredContent }. The 'data' field is always present; 'baseURL' is present for op='list', 'read', 'update', and 'delete'; 'counts' is present for op='list'; 'alert' is present for op='read'."Output schema / properties / data / descriptionPrevious value: -"Conflict data. For 'list' it is an array of conflict objects. For 'read' and 'update' it is a single conflict object."New value: +"Conflict data. For 'list' it is an array of conflict objects. For 'read' and 'update' it is a single conflict object. For 'delete' it is an object with { deleted: true }."Output schema / properties / data / oneOfPrevious value: -[
- {
- "description": "Array of conflicts (op='list').",
- "items": {
- "$ref": "#/$defs/conflict"
- },
- "type": "array"
- },
- {
- "$ref": "#/$defs/conflict"
- }
-]New value: +[
+ {
+ "description": "Array of conflicts (op='list').",
+ "items": {
+ "$ref": "#/$defs/conflict"
+ },
+ "type": "array"
+ },
+ {
+ "$ref": "#/$defs/conflict"
+ },
+ {
+ "additionalProperties": false,
+ "description": "Deletion result (op='delete').",
+ "properties": {
+ "deleted": {
+ "const": true,
+ "description": "Always true when the conflict was deleted.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "deleted"
+ ],
+ "type": "object"
+ }
+]echobillingconflictsettingsalertechogetPricingListTrademark search, monitoring and conflict research across 30+ registers, with provenance.
Monitors Brazilian trademarks at INPI and alerts on new RPI publications and deadlines.
Search 13.7M+ USPTO trademarks. Clearance, phonetic matching, TTAB stats, analytics.
Monitora marcas no INPI e alerta despachos novos da RPI por processo ou titular.
Add one secure layer between your agents and this server.
