Remote MCP · Endpoint

Capucine MCP server

No. Capucine answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scorelook.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.scorelook/capucine
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
750 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Capucine, styliste IA ScoreLook : looks sourcés, météo, hubs pièces, critères shopping.
Listing
From the official MCP registry (active).
Recent checks of Capucine
CheckedResultHandshake
1 hour agoHandshake completed750 ms
2 days agoHandshake completed400 ms
4 days agoHandshake completed391 ms
5 days agoHandshake completed445 ms
7 days agoHandshake completed735 ms
8 days agoHandshake completed960 ms
9 days agoHandshake completed372 ms
12 days agoHandshake completed367 ms
13 days agoHandshake completed814 ms
15 days agoHandshake completed390 ms
16 days agoHandshake completed490 ms
18 days agoHandshake completed381 ms
19 days agoHandshake completed375 ms
20 days agoHandshake completed361 ms
20 days agoHandshake completed442 ms
21 days agoHandshake completed381 ms
22 days agoHandshake completed449 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Capucine and makes no claim about it beyond what these checks measured.