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.

One1 Trademark Risk Check

REMOTE · ONE1.CN

Trademark conflict, logo look-alike and TRO enforcer checks for cross-border sellers.

Available components

0 this week 36 Trust /100

Last scanned (19 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

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

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Oct 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Stability: 0.50 → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 10 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “coverage_info” rewrote its description, which is the text the model reads security
    • Tool “graphic_trademark_search” rewrote its description, which is the text the model reads security
    • Tool “listing_scan” rewrote its description, which is the text the model reads security
    • Tool “trademark_lookup_by_serial” rewrote its description, which is the text the model reads security
    • Tool “trademark_owner_profile” rewrote its description, which is the text the model reads security
    • Tool “trademark_owner_search” rewrote its description, which is the text the model reads security
    • Tool “trademark_text_search” rewrote its description, which is the text the model reads security
    • Schema quality: 207 → 943 ▼ functional
    • Tool coverage: 0% → 33% ▲ functional
    • “coverage_info” reworded the description of “country” cosmetic
    • “graphic_trademark_search” reworded the description of “country” cosmetic
    • “listing_scan” reworded the description of “country” cosmetic
    • “trademark_lookup_by_serial” reworded the description of “country” cosmetic
    • “trademark_owner_profile” reworded the description of “country” cosmetic
    • “trademark_owner_search” reworded the description of “country” cosmetic
    • “trademark_text_search” reworded the description of “country” cosmetic
  • 29 Sept 26 0
    • Tool “graphic_trademark_search” rewrote its description, which is the text the model reads security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0

    First indexed and scored.

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 · Probed https://one1.cn/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=one1.cn CN=YE1,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA384 5082086fbb1d4e5dc3a333287f1f4807bcf
SANs: one1.cn, www.one1.cn
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of one1.cn. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cn. DS published 33094 8 Verified
one1.cn. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://one1.cn/.well-known/oauth-protected-resource/mcp", scope="mcp"

Bearer resource_metadata="https://one1.cn/.well-known/oauth-protected-resource/mcp", scope="mcp"
Header Value
www-authenticate Bearer resource_metadata="https://one1.cn/.well-known/oauth-protected-resource/mcp", scope="mcp"

Protected resource metadata

Document https://one1.cn/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://one1.cn/mcp
Authorisation server https://one1.cn

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://one1.cn/mcp Auth required 401
http (plaintext) http://one1.cn/mcp HTTPS enforced 301 https://one1.cn/mcp
MCP tools · 7 exposed · ~6,112 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
coverage_info ~796

查询 One1 已覆盖国家/地区的数据范围和覆盖限制;不证明每个工具均支持该辖区。 country: 省略或空串返回全部辖区摘要;纯空白按现有行为查询 US。非空时:单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–省略或空串返回全部辖区摘要;非空查单国;纯空白查询 US。单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, J…

No output schema declared.

No examples provided.

graphic_trademark_search ~862

按目标国家查询 One1 已覆盖的图形商标数据,返回视觉近似候选。 用于卖家查自家 Logo/图案是否撞已注册图形商标(CLIP 视觉相似 + 名录加权)。 image_url: 公网可访问的图片 URL(PNG/JPG)。 nice_class: 尼斯类别,可选。limit: 默认 10。 返回: {count, results:[{mark, visual_similarity, risk_level, applicant, legal_status}]}。 country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY…
image_urlstringyes–
limitinteger––
nice_classstring––

No output schema declared.

No examples provided.

listing_scan ~858

扫描 listing 的商标风险词。当前后端忽略 country,仅 US 可用;非 US 明确报错,不能声称已扫描目标国家。 用于卖家发品前一键自查整条 listing 标题是否含侵权商标词。 text: listing 标题或文案(可整段)。 nice_class: 尼斯商品类别号,可选。 返回: {summary:{高,中,低}, tro_count, hits:[{mark, risk_level, applicant, tro_alert?}]}。 country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY…
nice_classstring––
textstringyes–

No output schema declared.

No examples provided.

trademark_lookup_by_serial ~823

按目标国家查询 One1 已覆盖的商标数据,以该国数据库中的商标编号精确查询。 用于已知商标号(如收到侵权通知里的号)时直接查该标。 serial: 目标国库内编号;"78414956" 仅为 US 示例。 返回: {serial, found, result:{mark, legal_status, applicant, risk_level, ...}}。 country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY…
serialstringyes–

No output schema declared.

No examples provided.

trademark_owner_profile ~889

按目标国家查询 One1 已覆盖的商标数据,聚合权利人组合及库内维权信号。 用于卖家评估某品牌是否激进维权(批量起诉 Schedule A + 临时禁令 TRO 常冻结账户)、是否应高度规避。 owner: 权利人或品牌名,如 "Nike" 或 "YETI"。 返回: {owner, is_enforcer, enforcement{level,note,src}, total_marks, live_marks, top_classes[{nice,count}], tro_marks[], sample_marks[], risk_hint}。 is_enforcer=true 表示命中维权种子库,强烈建议规避;结果仅供参考,不构成法律意见。 country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY…
ownerstringyes–

No output schema declared.

No examples provided.

trademark_owner_search ~859

按目标国家查询 One1 已覆盖的商标数据,检索权利人/申请人名下记录。 用于做竞品权利人画像、查某公司商标布局、识别高频维权方。 owner: 权利人/公司名,如 "Nike, Inc."。 live_only: 仅 Live,默认 False。limit: 默认 20。 返回: {owner, count, results:[{mark, nice_class, legal_status, risk_level, tro_alert?}]}。 country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY…
limitinteger––
live_onlyboolean––
ownerstringyes–

No output schema declared.

No examples provided.

trademark_text_search ~1,025

按目标国家查询 One1 已覆盖的商标数据,检索品牌名的音/形/义近似候选。 用于卖家给产品起品牌名前,查是否与已注册商标冲突。 query: 要核查的品牌名或商标词,例如 "Nike"。 nice_class: 尼斯商品类别号(如 "025"=服装鞋帽),可选;提供则按同类目重排风险等级。 live_only: 仅返回有效(Live)注册,默认 False。 limit: 返回条数,默认 10。 ⚠️ 判读规则(重要):`count` 是返回的**最近邻条数**,受 limit 上限限制,**不是冲突数**—— 即使该词完全无人注册,仍可能返回低风险邻居。判断有无冲突请看 `has_conflicts` / `conflict_count`(= 风险等级为「高」的条数)。 ⚠️ `coverage.clearance_ok` 为 false 时,「无冲突」**不代表可注册**,必须结合当地检索。 返回: {query, conflict_count, has_conflicts, count, results:[...], coverage:{...}}。 country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

NameTypeReqDescription
countrystring–单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY…
limitinteger––
live_onlyboolean––
nice_classstring––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the One1 Trademark Risk Check MCP server?

One1 Trademark Risk Check is a hosted endpoint at https://one1.cn/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · one1.cn

# add to Claude Code
claude mcp add --transport http cn-one1-trademark 'https://one1.cn/mcp'
Common questions

What is the One1 Trademark Risk Check MCP server?

One1 Trademark Risk Check is an MCP server listed in the public MCP registry as cn.one1/trademark. Trademark conflict, logo look-alike and TRO enforcer checks for cross-border sellers. This page covers its hosted endpoint (https://one1.cn/mcp).

Is the One1 Trademark Risk Check MCP server safe to use?

One1 Trademark Risk Check scores 36 out of 100 on VerifyMCP. 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 One1 Trademark Risk Check MCP server expose?

One1 Trademark Risk Check exposes 7 tools: trademark_text_search, listing_scan, trademark_lookup_by_serial, trademark_owner_search, graphic_trademark_search, and 2 more. Their descriptions and schemas cost roughly 6,112 tokens of context every time the server is loaded.

Does the One1 Trademark Risk Check MCP server require authentication?

Yes. One1 Trademark Risk Check asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the One1 Trademark Risk Check MCP server still maintained?

One1 Trademark Risk Check 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 did VerifyMCP test on the One1 Trademark Risk Check MCP server?

VerifyMCP ran 5 checks on One1 Trademark Risk Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about One1 Trademark Risk Check: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.