GleanMark Trademark Search
warningsgleanmark.com
Search 13.7M+ USPTO trademarks. Clearance, phonetic matching, TTAB stats, analytics.
https://gleanmark.com/mcpOAuthMCP 2025-11-25v1.2.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 368 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://gleanmark.com/ |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token, client_credentials |
| Scopes | mcp:tools, offline_access |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 61 tools listable |
| Credentials demanded in prose | ✕resolve_trademark_subject These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
1 of the 61 tools listed anonymously say in their own descriptions that they need an account or a key (resolve_trademark_subject), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: analyze_prosecution_history, analyze_ttab_proceeding, check_brand_availability, check_domain_availability, compare_marks, count_trademarks_by_attributes, 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_trademark_analytics, get_ttab_document, get_ttab_proceeding_details, is_mark_famous, list_prosecution_documents, lookup_trademark, phonetic_search, recommend_nice_classes, research_office_action, resolve_trademark_subject, run_dupont_analysis, run_knockout_search, run_safe_analytics, 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.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/gleanmark-trademark-search)Own this server?
Sign in to claim this listing by proving control of the endpoint.