TenderWatch, marchés publics
REMOTE · TENDERWATCH.FR
Appels d'offres publics français ouverts, procédure selon le montant, intérêts moratoires, lexique.
Available components
Last scanned (19 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. 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 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 569 tokens (~142/item across 4 items; 4 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 5 Nov 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.
- 3 Nov 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.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 69
First indexed and scored.
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 5 Nov 2026 · Probed https://tenderwatch.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tenderwatch.fr | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 5874e9d991311331943cd0c84f186a97c99 |
| SANs: tenderwatch.fr | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tenderwatch.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| tenderwatch.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://checkout.stripe.com https://plausible.io https://www.clarity.ms https://scripts.clarity.ms; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://plausible.io https://*.clarity.ms https://c.bing.com https://*.ingest.de.sentry.io https://*.ingest.sentry.io; frame-src https://js.stripe.com https://checkout.stripe.com https://hooks.stripe.com https://billing.stripe.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tenderwatch.fr/mcp | Verified | 200 | |
| http (plaintext) | http://tenderwatch.fr/mcp | HTTPS enforced | 308 | https://tenderwatch.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 →
calculer_interets_moratoires Calculer les intérêts moratoires ~144
Calcule les intérêts moratoires et l'indemnité de 40 € dus par un acheteur public qui a payé une facture en retard (taux BCE + 8 points, code de la commande publique).
| Name | Type | Req | Description |
|---|---|---|---|
| date_paiement | string | yes | AAAA-MM-JJ, date du paiement effectif. |
| date_reception_facture | string | yes | AAAA-MM-JJ. |
| montant_ttc | number | yes | Montant TTC de la facture, en euros. |
| type_acheteur | string | – | Détermine le délai (30, 50 ou 60 jours). Défaut : État ou collectivité. |
No output schema declared.
No examples provided.
definition_marches_publics Définition d'un terme des marchés publics ~78
Donne la définition sourcée (code de la commande publique) d'un terme des marchés publics : DCE, CCAG, standstill, retenue de garantie, avance, offre anormalement basse, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| terme | string | yes | Le terme, ex. « DCE » ou « retenue de garantie ». |
No output schema declared.
No examples provided.
procedure_selon_montant Procédure de passation selon le montant ~87
Indique la procédure et la publicité applicables à un marché public selon son montant HT, sa nature et le type d'acheteur (seuils de dispense, MAPA, procédure formalisée).
| Name | Type | Req | Description |
|---|---|---|---|
| acheteur | string | yes | – |
| montant_ht | number | yes | Montant HT estimé du marché, en euros. |
| nature | string | yes | – |
No output schema declared.
No examples provided.
rechercher_appels_offres Rechercher des appels d'offres ouverts ~210
Cherche parmi les appels d'offres publics français encore ouverts (BOAMP, JOUE, plateformes d'acheteurs) ceux qui correspondent à des mots-clés, avec un filtre région optionnel. Renvoie l'intitulé, l'acheteur, la date limite et le lien de la fiche.
| Name | Type | Req | Description |
|---|---|---|---|
| limite | integer | – | Nombre de résultats (5 par défaut). |
| mots_cles | string | yes | Ce que fait l'entreprise, ex. « nettoyage de locaux » ou « maîtrise d'œuvre voirie ». |
| region | string | – | Région française, une parmi : Île-de-France, Auvergne-Rhône-Alpes, Bourgogne-Franche-Comté, Bretagne, Centre-Val de Loire, Corse, Grand Est, Hauts-de-France, Normandie, Nouvelle-Aquitaine, Occitanie,… |
No output schema declared.
No examples provided.
How do I install the TenderWatch, marchés publics MCP server?
TenderWatch, marchés publics is a hosted endpoint at https://tenderwatch.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 · tenderwatch.fr
claude mcp add --transport http fr-tenderwatch-marches-publics 'https://tenderwatch.fr/mcp'
What is the TenderWatch, marchés publics MCP server?
TenderWatch, marchés publics is an MCP server listed in the public MCP registry as fr.tenderwatch/marches-publics. Appels d'offres publics français ouverts, procédure selon le montant, intérêts moratoires, lexique. This page covers its hosted endpoint (https://tenderwatch.fr/mcp).
Is the TenderWatch, marchés publics MCP server safe to use?
TenderWatch, marchés publics scores 72 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 TenderWatch, marchés publics MCP server expose?
TenderWatch, marchés publics exposes 4 tools: rechercher_appels_offres, calculer_interets_moratoires, procedure_selon_montant, definition_marches_publics. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.
Does the TenderWatch, marchés publics MCP server require authentication?
No. We connected to TenderWatch, marchés publics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TenderWatch, marchés publics MCP server still maintained?
TenderWatch, marchés publics is still listed as active in the MCP registry. We last reached this channel on 5 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 TenderWatch, marchés publics MCP server?
VerifyMCP ran 13 checks on TenderWatch, marchés publics, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.