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.

socs.fr, la commande publique française

REMOTE · MCP.SOCS.FR

French public procurement: open tenders from BOAMP, public buyers, and contracts won by a company.

Available components

0 this week 38 Trust /100

Last scanned (17 hours ago)

Scores higher than 28% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security95
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

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.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 19 Oct 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: partial → pass ▲ security
    • First check of Authorization: pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 14 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Sept 26 0

    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://mcp.socs.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.gentry.fr CN=WR3,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 RSA 2048 SHA256-RSA 841f1a64dadd7f3b0a5a30b6bf58792d
SANs: mcp.gentry.fr, mcp.lucyol.fr, mcp.silvero.fr, mcp.socs.fr, mcp.vaq.fr, connexion.murmure.tech
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.socs.fr. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
fr. DS published 65381 13 Verified
socs.fr. DS published 24070 8 Verified
mcp.socs.fr. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.socs.fr/.well-known/oauth-protected-resource/mcp"

Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.socs.fr/.well-known/oauth-protected-resource/mcp"
Header Value
www-authenticate Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.socs.fr/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://mcp.socs.fr/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.socs.fr/mcp
Authorisation server https://mcp.socs.fr/

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.socs.fr/mcp Auth required 401
http (plaintext) http://mcp.socs.fr/mcp HTTPS enforced 301 https://mcp.socs.fr/mcp
MCP tools · 4 exposed · ~630 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
acheteurs_publics ~157

Liste les collectivités, hôpitaux et établissements publics qui ont réellement attribué des marchés sur un département, avec leur nombre de marchés, leur budget médian et leur dernière commande. À appeler quand la question porte sur « à qui vendre » ou « qui achète » quelque part. Le département s'écrit en code (35) ou en toutes lettres (Ille-et-Vilaine).

NameTypeReqDescription
departementstringyesDépartement, en code ou en toutes lettres : « 35 », « Ille-et-Vilaine »
limiteinteger––
secteurstring–Secteur d'achat, en code CPV à deux chiffres ou en toutes lettres : « 45 », « travaux de construction »

No output schema declared.

No examples provided.

barometre_secteur ~141

Pour un secteur d'achat (code CPV ou libellé) et un territoire : combien d'offres reçoit en moyenne un marché comparable, dans quelle fourchette de montants il se situe, quelle part passe par une procédure adaptée et quelle part relève d'accords-cadres. À appeler avant de décider de candidater. Sans département, la réponse porte sur la France entière et sert de repère.

NameTypeReqDescription
departementstring–Département, en code ou en toutes lettres. Sans lui, la France entière.
secteurstringyesSecteur d'achat, en code CPV à deux chiffres ou en toutes lettres

No output schema declared.

No examples provided.

consultations_ouvertes ~199

Les consultations publiées au BOAMP dont la date limite de remise des offres n'est pas passée, interrogées en direct. À appeler dès qu'une question porte sur des marchés « à venir », « ouverts » ou « auxquels répondre » : ces avis changent tous les jours et ne peuvent pas être connus de mémoire. Filtre par département, par mots-clés et par délai minimum restant : sous deux semaines, une PME n'a matériellement pas le temps de monter un dossier.

NameTypeReqDescription
departementstring–Département, en code ou en toutes lettres. Sans lui, la France entière.
joursMininteger–Ne garder que les avis laissant au moins ce nombre de jours pour répondre
limiteinteger––
motsClesstring–Mots présents dans l'objet du marché : « voirie », « restauration scolaire »
typestring–Travaux, Fournitures ou Services

No output schema declared.

No examples provided.

marches_d_une_entreprise ~133

À partir d'un SIREN : les marchés publics qu'une entreprise a remportés, chez quels acheteurs, dans quels secteurs et pour quels montants. À appeler quand la question porte sur l'activité publique d'une société, sa clientèle publique ou son poids sur un marché. Rend une réponse vide quand l'entreprise n'a remporté aucun marché déclaré, ce qui est le cas de l'immense majorité des sociétés françaises.

NameTypeReqDescription
limiteinteger–Nombre de marchés détaillés à rendre (8 par défaut)
sirenstringyesSIREN à neuf chiffres, espaces tolérés

No output schema declared.

No examples provided.

Install

How do I install the socs.fr, la commande publique française MCP server?

socs.fr, la commande publique française is a hosted endpoint at https://mcp.socs.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 · mcp.socs.fr

# add to Claude Code
claude mcp add --transport http fr-socs-commande-publique 'https://mcp.socs.fr/mcp'
Common questions

What is the socs.fr, la commande publique française MCP server?

socs.fr, la commande publique française is an MCP server listed in the public MCP registry as fr.socs/commande-publique. French public procurement: open tenders from BOAMP, public buyers, and contracts won by a company. This page covers its hosted endpoint (https://mcp.socs.fr/mcp).

Is the socs.fr, la commande publique française MCP server safe to use?

socs.fr, la commande publique française scores 38 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 socs.fr, la commande publique française MCP server expose?

socs.fr, la commande publique française exposes 4 tools: consultations_ouvertes, acheteurs_publics, barometre_secteur, marches_d_une_entreprise. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.

Does the socs.fr, la commande publique française MCP server require authentication?

Yes. socs.fr, la commande publique française asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the socs.fr, la commande publique française MCP server still maintained?

socs.fr, la commande publique française 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 socs.fr, la commande publique française MCP server?

VerifyMCP ran 5 checks on socs.fr, la commande publique française, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about socs.fr, la commande publique française: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.