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.

Sisoco One LEI

REMOTE · API.SISOCO.CO.UK

No sign-up. LEI lookup and direct/ultimate parent companies (GLEIF), and LEI to UK/FR company.

Available components

73 Trust /100

Last scanned (22 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

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 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 686 tokens (~228/item across 3 items; 3 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 Management3
  • Stability observed for 1 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 72

    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://api.sisoco.co.uk/mcp/lei

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sisoco.co.uk CN=YE2,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA384 58de504f5b0c0a87e284c580871a901e3f5
SANs: *.sisoco.co.uk, sisoco.co.uk
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 api.sisoco.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
sisoco.co.uk. No DS 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=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.sisoco.co.uk/mcp/lei Verified 200
http (plaintext) http://api.sisoco.co.uk/mcp/lei HTTPS enforced 301 https://api.sisoco.co.uk/mcp/lei
MCP tools · 3 exposed · ~478 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
sisoco_check_company ~215

Start here. Resolves a UK company number, French SIREN, LEI, or a company name with country (GB or FR) to one company, and returns its identity, current signals (e.g. accounts overdue, insolvency notice, sanctions possible match for the company or its GLEIF direct and ultimate parents) and events of the last 90 days, each with its official source URL. A name that matches several companies returns error ambiguous_match with ranked candidates; call again with a candidate's number. Facts from official registers, never a score or a verdict; sanctions results are possible matches that need the user's own review. Cost: 1 lookup from the monthly quota (same as GET /v1/check).

NameTypeReqDescription
companystringyesRegistry number (e.g. 00445790, SIREN 552032534), LEI, or a company name
countrystring–ISO 3166-1 alpha-2 (GB, FR); needed for name searches
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

sisoco_get_lei_parents ~140

Returns the direct and ultimate accounting-consolidation parents reported to GLEIF (Level 2) for a Legal Entity Identifier, each with its LEI and name, or the reason no parent is reported (e.g. NATURAL_PERSONS, NON_CONSOLIDATING, NO_KNOWN_PERSON). Works for any country. Source: GLEIF (CC0). Cost: 1 lookup (same as GET /v1/entities/lei/{lei}/parents).

NameTypeReqDescription
leistringyesLegal Entity Identifier (20 characters), e.g. 2138002P5RNKC5W2JZ46
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

sisoco_get_lei_record ~123

Returns the GLEIF record for a Legal Entity Identifier: legal name, registered and headquarters addresses, legal form, registration authority and number, entity and registration status (e.g. LAPSED). For its parent companies call sisoco_get_lei_parents. Source: GLEIF (CC0). Cost: 1 lookup (same as GET /v1/entities/lei/{lei}).

NameTypeReqDescription
leistringyesLegal Entity Identifier (20 characters), e.g. 2138002P5RNKC5W2JZ46
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

Install

How do I install the Sisoco One LEI MCP server?

Sisoco One LEI is a hosted endpoint at https://api.sisoco.co.uk/mcp/lei, 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 · api.sisoco.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-sisoco-gleif-lei-parent-company 'https://api.sisoco.co.uk/mcp/lei'
Common questions

What is the Sisoco One LEI MCP server?

Sisoco One LEI is an MCP server listed in the public MCP registry as uk.co.sisoco/gleif-lei-parent-company. No sign-up. LEI lookup and direct/ultimate parent companies (GLEIF), and LEI to UK/FR company. This page covers its hosted endpoint (https://api.sisoco.co.uk/mcp/lei).

Is the Sisoco One LEI MCP server safe to use?

Sisoco One LEI scores 73 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 Sisoco One LEI MCP server expose?

Sisoco One LEI exposes 3 tools: sisoco_check_company, sisoco_get_lei_parents, sisoco_get_lei_record. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.

Does the Sisoco One LEI MCP server require authentication?

No. We connected to Sisoco One LEI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sisoco One LEI MCP server still maintained?

Sisoco One LEI 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 Sisoco One LEI MCP server?

VerifyMCP ran 13 checks on Sisoco One LEI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.