Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BODACC Insolvency Claim Deadline Sentinel (France)

REMOTE · CREANCES.AMACUNIA.FR

Is a French company in insolvency (BODACC), and until when can a creditor file its claim?

67 Trust /100

Last scanned (23 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 390 tokens (~195/item across 2 items; 2 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 Management20
  • Stability observed for 6 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 (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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “creances_lookup” rewrote its description, which is the text the model reads security
    • Schema quality: 162 → 195 ▼ functional
    • Schema quality: 162 → 194 ▼ functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.5.0 → 0.5.1 functional
    • Server version: 0.4.0 → 0.5.0 functional
    • Server version: 0.3.0 → 0.4.0 functional
    • “creances_lookup” added an optional parameter “free_trial” cosmetic
  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 65

    First indexed and scored.

Diagnostics

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 Nov 2026 · Probed https://creances.amacunia.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=amacunia.fr CN=YE2,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA384 56c6a58320cd943823bf2bd7c882164b5f6
SANs: *.amacunia.fr, amacunia.fr
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of creances.amacunia.fr. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
fr. DS published 65381 13 Verified
amacunia.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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://creances.amacunia.fr/mcp Verified 200
http (plaintext) http://creances.amacunia.fr/mcp Inconclusive 405
MCP tools · 2 exposed · ~325 tokens

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 →

Tool Tokens
creances_example ~46

Free sample: real output for SIREN 910759158 as of 2026-11-09, while a claim window was open. Same shape as creances_lookup.

Input schema present but exposes no named parameters.

NameTypeReqDescription
avertissementstring|null––
date_calculstring|null––
entreprises_avec_delai_ouvertinteger|null––
licenceobject|null–Licence of the source data: nom, url, source, attribution (the credit the licence requires)
marche_a_suivrestring|null–How to file the claim (French), only when a window is open
residence_creancierstring|null––
resultatsarray|null––
sourcestring|null––

No examples provided.

creances_lookup ~279

Use this when checking if a French company is in insolvency proceedings and until when a creditor can still file its claim. For 1-50 SIREN numbers: proceedings published in the BODACC (safeguard, receivership, liquidation) and, for each opening judgment, the exact filing deadline (2 months after publication, 4 for a creditor outside the court's territory; art. R622-24 Code de commerce), days left, court-appointed representative and notice link. For credit managers, accountants, debt collectors. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

NameTypeReqDescription
free_trialboolean–Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.
residencestring–Where the creditor lives: metropole (default), etranger (abroad), or an overseas code (971 to 978, 986 to 988). Two more months when it differs from the court's territory
sirensstringyes1 to 50 SIREN (9 digits) or SIRET (14 digits), comma-separated
NameTypeReqDescription
avertissementstring|null––
date_calculstring|null––
entreprises_avec_delai_ouvertinteger|null––
licenceobject|null–Licence of the source data: nom, url, source, attribution (the credit the licence requires)
marche_a_suivrestring|null–How to file the claim (French), only when a window is open
residence_creancierstring|null––
resultatsarray|null––
sourcestring|null––

No examples provided.

Install

How do I install the BODACC Insolvency Claim Deadline Sentinel (France) MCP server?

BODACC Insolvency Claim Deadline Sentinel (France) is a hosted endpoint at https://creances.amacunia.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 · creances.amacunia.fr

# add to Claude Code
claude mcp add --transport http fr-amacunia-bodacc-insolvency-claim-deadline 'https://creances.amacunia.fr/mcp'
Common questions

What is the BODACC Insolvency Claim Deadline Sentinel (France) MCP server?

BODACC Insolvency Claim Deadline Sentinel (France) is an MCP server listed in the public MCP registry as fr.amacunia/bodacc-insolvency-claim-deadline. Is a French company in insolvency (BODACC), and until when can a creditor file its claim? This page covers its hosted endpoint (https://creances.amacunia.fr/mcp).

Is the BODACC Insolvency Claim Deadline Sentinel (France) MCP server safe to use?

BODACC Insolvency Claim Deadline Sentinel (France) scores 67 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 BODACC Insolvency Claim Deadline Sentinel (France) MCP server expose?

BODACC Insolvency Claim Deadline Sentinel (France) exposes 2 tools: creances_example, creances_lookup. Their descriptions and schemas cost roughly 325 tokens of context every time the server is loaded.

Does the BODACC Insolvency Claim Deadline Sentinel (France) MCP server require authentication?

No. We connected to BODACC Insolvency Claim Deadline Sentinel (France) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BODACC Insolvency Claim Deadline Sentinel (France) MCP server still maintained?

BODACC Insolvency Claim Deadline Sentinel (France) is still listed as active in the MCP registry. We last reached this channel on 21 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 BODACC Insolvency Claim Deadline Sentinel (France) MCP server?

VerifyMCP ran 12 checks on BODACC Insolvency Claim Deadline Sentinel (France), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BODACC Insolvency Claim Deadline Sentinel (France): HTTPS. 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.