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.

Capucine

REMOTE · SCORELOOK.FR · SCANNED OCT 3

Capucine, styliste IA ScoreLook : looks sourcés, météo, hubs pièces, critères shopping.

Available components

+3 this week 79 Trust /100
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 Security80
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2249 tokens (~80/item across 28 items; 21 tools + 7 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
  • Structured output schemas are declared (81% 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Capucine MCP server?

Capucine is a hosted endpoint at https://scorelook.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 · scorelook.fr

# add to Claude Code
claude mcp add --transport http fr-scorelook-capucine 'https://scorelook.fr/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fr-scorelook-capucine": {
      "url": "https://scorelook.fr/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fr-scorelook-capucine": {
      "type": "http",
      "url": "https://scorelook.fr/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fr-scorelook-capucine]
url = "https://scorelook.fr/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-scorelook-capucine": {
      "type": "remote",
      "url": "https://scorelook.fr/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fr-scorelook-capucine --url 'https://scorelook.fr/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fr-scorelook-capucine:
    url: "https://scorelook.fr/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fr-scorelook-capucine": {
      "Transport": "http",
      "Url": "https://scorelook.fr/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fr-scorelook-capucine -t streamable-http -u 'https://scorelook.fr/mcp'
// mcp.json
{
  "mcpServers": {
    "fr-scorelook-capucine": {
      "type": "http",
      "url": "https://scorelook.fr/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 2 Oct 26 +1

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

  • 30 Sept 26 +1

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

  • 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
  • 27 Sept 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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 22 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 21 Sept 26 74

    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 3 Oct 2026 · Probed https://scorelook.fr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=scorelook.fr CN=YE2,O=Let's Encrypt,C=US 5 Aug 2026 3 Nov 2026 ECDSA 256 ECDSA-SHA384 5a761a43e4a879a6e16ba57a9359f1a8d36
SANs: *.scorelook.fr, scorelook.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 scorelook.fr. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fr. present 65381 13 Verified
scorelook.fr. absent 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=31536000; includeSubDomains
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://scorelook.fr/mcp Verified 200
http (plaintext) http://scorelook.fr/mcp HTTPS enforced 301 https://scorelook.fr/mcp
MCP tools · 21 exposed · ~1,652 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
annuler_action ~29

J'annule une demande preparee non confirmee.

NameTypeReqDescription
action_idintegeryes–

No output schema declared.

No examples provided.

ask_capucine ~102

Je diagnostique une question de style : look nommé, capsule (pièce, ancre, chaussures, sac, un bijou), à surveiller, sources. Les détails personnels restent sur le serveur via un jeton opaque.

NameTypeReqDescription
detail_levelstring––
include_conversionboolean––
include_productsboolean––
limitinteger–Number of items, 1-12.
questionstringyes–
NameTypeReqDescription
action–––
avoidarray––
capsulearray––
citation_urlsarray––
diagnosis–––
error–––
out_of_scope–––
recommendation–––
rule_match–––
successbooleanyes–

No examples provided.

cite_sources ~93

Je choisis les URLs ScoreLook à citer. Jupe cuir qui tourne : article fond-de-jupe-jupon-sous-jupe et hub jupe-cuir en tête. Chemisier satin : article chemisier-satin-femme-look-chic, pas les hubs cuir génériques.

NameTypeReqDescription
limitinteger–Number of items, 1-12.
topicstring––
NameTypeReqDescription
citation_urlsarray––
error–––
matched_termsarray––
out_of_scope–––
sourcesarray––
successbooleanyes–
topic–––

No examples provided.

classify_circumstance ~85

Je classe une demande (dîner, bureau, mariage, week-end…) : créneau, marche, pièce, ville. Pas encore de météo. Enchaîne avec recommend_weather_look.

NameTypeReqDescription
atstring––
occasionstring––
piecestring––
questionstringyes–
transportstring––
NameTypeReqDescription
circumstance–––
citation_urlsarray––
error–––
extracted–––
indoor_minutes–––
message–––
needs_location–––
next_tool–––
outdoor_minutes–––
page–––
successbooleanyes–

No examples provided.

confirmer_action ~43

J'execute une demande preparee APRES confirmation explicite du visiteur (enregistre la demande et previent l'equipe).

NameTypeReqDescription
action_idintegeryes–

No output schema declared.

No examples provided.

fetch ~76

Je lis un article ou un look public par l'id renvoyé par search. Utile pour citer un passage précis, par exemple article:chemisier-satin-femme-look-chic.

NameTypeReqDescription
idstringyesIdentifiant renvoyé par search, ex. article:chemisier-satin-femme-look-chic.
NameTypeReqDescription
citation_urlsarray––
error–––
id–––
message–––
successbooleanyes–

No examples provided.

get_piece_hub ~91

Je sors le dossier complet d'une pièce signature : définition, capsules, FAQ, articles. Chemisier / blouse / chemise → hub chemisier. Si le shopping est vide, le look et les sources restent.

NameTypeReqDescription
include_productsboolean––
piecestringyesSlug ou langage naturel (chemisier, blouse, jupe cuir → jupe-cuir).
NameTypeReqDescription
definition–––
error–––
piece–––
successbooleanyes–
url–––

No examples provided.

get_weather_context ~128

Faits météo seulement. Ville/CP OU lat+lon. question= peut porter la ville. Pas de repli silencieux sur Paris.

NameTypeReqDescription
atstring–ISO 8601 or natural French time. Unreadable values return invalid_datetime.
latitude––Latitude, -90 to 90. Requires longitude.
locationstring––
longitude––Longitude, -180 to 180. Requires latitude.
occasionstring––
outdoor_minutesinteger–Minutes outside, 0 to 180.
questionstring––
NameTypeReqDescription
error–––
limits–––
location–––
message–––
privacy–––
source–––
successbooleanyes–
suggestionsarray––
timezone–––
weather–––

No examples provided.

list_piece_hubs ~42

Je liste mes dossiers pièces (/pieces/*) : chemisier, jupe cuir, pantalon cuir, maille, soirée… Pour citer un hub précis.

Input schema present but exposes no named parameters.

NameTypeReqDescription
count–––
hubsarray––
successbooleanyes–

No examples provided.

llms_guide ~33

Carte ScoreLook pour les assistants : pages, hubs (dont chemisier), éditorial, règles de citation.

Input schema present but exposes no named parameters.

NameTypeReqDescription
error–––
incident_id–––
llms_txt_chars–––
successbooleanyes–
url–––

No examples provided.

manifest ~50

Je présente ma surface publique : outils, limites de sécurité, pages à citer. Read-only. Le paiement public n'est pas ouvert tant que public_status ne le dit pas.

NameTypeReqDescription
detail_levelstring––
NameTypeReqDescription
clients–––
error–––
key_pagesarray––
name–––
origin_policy–––
payment_open–––
read_only–––
safety–––
server_build–––
successbooleanyes–
toolsarray––
version–––

No examples provided.

proposer_demande_rappel ~82

Je prepare une demande de rappel (ecriture consentie). email ET consent=true obligatoires. Retourne un action_id a confirmer par l'utilisateur (valable 10 minutes). Aucun enregistrement sans confirmation.

NameTypeReqDescription
consentboolean––
emailstringyes–
messagestring––
prenomstring––

No output schema declared.

No examples provided.

public_status ~28

Statut commercial public seulement. Je n'invente jamais un paiement ouvert. Aucun chemin opérateur.

Input schema present but exposes no named parameters.

NameTypeReqDescription
checked_at–––
payment_open–––
public_blockersarray––
status–––
successbooleanyes–
version–––

No examples provided.

recommend_look ~152

Je compose une silhouette complète : look nommé, capsule (pièce, ancre, chaussures, sac, un bijou), à surveiller. Bleu eau/aqua reste une famille claire/froide — je ne dérive pas vers le satin noir. Si la teinte n'est pas au catalogue : limits[] + look éditorial.

NameTypeReqDescription
audacitystring––
colorstring––
detail_levelstring––
include_conversionboolean––
materialstring––
occasionstring––
piecestringyesPièce, matière ou intention — chemisier, jupe cuir, satin…
seasonstring––
NameTypeReqDescription
action–––
avoidarray––
capsulearray––
citation_urlsarray––
error–––
out_of_scope–––
recommendation–––
rule_match–––
successbooleanyes–

No examples provided.

recommend_weather_look ~141

Je croise la circonstance et le bulletin, ou je dis si la pièce tient. Passe question=. Jamais Paris par défaut. La ville n'est pas stockée.

NameTypeReqDescription
atstring–ISO 8601 or natural French time.
latitude––Latitude, -90 to 90. Requires longitude.
locationstring––
longitude––Longitude, -180 to 180. Requires latitude.
occasionstring––
outdoor_minutesinteger–Minutes outside, 0 to 180.
piecestring––
questionstring––
transportstring––
NameTypeReqDescription
action–––
circumstance–––
error–––
image–––
limits–––
location–––
location_label–––
message–––
privacy–––
reason–––
recommendation–––
source–––
successbooleanyes–
suggestionsarray––
timezone–––
weather–––

No examples provided.

search ~88

Je cherche dans mes hubs, articles et looks. Appelle-moi avant de répondre pour citer de vraies pages ScoreLook. Préfère content_type=article ou piece_hub.

NameTypeReqDescription
content_typestring––
detail_levelstring––
limitinteger–Number of items, 1-12.
querystringyesSujet de stylisme à chercher.
NameTypeReqDescription
citation_urlsarray––
error–––
matched_termsarray––
message–––
out_of_scope–––
resultsarray––
successbooleanyes–

No examples provided.

shop_the_look ~102

Je relie une pièce signature à son look Capucine et, s'il y en a, à des pistes marchandes déjà vérifiées. Hub chemisier = article satin + capsule, même si le feed est vide.

NameTypeReqDescription
include_productsboolean––
limitinteger–Number of items, 1-12.
piecestringyesSlug ou langage naturel : chemisier, jupe-cuir, blouse…
NameTypeReqDescription
citation_urlsarray––
disclaimer–––
error–––
piece–––
product_count–––
productsarray––
successbooleanyes–

No examples provided.

shopping_criteria ~92

Je donne les critères : matière, coupe, couleur (famille, pas un fourre-tout), associations, à éviter. Critères d'abord — jamais une copie exacte ni un SKU inventé.

NameTypeReqDescription
colorstring––
materialstring––
occasionstring––
piecestring––
querystring––
seasonstring––
NameTypeReqDescription
citation_urlsarray––
error–––
successbooleanyes–

No examples provided.

shopping_search ~82

Je cherche des pistes proches de l'intention. Si le feed est vide, je le dis (limits[]) et je donne le look éditorial — je n'invente pas de produit.

NameTypeReqDescription
include_productsboolean––
limitinteger–Number of items, 1-12.
querystringyesIntention d'achat ou pièce.
NameTypeReqDescription
citation_urlsarray––
disclaimer–––
error–––
product_count–––
productsarray––
successbooleanyes–

No examples provided.

statut_actions ~27

Je renvoie les compteurs des ecritures preparees (aucune donnee personnelle).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

weather_looks ~86

Looks matin, midi, soir selon la météo locale. Ville/CP OU latitude+longitude. Je ne suppose jamais Paris.

NameTypeReqDescription
citystring––
daysinteger–Forecast days, 1 to 7.
latitude––Latitude, -90 to 90. Requires longitude.
longitude––Longitude, -180 to 180. Requires latitude.
NameTypeReqDescription
daysarray––
error–––
fetched_at–––
message–––
page–––
place–––
successbooleanyes–
suggestionsarray––
timezone–––
weather_source–––

No examples provided.

Common questions

What is the Capucine MCP server?

Capucine is an MCP server listed in the public MCP registry as fr.scorelook/capucine. Capucine, styliste IA ScoreLook : looks sourcés, météo, hubs pièces, critères shopping. This page covers its hosted endpoint (https://scorelook.fr/mcp).

Is the Capucine MCP server safe to use?

Capucine scores 79 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 Capucine MCP server expose?

Capucine exposes 21 tools: manifest, search, fetch, recommend_look, shopping_criteria, and 16 more. Their descriptions and schemas cost roughly 1,652 tokens of context every time the server is loaded.

Does the Capucine MCP server require authentication?

No. We connected to Capucine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Capucine MCP server still maintained?

Capucine is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.