lookup_trademark — GleanMark Trademark Search MCP Tool Read-only
lookup_trademark
(lookup trademark) is one of 64 tools on the
GleanMark Trademark Search
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call lookup_trademark from your client
- Claude Code GleanMark Trademark Search lookup_trademark run in your project directory
- Claude Desktop GleanMark Trademark Search lookup_trademark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GleanMark Trademark Search lookup_trademark ~/.cursor/mcp.json
- VS Code GleanMark Trademark Search lookup_trademark .vscode/mcp.json
- Zed GleanMark Trademark Search lookup_trademark ~/.config/zed/settings.json
- Windsurf GleanMark Trademark Search lookup_trademark ~/.codeium/windsurf/mcp_config.json
- Cline GleanMark Trademark Search lookup_trademark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GleanMark Trademark Search lookup_trademark ~/.gemini/settings.json
- Grok GleanMark Trademark Search lookup_trademark .mcp.json (in your project root)
- ChatGPT GleanMark Trademark Search lookup_trademark Settings → Connectors → Advanced → Developer mode
- Claude.ai GleanMark Trademark Search lookup_trademark Settings → Connectors → Add custom connector
- LangChain GleanMark Trademark Search lookup_trademark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http trademark-search https://gleanmark.com/mcpOther tools on this server
- analyze_prosecution_history
- analyze_ttab_proceeding
- check_brand_availability
- check_domain_availability
- compare_marks
- count_filings_by_period
- count_trademarks_by_attributes
- fetch
- get_chain_of_title
- get_class_relationships
- get_cohort_event_intervals
- get_correspondent_marks
- get_correspondent_specialization
- get_deadline_satisfaction_mapping
- get_event_code_reference
- get_event_status_mapping
- get_fame_profile
- get_firm_correspondent_tasks
- get_firm_deadlines
- get_firm_oa_outcomes
- get_firm_top_correspondents
- get_latest_office_action
- get_mark_ai_summary
- get_mark_deadlines
- get_mark_international_profile
- get_mark_owner_landscape
- get_mark_prosecution_summary
- get_nice_classes
- get_owner_ai_summary
- get_owner_deadlines
- get_owner_filing_trends
- get_owner_goods_keywords
- get_owner_related_parties
- get_owner_ttab_enforcement
- get_owner_ttab_stats
- get_prosecution_document
- get_prosecution_timeline
- get_reference_lookup
- get_similar_marks
- get_top_filers
- get_ttab_document
- get_ttab_proceeding_details
- get_ttab_top_opposition_filers
- is_mark_famous
- list_prosecution_documents
- phonetic_search
- recommend_nice_classes
- research_office_action
- resolve_trademark_subject
- run_knockout_search
- run_safe_analytics
- search
- search_attorneys
- search_by_owner
- search_claimed_colors
- search_design_codes
- search_goods_services
- search_mark_statements
- search_trademarks
- search_ttab_proceedings
- suggest_gs_descriptions
- validate_gs_description
- web_research
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.