Global FinReg
REMOTE · API2.GLOBALFINREG.COM · 2 COMPONENTS
Look up any LEI; register, renew and transfer LEIs and get invoices for a Global FinReg user.
Available components
Last scanned (4 hours ago)
Scores higher than 93% 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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 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.
- 2 Nov 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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 24 Oct 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.
- 22 Oct 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.
- 20 Oct 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.
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://api2.globalfinreg.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=globalfinreg.com | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9f3f8fbf864df64f0e507c14616877c1 |
| SANs: globalfinreg.com, *.globalfinreg.com | ||||||
| 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 secure
Validation of api2.globalfinreg.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| globalfinreg.com. | present | 2371 | 13 | Verified |
| api2.globalfinreg.com. | Verified address RRset verified with the apex keys |
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=2592000 |
| content-security-policy | default-src 'self';img-src data: https:;object-src 'none'; script-src https://stackpath.bootstrapcdn.com/ 'self' 'unsafe-inline' 'unsafe-eval' 'sha256-Tui7QoFlnLXkJCSl1/JvEZdIXTmBttnWNxzJpXomQjg=' 'sha256-nO75Ve4Rnx+D6IfPhLX42vIHEeOy2bXO9nyfmNB52Js=' 'sha256-aZx6raX8e1obRwSWfQvh2zSrcQ1KDYQxDieoMHf/Q3s=' 'sha256-LvV6zHWxhtV0xq7r5njB1oVYc8HX2qdo3IYDjJXTnJw=';style-src https://stackpath.bootstrapcdn.com/ 'self' 'unsafe-inline'; upgrade-insecure-requests; connect-src 'self' https://securetoken.google.com https://securetoken.google.com/live-swisscom https://identitytoolkit.googleapis.com; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api2.globalfinreg.com/mcp | Verified | 200 | |
| http (plaintext) | http://api2.globalfinreg.com/mcp | HTTPS enforced | 301 | https://api2.globalfinreg.com/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 →
create_user Create a Global FinReg account ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currencyCode | string | – | Currency for prices and invoices, e.g. EUR, DKK, SEK, NOK, USD, GBP. Default EUR. |
| string | yes | The user's email address. The account and all GFR emails use it. | |
| firstName | string | yes | 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 | yes | The user's last name, as the user gave it. Required. |
No output schema declared.
No examples provided.
get_lei_record Get LEI record ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lei | string | yes | The 20-character Legal Entity Identifier, e.g. 89450060XX5ILUURV330. |
No output schema declared.
No examples provided.
get_prices Get LEI prices ~86
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_legal_form Look up legal form ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | yes | 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. |
No output schema declared.
No examples provided.
search_lei_by_company_name Search LEI by company name ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results, 1 to 50. |
| query | string | yes | The legal name (or part of it) of the entity, at least 3 characters. |
No output schema declared.
No examples provided.
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.
remote · api2.globalfinreg.com
claude mcp add --transport http com-globalfinreg-lei 'https://api2.globalfinreg.com/mcp'
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.