# Global FinReg (remote · api2.globalfinreg.com)

Look up any LEI; register, renew and transfer LEIs and get invoices for a Global FinReg user.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api2.globalfinreg.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-globalfinreg-lei/api2.md), [page](https://verifymcp.io/servers/com-globalfinreg-lei/api2)
- remote · `api2.globalfinreg.com`: 39/100, [markdown](https://verifymcp.io/servers/com-globalfinreg-lei/mcp-account.md), [page](https://verifymcp.io/servers/com-globalfinreg-lei/mcp-account)

## Channel facts

- Endpoint: `https://api2.globalfinreg.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1314 tokens (~262/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Global FinReg MCP server?

Global FinReg is a hosted endpoint at https://api2.globalfinreg.com/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.

### Claude

```bash
claude mcp add --transport http com-globalfinreg-lei 'https://api2.globalfinreg.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-globalfinreg-lei": {
      "url": "https://api2.globalfinreg.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-globalfinreg-lei": {
      "type": "http",
      "url": "https://api2.globalfinreg.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-globalfinreg-lei]
url = "https://api2.globalfinreg.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-globalfinreg-lei": {
      "type": "remote",
      "url": "https://api2.globalfinreg.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-globalfinreg-lei --url 'https://api2.globalfinreg.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-globalfinreg-lei:
    url: "https://api2.globalfinreg.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-globalfinreg-lei": {
      "Transport": "http",
      "Url": "https://api2.globalfinreg.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-globalfinreg-lei -t streamable-http -u 'https://api2.globalfinreg.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-globalfinreg-lei": {
      "type": "http",
      "url": "https://api2.globalfinreg.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 86, +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.

### 2026-11-02 (score 85, +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.

### 2026-10-31 (score 84, +1)

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

### 2026-10-29 (score 83, +1)

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

### 2026-10-27 (score 82, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-24 (score 81, +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.

### 2026-10-22 (score 80, +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.

### 2026-10-20 (score 79, +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.

## MCP tools (5)

### `get_prices` (~86 tokens)

Get LEI prices

Returns Global FinReg's LEI prices in every supported currency, excluding VAT: for a new registration and for a renewal, for 1, 3 and 5 years, each as pricePerYear and total for the whole period; and the optional fully assisted service. For the exact total for one LEI, including VAT, use get_registration_quote or get_renewal_quote.

### `create_user` (~257 tokens)

Create a Global FinReg account

Creates a Global FinReg account for a user from their email address, so they can order and manage LEIs. GFR emails the address a link to set a password; you get no access to the account from this tool. After the user has set a password, register for access with /auth.md and use the account tools. If the address already has an account nothing changes, and the answer is the same. Ask the user for their email address, first name and last name, and confirm them with them before calling.

Input parameters:

- `currencyCode` (string): Currency for prices and invoices, e.g. EUR, DKK, SEK, NOK, USD, GBP. Default EUR.
- `email` (string, required): The user's email address. The account and all GFR emails use it.
- `firstName` (string, required): The user's first name, as the user gave it. Required.
- `languageCode` (string): Language code for the account, e.g. en, da, nn (Norwegian), sv, de, fr. The welcome email is in en, da, nn or sv, otherwise English. Default en.
- `lastName` (string, required): The user's last name, as the user gave it. Required.

### `search_lei_by_company_name` (~87 tokens)

Search LEI by company name

Searches the global LEI register by legal entity name. Returns matching entities with their LEI, country and a link to the entity's GlobalFinReg lookup page.

Input parameters:

- `limit` (integer): Maximum number of results, 1 to 50.
- `query` (string, required): The legal name (or part of it) of the entity, at least 3 characters.

### `get_lei_record` (~82 tokens)

Get LEI record

Returns the registration record of an LEI from the global LEI register: legal name, legal and headquarters address, jurisdiction, legal form, entity and registration status, registration and renewal dates and the managing LOU.

Input parameters:

- `lei` (string, required): The 20-character Legal Entity Identifier, e.g. 89450060XX5ILUURV330.

### `lookup_legal_form` (~144 tokens)

Look up legal form

Looks up an entity legal form (ISO 20275 ELF code list) in a country: by ELF code first, otherwise by the legal form's local name, optionally within a region of the country.

Input parameters:

- `countryCode` (string, required): ISO 3166-1 alpha-2 country code, e.g. DK.
- `elfCode` (string): The 4-character ELF code, e.g. H8VP.
- `localName` (string): The legal form's local name, e.g. Anpartsselskab.
- `regionCode` (string): ISO 3166-2 region code, for countries whose legal forms differ by region.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-globalfinreg-lei/api2#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 75
- 2026-10-09: 74

## Common questions

### What is the Global FinReg MCP server?

Global FinReg is an MCP server listed in the public MCP registry as com.globalfinreg/lei. Look up any LEI; register, renew and transfer LEIs and get invoices for a Global FinReg user. This page covers its hosted endpoint (https://api2.globalfinreg.com/mcp).

### Is the Global FinReg MCP server safe to use?

Global FinReg scores 86 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 Global FinReg MCP server expose?

Global FinReg exposes 5 tools: get_prices, create_user, search_lei_by_company_name, get_lei_record, lookup_legal_form. Their descriptions and schemas cost roughly 656 tokens of context every time the server is loaded.

### Does the Global FinReg MCP server require authentication?

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

### Is the Global FinReg MCP server still maintained?

Global FinReg 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.

## Links

- Remote endpoint: https://api2.globalfinreg.com/mcp
- Website: https://www.globalfinreg.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-globalfinreg-lei/api2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-globalfinreg-lei/api2.json
- HTML version of this page: https://verifymcp.io/servers/com-globalfinreg-lei/api2