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.

Euipo

NPM · @PIPEWORX/MCP-EUIPO · 2 COMPONENTS

EUIPO MCP — EU trademarks, registered Community designs, and the shared reference registers the…

81 Trust /100

Last scanned (8 hours ago)

Scores higher than 69% of npm servers

Category Documents and Files

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-euipo). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2034 tokens (~290/item across 7 items; 7 tools + 0 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 Management20
  • Stability observed for 6 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 8 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 (16)

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

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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 1 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 78

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-euipo@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-euipo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-euipo/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3635932047
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7cde274109d10c71e3b13fb30d454a0f1411f94e4ceb35867521ccbb668279a2101ba52731097c9d353a2f65170b0d170a7758575e61e66a224853e6c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,981 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
euipo_search_designs ~323

Search registered Community designs (RCD) at the EUIPO — "find registered EU designs owned by Adidas in Locarno class 02". Use for design-filing landscape and competitor design portfolios. Returns matching designs (design number, indication of product, status, owner, Locarno classes, filing date) plus raw. Example: euipo_search_designs({ owner: "adidas", locarno_classes: ["02"], _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
indicationstring–Indication of product / design keyword to match (wildcards added automatically), e.g. "footwear".
locarno_classesarray–Locarno classification classes to filter by, e.g. ["02", "09"].
ownerstring–Design owner / applicant name to match, e.g. "adidas".
pageinteger–Zero-based page index for pagination (default 0).
querystring–Advanced: raw RSQL filter passed through verbatim (e.g. indicationOfProduct=="*footwear*";locarnoClasses=in=(02)). Overrides the friendly params above.
sizeinteger–Max results per page (default 20, max 100).
statusstring–Design status filter, e.g. "REGISTERED", "EXPIRED". Comma-separate for multiple.

No output schema declared.

No examples provided.

euipo_search_goods_services ~322

Explore the EUIPO's harmonised Nice goods-and-services classification (TMClass) — "find accepted goods-and-services terms for 'software' in Nice class 9". Use when preparing a trademark filing or checking whether a term is already a recognised, pre-classified term. Returns matching terms with their Nice class and concept id, plus raw. Example: euipo_search_goods_services({ term: "software", nice_class: 9, language: "en", _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
include_term_variantsboolean–Include term variants in the results (default false).
languagestring–EU official language code for the search and results, e.g. "en", "es", "de", "fr". Required by the upstream API; defaults to "en".
nice_classarray–Nice classification class number(s) to restrict the search to, e.g. [9] or [9, 42]. Also accepts a single integer.
pageinteger–Zero-based page index for pagination (default 0).
parent_concept_idstring–Restrict to children of this taxonomy concept id (for browsing the classification tree).
sizeinteger–Max results per page (default 20).
termstring–Text to search for within goods-and-services terms, e.g. "software".

No output schema declared.

No examples provided.

euipo_search_persons ~323

Search applicants or representatives on record with the EUIPO for trademark/design procedures — "find the EUIPO representative record for a named law firm". Each row carries its role (e.g. APPLICANT_BUSINESS, APPLICANT_INDIVIDUAL, REPRESENTATIVE_EUIPO_PROFESSIONAL) and its source. Privacy: street/city/postal-code address details are withheld for individual persons — only country-level location is kept; business/association entities keep their registered address. Example: euipo_search_persons({ name: "adidas", role: "applicant", country: "DE", _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
citystring–City to filter by, e.g. "Alicante". Only meaningful for business/association entities (withheld for individuals in the response).
countrystring–ISO 3166-1 alpha-2 country code to filter by, e.g. "DE", "US".
namestring–Name to search for, e.g. "adidas" or a representative's firm/individual name.
pageinteger–Zero-based page index for pagination (default 0).
rolestring–Which EUIPO person register to search: "applicant" (default) or "representative".
sizeinteger–Max results per page (default 20).

No output schema declared.

No examples provided.

euipo_search_product_indications ~294

Search the EUIPO's harmonised Locarno product-indications classification (DSClass) used for registered Community design filings — "find accepted design indications for 'chair'". Returns matching indications with their Locarno class/subclass and concept id, plus raw. Example: euipo_search_product_indications({ term: "chair", locarno_class: 6, language: "en", _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
languagestring–EU official language code for the search and results, e.g. "en". Required by the upstream API; defaults to "en".
locarno_classinteger–Locarno classification class number to restrict the search to, e.g. 6.
locarno_subclassinteger–Locarno classification subclass number (requires locarno_class).
pageinteger–Zero-based page index for pagination (default 0).
parent_concept_idstring–Restrict to children of this taxonomy concept id (for browsing the classification tree).
sizeinteger–Max results per page (default 20).
termstring–Text to search for within product-indication terms, e.g. "chair".

No output schema declared.

No examples provided.

euipo_search_trademarks ~333

Search EU trademarks (EUTM) at the EUIPO — "find EU trademarks containing NIKE in Nice classes 9 and 25". Use for EU brand clearance and competitor trademark portfolios. Returns matching marks (application number, mark text, status, owner, Nice classes, filing date) plus raw. Example: euipo_search_trademarks({ verbal_element: "nike", nice_classes: [9, 25], status: "REGISTERED", _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
applicantstring–Applicant / owner name to match, e.g. "Nike Innovate".
nice_classesarray–Nice classification classes to filter by, e.g. [9, 25].
pageinteger–Zero-based page index for pagination (default 0).
querystring–Advanced: raw RSQL filter passed through verbatim (e.g. verbalElement=="*nike*";niceClasses=in=(9,25)). Overrides the friendly params above.
sizeinteger–Max results per page (default 20, max 100).
statusstring–Trademark status filter, e.g. "REGISTERED", "APPLICATION_FILED", "EXPIRED". Comma-separate for multiple.
verbal_elementstring–Text/word element of the mark to match (wildcards added automatically), e.g. "nike". Multi-word values are quoted safely.

No output schema declared.

No examples provided.

euipo_trademark ~145

Retrieve a single EU trademark by its application or registration number from the EUIPO — "look up EUTM 018123456". Returns the full record (mark text, status, owner/representative, Nice classes, goods & services, filing/registration/expiry dates) plus raw. Example: euipo_trademark({ number: "018123456", _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
numberstringyesEUTM application or registration number, e.g. "018123456".

No output schema declared.

No examples provided.

euipo_validate_goods_services ~241

Validate a list of goods-and-services terms against the EUIPO's harmonised database (TMClass) — checks whether each term is a recognised ("harmonized") term, and flags invalid characters, duplicates, forbidden terms, and length problems. Use before filing to catch terms an examiner would object to. Returns per-term accepted/not-accepted status plus raw. Example: euipo_validate_goods_services({ terms: ["computer software", "C@ts and dog$"], nice_class: 9, language: "en", _apiKey: "client_id:client_secret" })

NameTypeReqDescription
_apiKeystringyesEUIPO OAuth credentials as "client_id:client_secret" from dev.euipo.europa.eu.
languagestring–Language the terms are written in, e.g. "en". Required by the upstream API; defaults to "en".
nice_classinteger–Nice classification class the terms belong to, e.g. 9. The upstream validates terms per class.
termsarrayyesGoods-and-services terms to validate, e.g. ["computer software", "downloadable mobile applications"].

No output schema declared.

No examples provided.

Install

How do I install the Euipo MCP server?

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

npm · @pipeworx/mcp-euipo

# add to Claude Code
claude mcp add pipeworx-io-euipo -- npx -y @pipeworx/mcp-euipo
Common questions

What is the Euipo MCP server?

Euipo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/euipo. EUIPO MCP, EU trademarks, registered Community designs, and the shared reference registers the… This page covers its npm package (@pipeworx/mcp-euipo).

Is the Euipo MCP server safe to use?

Euipo scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Euipo MCP server expose?

Euipo exposes 7 tools: euipo_search_trademarks, euipo_trademark, euipo_search_designs, euipo_search_goods_services, euipo_validate_goods_services, and 2 more. Their descriptions and schemas cost roughly 1,981 tokens of context every time the server is loaded.

Is the Euipo MCP server still maintained?

Euipo is still listed as active in the MCP registry. We last reached this channel on 5 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 Euipo MCP server under?

Euipo 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 Euipo MCP server?

VerifyMCP ran 16 checks on Euipo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.