FEC Checker (French accounting file pre-audit)

io.github.vincenz-cdfPublished by GitHub account vincenz-cdfv0.1.2Updated Nov 1, 2026

Validate French FEC accounting files and flag audit risks before a tax audit.

The publisher's own server: audit.domains - Domain Valuation

VerifiedStreamable HTTPWeb executableFinanceDeveloper Tools

Overview

AI-generated overview

Lints French FEC accounting export files for structural errors, letting an assistant check a local file's format before an audit.

What you can do
  • Check a local FEC file's structure and return the same JSON result as the command-line tool
  • Validate file naming against the SIRENFECAAAAMMJJ.txt pattern, plus encoding, separator and the 18-column header
  • Report field-format errors such as invalid or wrongly formatted dates, amounts and missing mandatory fields or field pairs
  • Return errors, warnings and statistics for one file path per call
When to use it
Useful when you have a FEC file exported from French accounting software and want a quick structural check before handing it to an accountant or facing a tax audit. It is a technical format check only, not tax advice or a certification.
Requirements
The local MCP server runs from the PyPI package fec-lint via uvx or pipx, so Python tooling is needed; it reads a local file path. The hosted Apify variant requires an Apify OAuth sign-in, and agents can pay per file via x402.
Before you install
The free local linter only checks structure; balance, numbering and risk signals are only in the paid hosted version, which is billed per file and can be paid by agents via x402. The README states it does not certify a file or replace an accountant's review. The hosted version sends the file to Apify, while the local one keeps data on the machine.

Installation

In SourceWeft

  1. Open FEC Checker (French accounting file pre-audit) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vincenz-cdf%2Ffec-lint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "fec-checker-french-accounting-file-pre-a": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=highfiddle/fec-checker"
    }
  }
}

README

fec-lint

English · Français

Technical check, not tax advice. fec-lint checks the structure of a file against the published FEC format. It does not certify a file or replace an accountant's review.

Contrôle technique, pas un conseil fiscal. fec-lint vérifie la structure d'un fichier au regard du format FEC publié. Il ne certifie pas un fichier et ne remplace pas la revue d'un expert-comptable.

English

Free structural linter for French FEC files (Fichier des Écritures Comptables, art. A47 A-1 LPF), as a command line tool and an MCP server.

What file does it check?

The FEC your accounting software exports (look for "FEC" or "Export DGFiP" in its year-end menu); you don't build it by hand. It is a text file named SIRENFECAAAAMMJJ.txt (SIREN, FEC, closing date), tab- or pipe-separated, with this header and one line per accounting line:

text
JournalCode|JournalLib|EcritureNum|EcritureDate|CompteNum|CompteLib|CompAuxNum|CompAuxLib|PieceRef|PieceDate|EcritureLib|Debit|Credit|EcritureLet|DateLet|ValidDate|Montantdevise|IdeviseVE|Ventes|000039|20250610|411000|Clients|CLI001|Atelier Durand|F2025-06|20250610|Facture F2025-06 Atelier Durand|3960,00|0,00|||20250610||

Dates are AAAAMMJJ; amounts use a decimal comma and no thousands separator. CompAuxNum/CompAuxLib, EcritureLet/DateLet and Montantdevise/Idevise may be empty, but only in pairs; every other field is required. The FEC Checker page has the full column-by-column table. Synthetic examples are in tests/fixtures/.

Install

bash
pipx install fec-lint

Command line

bash
fec-lint 123456782FEC20251231.txt
text
123456782FEC20251231.txt: FAILED (encoding utf-8, separator pipe, lines 214)  error date_invalid x3: Non-existent date in EcritureDate. - line(s) 21, 22, 23  error date_format x3: Wrong date format in EcritureDate (expected AAAAMMJJ). - line(s) 64, 65, 66Structure has errors. Full pre-audit (balance, numbering, risk signals): https://apify.com/highfiddle/fec-checker
  • --json prints the full result: {ok, file, errors[], warnings[], stats}.
  • --name 123456782FEC20251231.txt sets the name checked against SIRENFECAAAAMMJJ.txt.
  • --quiet hides the last line.
  • Exit code: 0 when the structure is OK, 1 on errors, 2 when a file cannot be read. Several files can be given at once.
  • A .zip holding exactly one .txt FEC is unpacked first.

MCP server

Add it to your MCP client (Claude Desktop, Claude Code, Cursor…):

json
{    "mcpServers": {        "fec-lint": {            "command": "uvx",            "args": ["--from", "fec-lint", "fec-lint-mcp"]        }    }}

Without uv, install with pipx install fec-lint and use "command": "fec-lint-mcp". The server exposes one tool, lint_fec(path), which takes a local file path and returns the same JSON as --json.

Full pre-audit as a hosted MCP server. The paid FEC Checker (balance, numbering, risk signals, AI fix list) runs on Apify and is reachable over MCP. Users sign in with Apify OAuth; agents can pay with x402 by adding &payment=x402:

bash
claude mcp add --transport http fec-checker "https://mcp.apify.com/?tools=highfiddle/fec-checker"

Free vs full pre-audit

