IP Defender Trademark Monitoring MCP
REMOTE · WWW.IPDEFENDER.EU · SCANNED SEP 20
Trademark filing monitor across 40+ countries - detect filings that resemble your brand.
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 → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
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.
How do I install the IP Defender Trademark Monitoring MCP server?
IP Defender Trademark Monitoring MCP is a hosted endpoint at https://www.ipdefender.eu/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 · www.ipdefender.eu
claude mcp add --transport http webdevelopers-eu-ipdefender-mcp 'https://www.ipdefender.eu/mcp'
{
"mcpServers": {
"webdevelopers-eu-ipdefender-mcp": {
"url": "https://www.ipdefender.eu/mcp"
}
}
} {
"servers": {
"webdevelopers-eu-ipdefender-mcp": {
"type": "http",
"url": "https://www.ipdefender.eu/mcp"
}
}
} [mcp_servers.webdevelopers-eu-ipdefender-mcp] url = "https://www.ipdefender.eu/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"webdevelopers-eu-ipdefender-mcp": {
"type": "remote",
"url": "https://www.ipdefender.eu/mcp",
"enabled": true
}
}
} openclaw mcp add webdevelopers-eu-ipdefender-mcp --url 'https://www.ipdefender.eu/mcp' --transport streamable-http
mcp_servers:
webdevelopers-eu-ipdefender-mcp:
url: "https://www.ipdefender.eu/mcp" {
"McpServers": {
"webdevelopers-eu-ipdefender-mcp": {
"Transport": "http",
"Url": "https://www.ipdefender.eu/mcp"
}
}
} assistant mcp add webdevelopers-eu-ipdefender-mcp -t streamable-http -u 'https://www.ipdefender.eu/mcp'
{
"mcpServers": {
"webdevelopers-eu-ipdefender-mcp": {
"type": "http",
"url": "https://www.ipdefender.eu/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.
- 2 Sept 26 +3
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 30 Aug 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Aug 26 +3
- Stability: fail → pass ▲ security
- 26 Aug 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
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
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 20 Sept 2026 · Probed https://www.ipdefender.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ipdefender.eu | CN=YE1,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6bb695ab355879371cd84db9e6bc2625be5 |
| SANs: *.ipdefender.eu, ipdefender.eu | ||||||
| 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 www.ipdefender.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| ipdefender.eu. | absent | 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://www.ipdefender.eu/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://www.ipdefender.eu/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://www.ipdefender.eu/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://www.ipdefender.eu/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.ipdefender.eu/mcp |
| Authorisation server | https://www.ipdefender.eu |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ipdefender.eu/mcp | Auth required | 401 | |
| http (plaintext) | http://www.ipdefender.eu/mcp | HTTPS enforced | 301 | https://www.ipdefender.eu/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. 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 →
alert ~125
CRUD API for IP Defender alerts (trademark watch alerts). Create, read, update, delete, or list alerts. Each alert monitors a brand name across selected countries and reports conflicting trademark applications.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Alert payload. Required for 'create' and 'update' operations. Ignored for 'read', 'delete', and 'list'. |
| id | integer | – | Alert ID. Required for 'read', 'update', and 'delete' operations. Ignored for 'create' and 'list'. |
| op | string | yes | CRUD operation to perform on alerts. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Alert data. For 'list' it is an array of alert objects (summary form). For 'read', 'create', and 'update' it is a single alert object (complete form). For 'delete' it is a confirmation object {delete… |
No examples provided.
billing ~115
Retrieve billing information for the authenticated user: current daily service rate and account status (op='rate'), the list of invoices (op='invoices'), or a single invoice with line items and buyer details (op='invoiceDetail').
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | Invoice ID. Required for 'invoiceDetail'. Ignored for 'rate' and 'invoices'. |
| op | string | yes | Operation to perform: 'rate' for current billing rate; 'invoices' for the invoice list; 'invoiceDetail' for a single invoice. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | Billing data. Shape depends on op: 'rate' returns a rate object; 'invoices' returns an array of invoice summaries; 'invoiceDetail' returns a single invoice object with invoiceLines and buyer. |
No examples provided.
conflict ~186
List, read, or update IP Defender conflict records (conflicting trademark applications detected by an alert). Returns per-state counts and full conflict details including the conflicting mark's source, image, and match pairs.
| Name | Type | Req | Description |
|---|---|---|---|
| alertId | integer | – | Alert ID. When provided with op='list', only conflicts belonging to this alert are returned. Ignored for 'read' and 'update'. |
| data | object | – | Conflict payload. Required for 'update'. Ignored for 'list' and 'read'. |
| id | integer | – | Conflict ID. Required for 'read' and 'update'. Ignored for 'list'. |
| op | string | yes | Operation to perform: 'list' returns all conflicts for the user (or for a single alert when 'alertId' is given); 'read' returns one conflict with its parent alert; 'update' changes the state of one c… |
| Name | Type | Req | Description |
|---|---|---|---|
| alert | object | – | Parent alert object (op='read'). Same shape as the alert summary returned by the alert tool. |
| baseURL | string | yes | Base URL of the IP Defender server (e.g. 'https://www.ipdefender.eu'). All relative URLs in the response (imageURL, iconURL) must be prefixed with this baseURL to form complete URLs. For example, if… |
| counts | object | – | Per-state conflict counts (op='list'). Keys are state names; values are integers. |
| data | – | yes | Conflict data. For 'list' it is an array of conflict objects. For 'read' and 'update' it is a single conflict object. |
No examples provided.
getPricingList ~146
List all territories with pricing info for monitoring trademark in those territories. Billed daily, You only pay for active monitoring in your selected markets, with usage tracked on a daily basis for maximum flexibility. Your first statement arrives 30 days after activation, followed by quarterly billing thereafter. All monitored jurisdictions automatically include international trademarks (WIPO Madrid Protocol) at no extra cost. EU countries include trademarks registered in the European Union as a whole (European Union trade marks / EUTM) at no extra cost. Every plan includes 5 specialized AI watch agents and 11 detection layers, delivering unparalleled protection.
| Name | Type | Req | Description |
|---|---|---|---|
| _ | null | – | Reserved placeholder. The tool takes no arguments; send {}. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Response envelope from the ipd:countries handler. |
No examples provided.
settings ~182
Get or set the authenticated user's account settings (notification emails, billing emails, invoice address, given/family name, company details, etc.). op='get' reads requested properties; op='set' writes provided property values.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Property values to write (op='set'). Keys must be valid UserPropsEnum values. Ignored for 'get'. |
| op | string | yes | Operation to perform: 'get' reads settings; 'set' writes settings. |
| props | array | – | Property names to read (op='get'). Each must be a valid UserPropsEnum value: givenName, familyName, username, phone, billingEmails, invoiceAddress, paymentTerms, notificationEmails, notificationFrequ… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Requested settings values (op='get'). Keys are the property names requested in 'props'; values are the current values (strings, arrays, or objects depending on the property). Absent for op='set'. |
No examples provided.
What is the IP Defender Trademark Monitoring MCP server?
IP Defender Trademark Monitoring MCP is listed in the public MCP registry as io.github.webdevelopers-eu/ipdefender-mcp. Trademark filing monitor across 40+ countries - detect filings that resemble your brand. This page covers its hosted endpoint (https://www.ipdefender.eu/mcp).
Is the IP Defender Trademark Monitoring MCP server safe to use?
IP Defender Trademark Monitoring MCP 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 IP Defender Trademark Monitoring MCP server expose?
IP Defender Trademark Monitoring MCP exposes 5 tools: alert, billing, conflict, getPricingList, settings. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.
Does the IP Defender Trademark Monitoring MCP server require authentication?
Yes. IP Defender Trademark Monitoring MCP 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 IP Defender Trademark Monitoring MCP server still maintained?
IP Defender Trademark Monitoring MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.