Zovo LEI Lookup
REMOTE · LEI-LOOKUP.ZOVO.ONE
LEI checks and renewal dates
Available components
Last scanned (10 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 466 tokens (~116/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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 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.
- 2 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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 75
First indexed and scored.
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 · Probed https://lei-lookup.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 31ec26c69baf08600e19d3f1f14227c0 |
| SANs: zovo.one, lei-lookup.zovo.one, *.lei-lookup.zovo.one | ||||||
| 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 lei-lookup.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lei-lookup.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://lei-lookup.zovo.one/mcp | HTTPS enforced | 301 | https://lei-lookup.zovo.one/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 →
find_leis_by_name Find LEIs by name ~118
Use this when the user wants to find lei by company name, an lei search, or a legal entity identifier lookup. Reads live public-index candidates and returns XLSX/CSV files. Up to 25 names of 2–200 characters with optional legal-address country; up to five candidates per name; ambiguous matches need the user to choose. Do not use for ownership verification.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | Up to 25 company names and optional country. Example: [{"name":"Siemens Aktiengesellschaft","country":"DE"}]. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| golden_copy_publish_date | string | yes | – |
| kind | string | yes | – |
| note | string | yes | – |
| preview_rows | number | yes | – |
| retrieved | string | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| summary | object | yes | – |
| today | string | yes | – |
| total_rows | number | yes | – |
No examples provided.
get_lei_parents Get LEI parents ~116
Use this when the user wants an lei parent company, lei lookup, or legal entity identifier lookup for reported accounting-consolidation parents. Reads live public-index data and returns XLSX/CSV files. Up to 10 LEIs, with direct and ultimate parent or reporting-exception reasons. Do not use for a full ownership chart or beneficial ownership determination.
| Name | Type | Req | Description |
|---|---|---|---|
| leis | array | yes | Up to 10 LEIs for parent lookup. Example: ["5493001KJTIIGC8Y1R12"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| golden_copy_publish_date | string | yes | – |
| kind | string | yes | – |
| note | string | yes | – |
| preview_rows | number | yes | – |
| retrieved | string | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| summary | object | yes | – |
| today | string | yes | – |
| total_rows | number | yes | – |
No examples provided.
verify_leis Verify LEIs ~165
Use this when the user wants an lei lookup, lei check, or to verify lei numbers and check an lei renewal date or lapsed lei check. Reads live public-index data and returns dated XLSX/CSV files. Up to 100 LEIs; optional renewal date; invalid and duplicate rows stay in the report. Do not use for legal or regulatory advice.
| Name | Type | Req | Description |
|---|---|---|---|
| leis | array | yes | LEIs to verify, up to 100. Example: ["HWUPKR0MPOU8FGXBT394", "5493001KJTIIGC8Y1R12"]. |
| today | string | – | Renewal check date YYYY-MM-DD, 2000–2100; default current UTC date. Example: 2026-12-27. |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | object | yes | – |
| golden_copy_publish_date | string | yes | – |
| kind | string | yes | – |
| note | string | yes | – |
| preview_rows | number | yes | – |
| retrieved | string | yes | – |
| rows | array | yes | – |
| source | string | yes | – |
| source_url | string | yes | – |
| summary | object | yes | – |
| today | string | yes | – |
| total_rows | number | yes | – |
No examples provided.
How do I install the Zovo LEI Lookup MCP server?
Zovo LEI Lookup is a hosted endpoint at https://lei-lookup.zovo.one/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 · lei-lookup.zovo.one
claude mcp add --transport http theluckystrike-lei-lookup 'https://lei-lookup.zovo.one/mcp'
What is the Zovo LEI Lookup MCP server?
Zovo LEI Lookup is an MCP server listed in the public MCP registry as io.github.theluckystrike/lei-lookup. LEI checks and renewal dates. This page covers its hosted endpoint (https://lei-lookup.zovo.one/mcp).
Is the Zovo LEI Lookup MCP server safe to use?
Zovo LEI Lookup scores 81 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 Zovo LEI Lookup MCP server expose?
Zovo LEI Lookup exposes 3 tools: verify_leis, find_leis_by_name, get_lei_parents. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.
Does the Zovo LEI Lookup MCP server require authentication?
No. We connected to Zovo LEI Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo LEI Lookup MCP server still maintained?
Zovo LEI Lookup 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.