Remote MCP · Endpoint

Flamel Public Content MCP server

No. Flamel Public Content answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://www.flamel.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.flamel/public-content
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
177 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only MCP server for Flamel.ai's public content: company overview, blog, case studies, FAQs.
Listing
From the official MCP registry (active).
Recent checks of Flamel Public Content
CheckedResultHandshake
43 minutes agoHandshake completed177 ms
10 days agoHandshake completed197 ms
10 days agoHandshake completed169 ms
11 days agoHandshake completed244 ms
12 days agoHandshake completed117 ms
14 days agoHandshake completed158 ms
14 days agoHandshake completed103 ms
15 days agoHandshake completed157 ms
17 days agoHandshake completed90 ms
19 days agoHandshake completed275 ms
21 days agoHandshake completed143 ms
24 days agoHandshake completed108 ms
26 days agoHandshake completed129 ms
28 days agoHandshake completed101 ms

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

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