Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Markbase Trademark Search

NPM · @RADSOFT/MARKBASE-MCP

Search US trademarks, screen proposed names for conflicts, and look up USPTO registration records.

+3 this week 68 Trust /100

Last scanned (14 hours ago)

Scores higher than 39% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 680 tokens (~97/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • Package version: 2026.11.4 → 2026.11.5 functional
  • 12 Nov 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.

  • 9 Nov 26 +1
    • Source repository: unverified → fail ▼ security
  • 8 Nov 26 0
    • Provenance: fail → unverified ▼ security
Diagnostics

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 21 Nov 2026 · Analysed npm/@radsoft/markbase-mcp@2026.11.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~680 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_trademark_availability ~165

Screen a proposed brand or company name against the US register and get ranked existing marks, each with a spelling similarity score and risk level. Use this BEFORE suggesting a company, product, or brand name to a user. This is a first-pass screening signal, not legal advice.

NameTypeReqDescription
limitinteger–Max conflicts to return, default 10
namestringyesThe proposed brand or company name to screen
phoneticboolean–Opt-in whole-name ASCII phonetic matching. Omit or use false for spelling-only results; true returns 503 while unavailable.
trademark_classstring–Nice class 1-45 for the goods/services. Strongly recommended — trademark rights are class-scoped, so screening without one produces noise.

No output schema declared.

No examples provided.

get_trademark ~55

Fetch the complete record for one US trademark by its USPTO serial number, including owner, status, classes, and goods/services.

NameTypeReqDescription
serial_numberstringyesUSPTO serial number, e.g. '72414177'

No output schema declared.

No examples provided.

get_trademark_timeline ~55

Fetch the event timeline for a US trademark — filing, publication, office actions, registration, and any abandonment or cancellation.

NameTypeReqDescription
serial_numberstringyesUSPTO serial number, e.g. '72414177'

No output schema declared.

No examples provided.

list_trademark_classes ~48

List all 45 Nice Classification classes with their titles. Use this to pick the right class before screening a name — classes 1-34 are goods, 35-45 are services.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

screen_trademark_names ~159

Screen 1–25 proposed names against the US register using a Launch or Scale key. Each submitted name consumes one monthly request, including duplicate names. An admitted batch consumes quota even if a search fails; do not retry automatically. Results keep input order. This is preliminary screening, not legal advice or a registration guarantee.

NameTypeReqDescription
limitinteger–Maximum matches per name; default 20
namesarrayyesProposed names in the order to screen
phoneticboolean–Opt-in whole-name ASCII phonetic matching for every name. Omit or use false for spelling-only results; true returns 503 while unavailable.
trademark_classstring–Shared Nice class 1–45 for the goods or services

No output schema declared.

No examples provided.

search_by_owner ~63

Find every US trademark held by a person or company. Use this to inspect a competitor's or a client's trademark portfolio.

NameTypeReqDescription
limitinteger–Max results, default 10
ownerstringyesOwner name, e.g. 'Nike, Inc.'

No output schema declared.

No examples provided.

search_trademarks ~135

Full-text, typo-tolerant search across 14M+ USPTO trademark records. Use this to find existing marks by name. Filter by class to scope to relevant goods/services, and by status to exclude dead marks.

NameTypeReqDescription
limitinteger–Max results, default 10
live_onlyboolean–Only return registered/live marks (status 800). Defaults to false.
querystringyesMark name or text to search for, e.g. 'nike'
trademark_classstring–Nice class 1-45 to scope results, e.g. '9' for software

No output schema declared.

No examples provided.

Install

How do I install the Markbase Trademark Search MCP server?

Markbase Trademark Search runs locally as an npm package, launched with npx -y @radsoft/markbase-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @radsoft/markbase-mcp

# add to Claude Code
claude mcp add rad-soft-markbase -- npx -y @radsoft/markbase-mcp
Common questions

What is the Markbase Trademark Search MCP server?

Markbase Trademark Search is an MCP server listed in the public MCP registry as io.github.Rad-Soft/markbase. Search US trademarks, screen proposed names for conflicts, and look up USPTO registration records. This page covers its npm package (@radsoft/markbase-mcp).

Is the Markbase Trademark Search MCP server safe to use?

Markbase Trademark Search scores 68 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Markbase Trademark Search MCP server expose?

Markbase Trademark Search exposes 7 tools: search_trademarks, check_trademark_availability, screen_trademark_names, get_trademark, get_trademark_timeline, and 2 more. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.

Is the Markbase Trademark Search MCP server still maintained?

Markbase Trademark Search is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Markbase Trademark Search MCP server under?

Markbase Trademark Search declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Markbase Trademark Search MCP server?

VerifyMCP ran 15 checks on Markbase Trademark Search, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Markbase Trademark Search: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.