Checkfec-lint (free)FEC Checker on Apify
File name SIRENFECAAAAMMJJ.txt, SIREN key✅✅
Encoding, separator, 18 headers✅✅
Field formats: dates, amounts, mandatory fields, pairs✅✅
Balance per entry and for the whole file—✅
EcritureNum gaps and duplicates, ValidDate chronology—✅
Risk signals: weekends, holidays, round amounts, Benford, cash 53x, suspense 471, after year end—✅
Verdict, 0-100 score, AI-written fix list (FR/EN)—✅
Runslocally, nothing leaves your machineon Apify, pay per file

Français

Linter structurel gratuit pour les FEC (Fichier des Écritures Comptables, art. A47 A-1 LPF), en ligne de commande et en serveur MCP.

Quel fichier contrôle-t-il ?

Le FEC exporté par votre logiciel comptable (cherchez « FEC » ou « Export DGFiP » dans le menu de clôture) ; vous ne le construisez pas à la main. C'est un fichier texte nommé SIRENFECAAAAMMJJ.txt (SIREN, FEC, date de clôture), séparé par tabulations ou barres verticales, avec l'en-tête et le type de ligne montrés plus haut.

Les dates sont au format AAAAMMJJ ; les montants utilisent la virgule décimale, sans séparateur de milliers. CompAuxNum/CompAuxLib, EcritureLet/DateLet et Montantdevise/Idevise peuvent être vides, mais seulement par paires ; tous les autres champs sont obligatoires. La page FEC Checker détaille chaque colonne. Des exemples fictifs sont dans tests/fixtures/.

Installation

bash
pipx install fec-lint

Ligne de commande

bash
fec-lint 123456782FEC20251231.txt
  • --json affiche le résultat complet : {ok, file, errors[], warnings[], stats}.
  • --name 123456782FEC20251231.txt indique le nom à contrôler selon SIRENFECAAAAMMJJ.txt.
  • --quiet masque la dernière ligne.
  • Code de sortie : 0 si la structure est correcte, 1 en cas d'erreur, 2 si un fichier est illisible. Plusieurs fichiers peuvent être passés à la fois.
  • Un .zip contenant un seul FEC .txt est décompressé d'abord.

Les messages sont en anglais ; les codes de règle (date_invalid, header_missing…) sont stables.

Serveur MCP

Ajoutez-le à votre client MCP (Claude Desktop, Claude Code, Cursor…) avec la configuration ci-dessus. L'outil lint_fec(path) prend le chemin d'un fichier local et renvoie le même JSON que --json.

Pré-audit complet en serveur MCP hébergé. Le FEC Checker payant (équilibre, numérotation, signaux de risque, plan de correction IA) tourne sur Apify et s'utilise en MCP via https://mcp.apify.com/?tools=highfiddle/fec-checker (connexion Apify OAuth ; les agents peuvent payer en x402 avec &payment=x402).

Gratuit ou pré-audit complet

Contrôlefec-lint (gratuit)FEC Checker sur Apify
Nom SIRENFECAAAAMMJJ.txt, clé du SIREN✅✅
Encodage, séparateur, 18 colonnes✅✅
Formats : dates, montants, champs obligatoires, couples de champs✅✅
Équilibre par écriture et du fichier—✅
Ruptures et doublons d'EcritureNum, chronologie de ValidDate—✅
Signaux de risque : week-ends, jours fériés, montants ronds, Benford, caisse 53x, attente 471, après clôture—✅
Verdict, score 0-100, plan de correction rédigé par IA (FR/EN)—✅
Exécutionen local, rien ne quitte votre machinesur Apify, paiement par fichier

Development

bash
python -m venv .venv.venv/bin/pip install -e ".[test]"   # Windows: .venv\Scripts\pippytest

The fixtures in tests/fixtures/ are synthetic FEC files (fictitious SIREN 123456782). MIT license.

Source: README.md at commit 474e644

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.2LatestNov 1, 2026
  2. v0.1.1Nov 1, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Audit integrations

audit.domains - Domain Valuation

domains.auditOfficial publisher

Deterministic domain-name valuation: fair-value intervals, comparable recorded sales, availability checks, and a verified for-sale listing market.

Streamable HTTPWeb executable
Business & Commerce27 toolsNov 1, 2026

Revenue Agent — OpenAPI Audit & Change Detection

news.prhOfficial publisher

A remote MCP endpoint that audits OpenAPI specifications and detects API changes, charging $0.10 USDC per analysis via x402 on Base.

Streamable HTTPWeb executable
Developer Tools2 toolsOct 24, 2026

FinePrint AI Legal Risk & Contract Audit MCP Server

Published by GitHub account RitualDev-Lab

Local in-memory scanner that grades legal contracts, NDAs and leases for risk and drafts redline amendments for coding agents.

STDIODesktop only
AI & MLNot validated yetNov 7, 2026

Mcp Supply Audit

Published by GitHub account kimmawla

Audits MCP servers as supply-chain artifacts — registry entries, PyPI/npm packages, client configs and tool definitions — using read-only static checks.

STDIODesktop only
Developer ToolsNot validated · the package did not installNov 5, 2026

Arquestra Audit

Published by GitHub account pablo-ramossanchez

Audit a data file before publishing: one light per figure. Your data never reaches the server.

Streamable HTTPWeb executable
5 toolsNov 3, 2026