@pipeworx/fr-decp

French public-contract AWARD data (données essentielles de la commande publique / DECP) — for every contract a French public buyer has awarded: buyer, awarded supplier's SIRET, amount, notification date, and CPV code. This is award data (after the fact), not tender notices — it complements france-boamp (open tender bulletin, before award), it does not duplicate it.

Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

• fr_decp_search_contracts(keyword?, buyer_name?, buyer_siret?, supplier_name?, supplier_siret?, cpv_code?, department_code?, min_amount?, max_amount?, date_from?, date_to?, sort?, limit?, offset?) — search awarded contracts by any combination of buyer, supplier, CPV, French department, amount range, notification-date range, and free text in the contract description. Returns total_matches (the true count over the whole filtered set) plus the matching contracts, newest first by default.

• fr_decp_get_contract(uid) — fetch one contract award by its unique record id, as returned in a search result.

• fr_decp_contract_stats(group_by, keyword?, buyer_name?, buyer_siret?, supplier_name?, supplier_siret?, cpv_code?, department_code?, min_amount?, max_amount?, date_from?, date_to?, limit?) — aggregate contract counts by buyer department, buyer region, buyer type, supplier size category, supplier department, CPV code, procedure, or contract type, over the same filters as the search tool — "which departments/CPV codes/buyer types won the most contracts matching X".

Related MCP server: mcp-marches-publics

Auth

Keyless. No PISTE/API-Gouv account, app registration, or key is needed.

Data sources

• Ministère de l'économie et des finances (DAJ), Données essentielles de la commande publique — the legally-required disclosure (arrêté of 22 March

  2019. every French public buyer files about a contract it awards, served through the state's own consolidated, re-published copy under Licence Ouverte v2.0 (Etalab) — which explicitly permits redistribution and re-use, commercial included.

Notes

The upstream (an older "decp_augmente" dataset on data.economie.gouv.fr) was deprecated in November 2023 in favour of a newer, actively-maintained consolidated file; this pack targets the live successor, which is updated multiple times a month and carries records notified days before a query runs (verified: a contract notified the day before was queryable immediately).

The consolidated dataset's own file is multi-gigabyte — too large to proxy or mirror whole — so this pack queries it live, per request, through the publisher's own keyless row-filtering query service for hosted datasets. No nothing downloaded or stored by this pack; every response carries data_as_of.

Two upstream quirks worth knowing if you touch this pack:

• The __groupby and __count query operators are bare flags — passing them as key=value (what URLSearchParams.set() always produces) gets the whole query rejected with a 400 "Malformed query". They have to be concatenated onto the query string unencoded, with no =.

• page_size silently returns zero rows above ~200 rather than erroring or clamping — there is no error to catch, so stay at or under 200.

A small share of upstream rows carry obviously-wrong values (e.g. a dateNotification decades in the future) — a data-quality property of the underlying government filings, not of this pack.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "fr-decp": {
      "url": "https://gateway.pipeworx.io/fr-decp/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/fr-decp/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/fr_decp_search_contracts \
  -H 'Content-Type: application/json' \
  -d '{"buyer_name":"VILLE DE PARIS","cpv_code":"30230000","limit":3}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/fr_decp_search_contracts. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-fr-decp is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/fr-decp/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "fr-decp": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-fr-decp"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Fr Decp data" })

The gateway picks the right tool and fills the arguments automatically.

More

• Docs and guides

• pipeworx.io

License

MIT