# auregistre (remote · auregistre.fr)

French companies: dated changes and insolvencies (BODACC), filed accounts by year (INPI). No key.

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

## Components

- remote · `auregistre.fr`: 83/100 (this document), [markdown](https://verifymcp.io/servers/fr-auregistre-auregistre/auregistre.md), [page](https://verifymcp.io/servers/fr-auregistre-auregistre/auregistre)

## Channel facts

- Endpoint: `https://auregistre.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-09-21.

- **Endpoint Security**: 80/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 check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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.
  - Structured output schemas are declared (25% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 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 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.

### Claude

```bash
claude mcp add --transport http fr-auregistre-auregistre 'https://auregistre.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-auregistre-auregistre": {
      "url": "https://auregistre.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-auregistre-auregistre": {
      "type": "http",
      "url": "https://auregistre.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-auregistre-auregistre]
url = "https://auregistre.fr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-auregistre-auregistre": {
      "type": "remote",
      "url": "https://auregistre.fr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-auregistre-auregistre --url 'https://auregistre.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-auregistre-auregistre:
    url: "https://auregistre.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-auregistre-auregistre": {
      "Transport": "http",
      "Url": "https://auregistre.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-auregistre-auregistre -t streamable-http -u 'https://auregistre.fr/mcp'
```

### Other

```json
{
  "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.

## 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-09-20 (score 83, +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.

### 2026-09-18 (score 82, +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-09-16 (score 81, +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-09-13 (score 80, +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.

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

### 2026-09-09 (score 78, +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.

### 2026-09-07 (score 77, +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.

### 2026-09-05 (score 76, +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.

## MCP tools (4)

### `get_french_company_timeline` (~225 tokens)

French company timeline

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.

Input parameters:

- `siren` (string, required): 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.

### `get_french_company_announcements` (~197 tokens)

What the gazette published recently

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.

Input parameters:

- `since` (string): Publication date to look back to, ISO 8601. Defaults to 30 days ago.
- `siren` (array, required): The companies to look at. One call for all of them, not one call each.

### `get_french_insolvency_barometer` (~170 tokens)

French insolvency barometer

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.

Input parameters:

- `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.

Output parameters:

- `by_department` (array): Ranking over the window, largest first. Country scope only.
- `by_nature` (array)
- `change_percent` (number|null): Null when the reference is zero: a place with no failure last year did not explode.
- `monthly` (array)
- `page_url` (string): The page that shows the same thing to a human.
- `reference`
- `scope` (object)
- `window`

### `get_french_company_financials` (~240 tokens)

French company filed accounts

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.

Input parameters:

- `siren` (string, required): 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.

## Diagnostics

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

## Score history

- 2026-09-21: 83
- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 75

## Common questions

### 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.

## Links

- Remote endpoint: https://auregistre.fr/mcp
- Website: https://auregistre.fr/api
- Changelog RSS feed: https://verifymcp.io/servers/fr-auregistre-auregistre/auregistre.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-auregistre-auregistre/auregistre.json
- HTML version of this page: https://verifymcp.io/servers/fr-auregistre-auregistre/auregistre