Remote MCP · Endpoint

FiltreCharbon MCP server

No. FiltreCharbon answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://filtrecharbon.com/mcp

The last check completed an MCP handshake.

Registry name
com.filtrecharbon/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
278 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search FAC charcoal filters, check specifications and prepare a checkout link for France or Belgium.
Listing
From the official MCP registry (active).
Recent checks of FiltreCharbon
CheckedResultHandshake
1 hour agoHandshake completed278 ms
2 days agoHandshake completed267 ms
4 days agoHandshake completed271 ms
6 days agoHandshake completed268 ms
8 days agoHandshake completed269 ms
10 days agoHandshake completed284 ms
12 days agoHandshake completed278 ms
13 days agoHandshake completed293 ms
14 days agoHandshake completed271 ms
16 days agoHandshake completed272 ms
18 days agoHandshake completed269 ms
20 days agoHandshake completed276 ms
21 days agoHandshake completed273 ms
23 days agoHandshake completed270 ms
24 days agoHandshake completed281 ms

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

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 FiltreCharbon and makes no claim about it beyond what these checks measured.