exa vs GleanMark USPTO Trademark Search
exa is a plugin bundle for AI coding tools published by exa-labs. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Docker MCP Catalog, Claude: knowledge-work-plugins). GleanMark USPTO Trademark Search is an MCP server published by gleanmark.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  exa |  GleanMark USPTO Trademark Search |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 3.4.1 Forks (GitHub): 404 Stars (GitHub): 5 200 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 3.4.1 Forks (GitHub): 404 Stars (GitHub): 5 200 Not marked · First seen |
Listed Version: 1.2.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:d88edd571d98 Forks (GitHub): 404 Pulls (Docker Hub): 37 292 Stars (Docker Hub): 7 Stars (GitHub): 5 200 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 3.4.1 Forks (GitHub): 404 Stars (GitHub): 5 200 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | exa | GleanMark USPTO Trademark Search |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 5 200 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 37 292 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 404 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server or your machine | Remote server (gleanmark.com/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/exa-labs/exa-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 days ago | Responded 45 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
exa
Exa AI web search, deep research, and content extraction. Provides MCP tools and research skills for comprehensive web search, people discovery, company research, academic papers, and more.
GleanMark USPTO Trademark Search
USPTO trademark data: 14M+ marks, owners, Office Actions, TTAB cases. Public tools need no account.
How to run each
exa As a Claude Code plugin
/plugin install exa@claude-plugins-officialGleanMark USPTO Trademark Search As a remote MCP server
claude mcp add --transport http trademark-search https://gleanmark.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Only exa has
web_fetch_exaweb_search_exa
Only GleanMark USPTO Trademark Search has
analyze_prosecution_historyanalyze_ttab_proceedingcheck_brand_availabilitycheck_domain_availabilitycompare_markscount_filings_by_periodcount_trademarks_by_attributesfetchget_chain_of_titleget_class_relationshipsget_cohort_event_intervalsget_correspondent_marks
Show the remaining 52
get_correspondent_specializationget_deadline_satisfaction_mappingget_event_code_referenceget_event_status_mappingget_fame_profileget_firm_correspondent_tasksget_firm_deadlinesget_firm_oa_outcomesget_firm_top_correspondentsget_latest_office_actionget_mark_ai_summaryget_mark_deadlinesget_mark_international_profileget_mark_owner_landscapeget_mark_prosecution_summaryget_nice_classesget_owner_ai_summaryget_owner_deadlinesget_owner_filing_trendsget_owner_goods_keywordsget_owner_related_partiesget_owner_ttab_enforcementget_owner_ttab_statsget_prosecution_documentget_prosecution_timelineget_reference_lookupget_similar_marksget_top_filersget_ttab_documentget_ttab_proceeding_detailsget_ttab_top_opposition_filersis_mark_famouslist_prosecution_documentslookup_trademarkphonetic_searchrecommend_nice_classesresearch_office_actionresolve_trademark_subjectrun_knockout_searchrun_safe_analyticssearchsearch_attorneyssearch_by_ownersearch_claimed_colorssearch_design_codessearch_goods_servicessearch_mark_statementssearch_trademarkssearch_ttab_proceedingssuggest_gs_descriptionsvalidate_gs_descriptionweb_research
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (GleanMark USPTO Trademark Search as of 2026-10-21). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of GleanMark USPTO Trademark Search publish no settings it asks for, so we do not compare settings.
What it can do: exa · What it can do: GleanMark USPTO Trademark Search · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.