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.

European IP Data & Analytics — IPRATE

REMOTE · MCP.IPRATE.EU · SCANNED SEP 24

Free anonymous selections from released European IP profiles, rankings, and market statistics.

Available components

+3 this week 78 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 523 tokens (~130/item across 4 items; 4 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 Management90
  • Stability observed for 27 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the European IP Data & Analytics — IPRATE MCP server?

European IP Data & Analytics — IPRATE is a hosted endpoint at https://mcp.iprate.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 · mcp.iprate.eu

# add to Claude Code
claude mcp add --transport http eu-iprate-ip-analytics 'https://mcp.iprate.eu/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "eu-iprate-ip-analytics": {
      "url": "https://mcp.iprate.eu/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "eu-iprate-ip-analytics": {
      "type": "http",
      "url": "https://mcp.iprate.eu/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.eu-iprate-ip-analytics]
url = "https://mcp.iprate.eu/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-iprate-ip-analytics": {
      "type": "remote",
      "url": "https://mcp.iprate.eu/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add eu-iprate-ip-analytics --url 'https://mcp.iprate.eu/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  eu-iprate-ip-analytics:
    url: "https://mcp.iprate.eu/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "eu-iprate-ip-analytics": {
      "Transport": "http",
      "Url": "https://mcp.iprate.eu/mcp"
    }
  }
}
# add to Vellum
assistant mcp add eu-iprate-ip-analytics -t streamable-http -u 'https://mcp.iprate.eu/mcp'
// mcp.json
{
  "mcpServers": {
    "eu-iprate-ip-analytics": {
      "type": "http",
      "url": "https://mcp.iprate.eu/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 24 Sept 26 +1

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

  • 22 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

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 24 Sept 2026 · Probed https://mcp.iprate.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=iprate.eu CN=WE1,O=Google Trust Services,C=US 28 Aug 2026 26 Nov 2026 ECDSA 256 ECDSA-SHA256 d58400b192ff3f990e47b3f71c5254e4
SANs: iprate.eu, mcp.iprate.eu, *.mcp.iprate.eu
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.iprate.eu. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
eu. present 35926 8 Verified
iprate.eu. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.iprate.eu/mcp Verified 200
http (plaintext) http://mcp.iprate.eu/mcp Inconclusive 405
MCP tools · 4 exposed · ~471 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
find_ip_representatives ~197

Find up to five firms or attorneys from the selected static release. Use this for a name, jurisdiction, right type, released leading Nice class, or released leading-client match. At least one filter is required.

NameTypeReqDescription
client_namestring–Named client to match against leading-client evidence already public on profiles.
jurisdictionstring–ISO 3166-1 alpha-2 jurisdiction code, or EU for the European route.
limitinteger–Maximum results; hard maximum five.
namestring–Representative name fragment, matched against released profile identities.
nice_classesarray–One to five Nice class numbers; trademark only.
representative_typestring–Return firms, attorneys, or both.
right_typestring–IP right type.
tierstring–Optional released national or European route.
windowstring–Optional released long or recent analytical window.

No output schema declared.

No examples provided.

get_ip_market_snapshot ~98

Return one already-computed static cohort snapshot and up to five leading released firms. No dates, raw records, SQL, arbitrary grouping, or free-form question are accepted.

NameTypeReqDescription
jurisdictionstringyesISO 3166-1 alpha-2 jurisdiction code.
right_typestringyesIP right type.
tierstringyesReleased national or European route.
windowstringyesReleased long or recent analytical window.

No output schema declared.

No examples provided.

get_ip_representative_profile ~82

Return the bounded public evidence profile for one published IP firm or attorney. Provide exactly one numeric representative_id or public profile slug.

NameTypeReqDescription
representative_idinteger–Published representative numeric ID.
representative_typestring–Disambiguates an identifier shared by firm and attorney profiles.
slugstring–Exact public IPRATE profile slug.

No output schema declared.

No examples provided.

get_iprate_coverage ~94

Explain which static release cohorts support a jurisdiction and IP-right question. Returns held, partial, or not-covered state, release assets, counts, fields, and incidents.

NameTypeReqDescription
jurisdictionstring–Optional ISO 3166-1 alpha-2 code, or EU for the European route.
right_typestring–Optional IP right type.
tierstring–Optional released national or European route.

No output schema declared.

No examples provided.

Common questions

What is the European IP Data & Analytics — IPRATE MCP server?

European IP Data & Analytics — IPRATE is an MCP server listed in the public MCP registry as eu.iprate/ip-analytics. Free anonymous selections from released European IP profiles, rankings, and market statistics. This page covers its hosted endpoint (https://mcp.iprate.eu/mcp).

Is the European IP Data & Analytics — IPRATE MCP server safe to use?

European IP Data & Analytics — IPRATE scores 78 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 European IP Data & Analytics — IPRATE MCP server expose?

European IP Data & Analytics — IPRATE exposes 4 tools: find_ip_representatives, get_ip_representative_profile, get_ip_market_snapshot, get_iprate_coverage. Their descriptions and schemas cost roughly 471 tokens of context every time the server is loaded.

Does the European IP Data & Analytics — IPRATE MCP server require authentication?

No. We connected to European IP Data & Analytics — IPRATE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the European IP Data & Analytics — IPRATE MCP server still maintained?

European IP Data & Analytics — IPRATE is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.