GleanMark Trademark Search
REMOTE · GLEANMARK.COM · SCANNED AUG 3
Search 13.7M+ USPTO trademarks. Clearance, phonetic matching, TTAB stats, analytics.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13036 tokens (~176/item across 74 items; 60 tools + 14 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- Structured output schemas are declared (30% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · gleanmark.com
claude mcp add --transport http com-gleanmark-trademark-search https://gleanmark.com/mcp
[mcp_servers.com-gleanmark-trademark-search] url = "https://gleanmark.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gleanmark-trademark-search": {
"type": "remote",
"url": "https://gleanmark.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-gleanmark-trademark-search --url https://gleanmark.com/mcp --transport streamable-http
mcp_servers:
com-gleanmark-trademark-search:
url: "https://gleanmark.com/mcp" {
"mcpServers": {
"com-gleanmark-trademark-search": {
"type": "http",
"url": "https://gleanmark.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → excellent functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New tool “get_owner_related_parties” functional
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +4
- Authorization: unverified → partial ▲ security
- Tool “get_correspondent_marks” rewrote its description, which is the text the model reads security
- Tool “get_correspondent_specialization” rewrote its description, which is the text the model reads security
- Tool “get_firm_correspondent_tasks” rewrote its description, which is the text the model reads security
- Tool “get_firm_top_correspondents” rewrote its description, which is the text the model reads security
- Tool “get_mark_owner_landscape” rewrote its description, which is the text the model reads security
- Tool “get_top_filers” rewrote its description, which is the text the model reads security
- Tool “search_design_codes” rewrote its description, which is the text the model reads security
- Tool “count_trademarks_by_attributes” rewrote its description, which is the text the model reads security
- “search_design_codes” reworded the description of “mode” cosmetic
- Tool “get_class_relationships” changed its title: Get Related Nice Classes cosmetic
- Tool “get_cohort_event_intervals” changed its title: Cohort Event Intervals cosmetic
- Tool “get_correspondent_marks” changed its title: Marks for a Correspondent cosmetic
- Tool “get_correspondent_specialization” changed its title: Correspondent Specialization cosmetic
- Tool “get_deadline_satisfaction_mapping” changed its title: Deadline Satisfaction Reference cosmetic
- Tool “get_event_code_reference” changed its title: USPTO Event Code Reference cosmetic
- Tool “get_event_status_mapping” changed its title: USPTO Event Status Reference cosmetic
- Tool “get_fame_profile” changed its title: Fame Profile for a Mark cosmetic
- Tool “get_firm_correspondent_tasks” changed its title: Firm Correspondent Tasks cosmetic
- Tool “get_firm_deadlines” changed its title: Firm Deadlines cosmetic
- Tool “get_firm_oa_outcomes” changed its title: Firm Office Action Outcomes cosmetic
- Tool “get_firm_top_correspondents” changed its title: Top Correspondents at a Firm cosmetic
- Tool “get_latest_office_action” changed its title: Latest Office Action for a Mark cosmetic
- Tool “get_mark_ai_summary” changed its title: AI Summary of a Mark cosmetic
- Tool “get_mark_deadlines” changed its title: Deadlines for a Mark cosmetic
- Tool “get_mark_international_profile” changed its title: International Filings for a Mark cosmetic
- Tool “get_mark_owner_landscape” changed its title: Owner Landscape for a Mark cosmetic
- Tool “get_mark_prosecution_summary” changed its title: Prosecution Summary for a Mark cosmetic
- Tool “get_nice_classes” changed its title: Look Up Nice Classes cosmetic
- Tool “get_owner_ai_summary” changed its title: AI Summary of an Owner cosmetic
- Tool “get_owner_deadlines” changed its title: Deadlines for an Owner cosmetic
- Tool “get_owner_filing_trends” changed its title: Owner Filing Trends cosmetic
- Tool “get_owner_goods_keywords” changed its title: Owner Goods & Services Keywords cosmetic
- Tool “get_owner_ttab_enforcement” changed its title: TTAB Enforcement History for an Owner cosmetic
- Tool “get_owner_ttab_stats” changed its title: TTAB Statistics for an Owner cosmetic
- Tool “get_prosecution_document” changed its title: Get a Prosecution Document cosmetic
- Tool “get_prosecution_timeline” changed its title: Prosecution Timeline cosmetic
- Tool “get_reference_lookup” changed its title: Reference Data Lookup cosmetic
- Tool “get_similar_marks” changed its title: Find Similar Marks cosmetic
- Tool “get_top_filers” changed its title: Top Trademark Filers cosmetic
- Tool “get_trademark_analytics” changed its title: Trademark Analytics cosmetic
- Tool “get_ttab_document” changed its title: Get a TTAB Document cosmetic
- Tool “get_ttab_proceeding_details” changed its title: TTAB Proceeding Details cosmetic
- Tool “is_mark_famous” changed its title: Check Whether a Mark Is Famous cosmetic
- Tool “list_prosecution_documents” changed its title: List Prosecution Documents cosmetic
- Tool “lookup_trademark” changed its title: Look Up Trademark by Serial Number cosmetic
- Tool “phonetic_search” changed its title: Search Marks That Sound Alike cosmetic
- Tool “recommend_nice_classes” changed its title: Recommend Nice Classes cosmetic
- Tool “research_office_action” changed its title: Research an Office Action cosmetic
- Tool “resolve_trademark_subject” changed its title: Resolve an Ambiguous Name cosmetic
- Tool “run_dupont_analysis” changed its title: Run DuPont Likelihood-of-Confusion Analysis cosmetic
- Tool “run_knockout_search” changed its title: Run Knockout Search cosmetic
- Tool “run_safe_analytics” changed its title: Run Safe Analytics Query cosmetic
- Tool “search_attorneys” changed its title: Search Trademark Attorneys cosmetic
- Tool “search_by_owner” changed its title: Search Marks by Owner cosmetic
- Tool “search_claimed_colors” changed its title: Search Marks by Claimed Color cosmetic
- Tool “search_design_codes” changed its title: Search USPTO Design Codes cosmetic
- Tool “search_mark_statements” changed its title: Search Mark Statements cosmetic
- Tool “search_trademarks” changed its title: Search Trademarks cosmetic
- Tool “search_ttab_proceedings” changed its title: Search TTAB Proceedings cosmetic
- Tool “suggest_gs_descriptions” changed its title: Suggest Goods & Services Descriptions cosmetic
- Tool “validate_gs_description” changed its title: Validate a Goods & Services Description cosmetic
- Tool “web_research” changed its title: Web Research cosmetic
- Tool “analyze_prosecution_history” changed its title: Analyze Prosecution History cosmetic
- Tool “analyze_ttab_proceeding” changed its title: Analyze a TTAB Proceeding cosmetic
- Tool “check_brand_availability” changed its title: Check Brand Availability cosmetic
- Tool “check_domain_availability” changed its title: Check Domain Availability cosmetic
- Tool “compare_marks” changed its title: Compare Two Marks for Confusion cosmetic
- Tool “count_trademarks_by_attributes” changed its title: Count Trademarks by Attributes cosmetic
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://gleanmark.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gleanmark.com | CN=YR2,O=Let's Encrypt,C=US | 20 Jul 2026 | 18 Oct 2026 | RSA 2048 | SHA256-RSA | 5e8af32ff0ff1664f08f58964865949b492 |
| SANs: gleanmark.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of gleanmark.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gleanmark.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gleanmark.com/mcp | Verified | 200 | |
| http (plaintext) | http://gleanmark.com/mcp | HTTPS enforced | 301 | https://gleanmark.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
run_safe_analytics Run Safe Analytics Query ~191
Run a constrained business-level analytics query without exposing schema details. This is the default fallback for bespoke rankings, counts, snapshots, and timelines across owners, firms, and correspondents. Prefer this before chaining search, summary, or web research tools for aggregate business questions.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_type | string | yes | Business analytics mode: ranking, count, snapshot, or timeline. |
| entity | string | yes | What to analyze. Ranking currently supports owners. Count, snapshot, and timeline also support firms and correspondents. |
| filters | object | — | — |
| limit | integer | — | Maximum number of ranked rows, preview marks, or timeline events to return. |
| metric | string | — | Required for count. Ranking currently supports filings only. |
| subject_name | string | — | Required for count, snapshot, and timeline. Examples: "Ideaya Biosciences", "Goodwin Procter", or "Todd Schneider". |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_type | string | yes | — |
| count_result | — | yes | — |
| entity | string | yes | — |
| filters_applied | object | yes | — |
| metric | — | yes | — |
| open_in_gleanmark | string | yes | — |
| rankings | array | yes | — |
| resolution | — | yes | — |
| resolved_subject | — | yes | — |
| returned | integer | yes | — |
| snapshot_result | — | yes | — |
| subject_name | — | yes | — |
| summary | string | yes | — |
| timeline_result | — | yes | — |
| title | string | yes | — |
| total_matching_entities | — | — | — |
| total_matching_live_marks | — | — | — |
| total_matching_marks | — | — | — |
No examples provided.
search_attorneys Search Trademark Attorneys ~81
Search for trademark attorneys or law firms. Returns prosecution statistics, TTAB proceeding counts (as plaintiff/defendant), and contact information.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum number of results to return |
| search_term | string | yes | Attorney name or law firm name to search for |
| search_type | string | — | Search for individual attorneys or law firms |
| Name | Type | Req | Description |
|---|---|---|---|
| open_in_gleanmark | string | — | — |
| query | string | yes | — |
| results | array | yes | — |
| search_type | string | yes | — |
No examples provided.
search_by_owner Search Marks by Owner ~94
Search for trademark owners by name. Use this to resolve or list candidate owners, not for owner counts, rankings, prosecution snapshots, or recent activity checks. Returns matching companies/individuals with their trademark portfolio statistics (total marks, live/dead counts, registered/pending).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum number of owners to return |
| owner_name | string | yes | Owner name to search for (company or individual) |
| Name | Type | Req | Description |
|---|---|---|---|
| open_in_gleanmark | string | — | — |
| owners | array | yes | — |
| query | string | yes | — |
No examples provided.
search_claimed_colors Search Marks by Claimed Color ~491
Search or count US trademarks by the colours they claim, parsed from USPTO colour-claim statements. Neither TESS nor its successor offers this. TWO levels: level="family" (16 families; searching "red" also finds dark red, maroon, burgundy) and level="shade" (the exact term as claimed, e.g. "dark red"). Use match="all" for "claims at least these colours", match="only" for "claims exactly these and nothing else", match="only_bw" to also tolerate black/white. Set claimed=false to count marks whose statement DISCLAIMS colour. Modes: count, top_owners, list_marks, vocabulary (list the valid families or shades with corpus counts), explain_term (which family a shade belongs to), by_serial (what one mark claims).
| Name | Type | Req | Description |
|---|---|---|---|
| claimed | boolean | — | false = count marks whose statement disclaims colour ("Color is not claimed as a feature of the mark"). |
| colors | array | — | Colour terms, e.g. ["orange","green","red"]. Must be real families or shades — call mode="vocabulary" if unsure. Omit to match every colour-claiming mark. |
| level | string | — | family = 16 broad families (red covers maroon). shade = the exact claimed term. |
| limit | integer | — | Rows for top_owners, list_marks, vocabulary. |
| match | string | — | all = claims at least these. only = claims exactly these, nothing else. only_bw = exactly these, allowing black/white (usually background). |
| mode | string | — | count = how many marks match. top_owners = who owns the most. list_marks = sample the matches. vocabulary = valid colour terms + corpus counts. explain_term = a shade's family. by_serial = what one m… |
| nice_class | string | — | Restrict to one Nice class, e.g. "25" or "025". |
| registration_number | string | — | Registration number for mode="by_serial"; resolved to its serial number automatically. |
| serial_number | string | — | Eight-digit serial number for mode="by_serial". |
| status | string | — | registered/pending are narrower than live. "How many live REGISTRATIONS" means status="registered". |
| term | string | — | Required for mode="explain_term", e.g. "maroon". |
No output schema declared.
No examples provided.
search_design_codes Search USPTO Design Codes ~377
Find US trademarks by USPTO design code — the codes examiners assign to the visual elements of a logo (26.17.01 = straight bands, 24.11 = crowns). Accepts dotted (26.17.01) or packed (261701) form. USPTO design vocabulary is literal and narrow: it records "Bands, straight" where a person says "stripe", and has no entry for words like "swoosh", so a plain shape word resolves to a code through mode="search_codes" before marks can be counted or listed. Modes: count, top_owners, list_marks, by_serial (what codes one mark carries), describe_code, search_codes. Omitting mode infers it from the arguments supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | — | Design codes, dotted or packed, e.g. ["26.17.01"]. |
| limit | integer | — | — |
| match | string | — | all = mark carries every code. any = at least one. |
| mode | string | — | search_codes = find a code from a word. describe_code = what a code means. count/top_owners/list_marks = marks carrying the codes. Omit it and the mode is inferred: query -> search_codes, serial_numb… |
| nice_class | string | — | Restrict to one Nice class, e.g. "25". |
| query | string | — | Required for mode="search_codes". A shape word: band, bar, circle, star, triangle, chevron, crown, leaf, arrow, shield. |
| registration_number | string | — | Registration number for mode="by_serial"; resolved to its serial number automatically. |
| serial_number | string | — | Eight-digit serial number for mode="by_serial". |
| status | string | — | — |
No output schema declared.
No examples provided.
search_mark_statements Search Mark Statements ~273
Search the statements USPTO records on a trademark: disclaimer ("no claim is made to PIZZA apart from the mark"), description (the examiner's written description of the drawing — "the mark consists of a red and white striped awning"), translation (foreign wording), prior_marks (claimed ownership of earlier registrations). Answers "which marks disclaim PIZZA" and "which marks are described as stripes". Colour claims have their own tool (search_claimed_colors); goods text is served by search_trademarks. Modes: count, top_owners, list_marks, by_serial (every statement on one mark), statement_types.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| mode | string | — | — |
| nice_class | string | — | Restrict to one Nice class, e.g. "25". |
| registration_number | string | — | Registration number for mode="by_serial"; resolved to its serial number automatically. |
| serial_number | string | — | Eight-digit serial number for mode="by_serial". |
| statement_type | string | — | Required except for by_serial and statement_types. |
| status | string | — | — |
| text | string | — | Free text to find inside the statement, minimum 3 characters (e.g. "PIZZA", "stripe"). Omit to count every mark carrying that statement type. |
No output schema declared.
No examples provided.
search_trademarks Search Trademarks ~188
Search the USPTO trademark database by name — a RANKED similarity/prefix search that returns the closest whole-mark matches (14M records). It is NOT an exhaustive contains-scan: multi-word marks that merely contain the queried word rank low and are usually cut (a KWIK query will miss KWIK REWARDS / KWIK KOPY). To enumerate ALL live marks containing a word — including compounds and respelled forms via USPTO pseudo-mark equivalents — use list_marks_containing_term instead. Thin results here are never proof a name is absent or available; availability questions belong to run_knockout_search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Maximum number of results to return |
| nice_classes | array | — | Filter by Nice Classification classes (1-45) |
| query | string | yes | Search query for trademark name |
| status_filter | string | — | Filter by trademark status |
| Name | Type | Req | Description |
|---|---|---|---|
| open_in_gleanmark | string | — | — |
| query | string | yes | — |
| results | array | yes | — |
| total_count | integer | yes | — |
No examples provided.
search_ttab_proceedings Search TTAB Proceedings ~220
Search TTAB proceedings using the same discovery index as the GleanMark TTAB workspace. Use for broad proceeding discovery by party name, exact 8-digit proceeding number, 8-digit trademark serial number, or 7-digit registration number. Supports status, proceeding type, matched party role, and owner-name filters. For one known case after discovery, use get_ttab_proceeding_details; for owner enforcement statistics, use get_owner_ttab_enforcement.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| owner_contains | string | — | Optional additional substring that must appear in any party name. |
| query | string | yes | Party name, 8-digit proceeding/serial number, or 7-digit registration number. |
| role_filter | array | — | Role of the party matched by query: P for plaintiff/petitioner, D for defendant/respondent. |
| status_filter | array | — | — |
| type_filter | array | — | Exact TTAB type labels, such as Oppositions, Cancellations, or Extensions of Time to Oppose. |
No output schema declared.
No examples provided.
suggest_gs_descriptions Suggest Goods & Services Descriptions ~166
Search the USPTO Trademark ID Manual (pre-approved, surcharge-free goods & services identifications) by plain words. Call once per distinct product/service line (e.g. construction services and lighting products are two separate calls), not once per whole business. Returns selectable Term IDs; entries with {curly-brace} placeholders are fill-in templates.
| Name | Type | Req | Description |
|---|---|---|---|
| classes | array | — | Optional Nice class filter, 1-45 (padded or unpadded, e.g. 9 or "009") |
| gs_type | string | — | Optional filter to goods or services entries |
| limit | integer | — | Max suggestions (default 10) |
| query | string | yes | Plain-words description of ONE product or service line (e.g. "phone cases with batteries") |
| Name | Type | Req | Description |
|---|---|---|---|
| cta | string | — | — |
| open_in_gleanmark | string | — | — |
| suggestions | array | yes | — |
No examples provided.
validate_gs_description Validate a Goods & Services Description ~121
Check a draft goods & services description against the USPTO ID Manual, clause by clause (clauses split on ";"). Each clause comes back verbatim (selectable pre-approved entry), close (with up to 3 pre-approved substitutes), or freeform (subject to the USPTO $200/class free-form surcharge). Deterministic — no AI rewriting.
| Name | Type | Req | Description |
|---|---|---|---|
| classes | array | — | Optional Nice class scope, 1-45; without it exact matches may span classes |
| text | string | yes | The draft goods & services description to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| clauses | array | yes | — |
| summary | object | yes | — |
| truncated | boolean | yes | — |
| unprocessed_clause_count | integer | — | — |
No examples provided.
web_research Web Research ~111
Research a company, trademark, or legal topic on the internet. Returns grounded results with source citations. Use for company background, recent news, common law trademark use, or case law research.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_name | string | yes | Company name, trademark, or topic to research |
| mark_text | string | — | Trademark text (for common_law_use and state_registrations searches) |
| nice_classes | array | — | Nice classes for context |
| research_type | string | yes | Type of research to perform |
No output schema declared.
No examples provided.