auregistre
REMOTE · AUREGISTRE.FR
French companies: dated changes and insolvencies (BODACC), filed accounts by year (INPI). No key.
Available components
Last scanned (13 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 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. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1533 tokens (~219/item across 7 items; 6 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Oct 26 0
- Tool coverage: 17% → 100% ▲ functional
- Tool “get_french_company_ademe_grants” now declares an output schema ▲ functional
- Tool “get_french_company_announcements” now declares an output schema ▲ functional
- Tool “get_french_company_financials” now declares an output schema ▲ functional
- Tool “get_french_company_state_aid” now declares an output schema ▲ functional
- Tool “get_french_company_timeline” now declares an output schema ▲ functional
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1338 → 1533 ▼ functional
- New tool “get_french_company_state_aid” functional
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 25% → 20% ▼ functional
- Schema quality: 1114 → 1338 ▼ functional
- New tool “get_french_company_ademe_grants” functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 33% → 25% ▼ functional
- Schema quality: 838 → 1114 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.1.1 functional
- New tool “get_french_company_financials” functional
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 6 Nov 2026 · Probed https://auregistre.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=auregistre.fr | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 24b29242ec1cac73138b61a3867f3fc7 |
| SANs: auregistre.fr, develop.auregistre.fr, *.develop.auregistre.fr | ||||||
| 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 auregistre.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| auregistre.fr. | 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 |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://auregistre.fr/mcp | Verified | 200 | |
| http (plaintext) | http://auregistre.fr/mcp | HTTPS enforced | 301 | https://auregistre.fr/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 →
get_french_company_ademe_grants ADEME grants received by a French company ~201
The grants the ADEME, the French ecological transition agency, awarded to one French company since 2021, from its open dataset of financial aid: date of the agreement, amount in euros, purpose, aid scheme and decision reference, most recent first, with the total count. Use this to answer "did X receive public aid from the ADEME", "what subsidies did X get for its energy transition". The dataset covers the ADEME alone: it is not all the public money a company received, and a company with no ADEME grant may have received aid from another body. Grants are matched on the SIRET, never on the name.
| Name | Type | Req | Description |
|---|---|---|---|
| siren | string | yes | The nine-digit SIREN of a French legal entity. Spaces, dots and dashes are accepted. This is not a SIRET: drop the last five digits of a SIRET to get the SIREN. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| empreinte | string | yes | – |
| fait | object | yes | – |
| source | object | yes | – |
No examples provided.
get_french_company_announcements What the gazette published recently ~197
What the French official gazette printed about companies you already track, since a date. Answers "did anything happen to these companies", "any news on X since my last check". Up to 20 companies per call. Each one spends one unit of the rate limit (30 per minute per address), so pass them in ONE call rather than one call each. Entries are filtered on the PUBLICATION date, not the date of the act. The two differ by 16 days at the median, so a window filtered on the act would miss a judgment ruled before your last visit and printed after. An empty list means nothing was published, not that nothing happened.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Publication date to look back to, ISO 8601. Defaults to 30 days ago. |
| siren | array | yes | The companies to look at. One call for all of them, not one call each. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| empreinte | string | yes | – |
| fait | object | yes | – |
| source | object | yes | – |
No examples provided.
get_french_company_financials French company filed accounts ~240
The annual accounts one French company filed with the business register, fiscal year by fiscal year: revenue, gross margin, EBITDA, EBIT, net income, and the thirteen ratios the INPI computes from them (margins, financial autonomy, debt, liquidity, working capital, customer and supplier payment delays). Use this to answer "what is the revenue of X", "is X profitable", "how has the turnover of X evolved", "how indebted is X". Accounts of the legal entity under this SIREN and consolidated accounts of its group are listed apart and NEVER add up: a holding files a revenue of zero beside a group revenue in the billions. Quote the perimeter with the figure. Filings kept confidential are not listed, and a missing fiscal year is not a fiscal year at zero. Amounts are in euros as filed.
| Name | Type | Req | Description |
|---|---|---|---|
| siren | string | yes | The nine-digit SIREN of a French legal entity. Spaces, dots and dashes are accepted. This is not a SIRET: drop the last five digits of a SIRET to get the SIREN. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| empreinte | string | yes | – |
| fait | object | yes | – |
| source | object | yes | – |
No examples provided.
get_french_company_state_aid State aid received by a French company (EU transparency register) ~183
The state aid published for one French company in the European Commission transparency register: grant date, amount or tax-aid bracket, objective, instrument, granting authority (Bpifrance, regions, ministries) and aid scheme, most recent first, with the total count. Use this to answer "what public aid did X receive", "did the State fund X". The register lists aid above a publication threshold only. Some ADEME grants are in both this tool and the ADEME one: never add the two. Matched on the SIREN, never on the name.
| Name | Type | Req | Description |
|---|---|---|---|
| siren | string | yes | The nine-digit SIREN of a French legal entity. Spaces, dots and dashes are accepted. This is not a SIRET: drop the last five digits of a SIRET to get the SIREN. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| empreinte | string | yes | – |
| fait | object | yes | – |
| source | object | yes | – |
No examples provided.
get_french_company_timeline French company timeline ~225
Every dated change the French official gazette recorded for one company: share capital, legal name, legal form, registered office, stated activity, plus insolvency judgments and the current insolvency status. Use this to answer "when did X change", "how has X evolved", "has X ever been in receivership". Do NOT use it to get the current state of a company (today's officers, today's address, today's headcount): this server only publishes what CHANGED. A field that never moved is not in the answer. Coverage starts at 2008; a company may exist and have published nothing. Announcements that merely cite the SIREN without describing the company are excluded; on large franchised networks that is around 40% of what a naive search returns.
| Name | Type | Req | Description |
|---|---|---|---|
| siren | string | yes | The nine-digit SIREN of a French legal entity. Spaces, dots and dashes are accepted. This is not a SIRET: drop the last five digits of a SIRET to get the SIREN. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| empreinte | string | yes | – |
| fait | object | yes | – |
| source | object | yes | – |
No examples provided.
get_french_insolvency_barometer French insolvency barometer ~170
Insolvency openings in France over the last twelve complete months, against the twelve before, with the monthly series and a split by nature (liquidation, receivership, safeguard). Scope: the whole country by default, or one department, or one trade. Pass at most one of them. This counts OPENING judgments only, and it counts judgments, not companies. The current month is never included: still running, it would read as a collapse.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | French department code. Two digits, 2A and 2B for Corsica, three digits overseas. Omit for the whole country. |
| trade | string | – | Trade, read from the words of the activity declared in the gazette. Omit for all trades. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| empreinte | string | yes | – |
| fait | object | yes | – |
| source | object | yes | – |
No examples provided.
How do I install the auregistre MCP server?
auregistre is a hosted endpoint at https://auregistre.fr/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 · auregistre.fr
claude mcp add --transport http fr-auregistre-auregistre 'https://auregistre.fr/mcp'
What is the auregistre MCP server?
auregistre is an MCP server listed in the public MCP registry as fr.auregistre/auregistre. French companies: dated changes and insolvencies (BODACC), filed accounts by year (INPI). No key. This page covers its hosted endpoint (https://auregistre.fr/mcp).
Is the auregistre MCP server safe to use?
auregistre scores 88 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 auregistre MCP server expose?
auregistre exposes 6 tools: get_french_company_timeline, get_french_company_announcements, get_french_insolvency_barometer, get_french_company_financials, get_french_company_ademe_grants, get_french_company_state_aid. Their descriptions and schemas cost roughly 1,216 tokens of context every time the server is loaded.
Does the auregistre MCP server require authentication?
No. We connected to auregistre without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the auregistre MCP server still maintained?
auregistre is still listed as active in the MCP registry. We last reached this channel on 6 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 auregistre MCP server?
VerifyMCP ran 13 checks on auregistre, 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.