auregistre
REMOTE · AUREGISTRE.FR · SCANNED SEP 21
French companies: dated changes and insolvencies (BODACC), filed accounts by year (INPI). No key.
Available components
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 Usability80
- 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 1114 tokens (~222/item across 5 items; 4 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 Management63
- Stability observed for 19 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 (25% 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 4 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
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'
{
"mcpServers": {
"fr-auregistre-auregistre": {
"url": "https://auregistre.fr/mcp"
}
}
} {
"servers": {
"fr-auregistre-auregistre": {
"type": "http",
"url": "https://auregistre.fr/mcp"
}
}
} [mcp_servers.fr-auregistre-auregistre] url = "https://auregistre.fr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-auregistre-auregistre": {
"type": "remote",
"url": "https://auregistre.fr/mcp",
"enabled": true
}
}
} openclaw mcp add fr-auregistre-auregistre --url 'https://auregistre.fr/mcp' --transport streamable-http
mcp_servers:
fr-auregistre-auregistre:
url: "https://auregistre.fr/mcp" {
"McpServers": {
"fr-auregistre-auregistre": {
"Transport": "http",
"Url": "https://auregistre.fr/mcp"
}
}
} assistant mcp add fr-auregistre-auregistre -t streamable-http -u 'https://auregistre.fr/mcp'
{
"mcpServers": {
"fr-auregistre-auregistre": {
"type": "http",
"url": "https://auregistre.fr/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 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.
- 16 Sept 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.
- 13 Sept 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 21 Sept 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 | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | e71fb352bb94a131312024971b90782 |
| 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. | present | 65381 | 13 | Verified |
| auregistre.fr. | 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=31536000 |
| x-content-type-options | nosniff |
| 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_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. |
No output schema declared.
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. |
No output schema declared.
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. |
No output schema declared.
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 |
|---|---|---|---|
| by_department | array | – | Ranking over the window, largest first. Country scope only. |
| by_nature | array | yes | – |
| change_percent | number|null | – | Null when the reference is zero: a place with no failure last year did not explode. |
| monthly | array | yes | – |
| page_url | string | yes | The page that shows the same thing to a human. |
| reference | – | yes | – |
| scope | object | yes | – |
| window | – | yes | – |
No examples provided.
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 83 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 4 tools: get_french_company_timeline, get_french_company_announcements, get_french_insolvency_barometer, get_french_company_financials. Their descriptions and schemas cost roughly 832 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.