Flamel MCP server

• Registry nameai.flamel/public-contentverified in the MCP registry

The registry name sits under flamel.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-17
• Tools9
• Server calls itselfflamel-public-content
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 210 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer227 ms
• Space in an agent's context≈ 871 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_company_overview

  Get a structured overview of Flamel: what the product does, who it is for, the solution areas, key links, and how to contact sales or start a trial. Start here if you know nothing about Flamel.

• search_flamel_content

  Full-text search across Flamel's published blog posts, case studies, and FAQ entries. Use this first when you do not already know which page answers the question.

• list_blog_posts

  List published Flamel blog posts, newest first. Optionally filter by category. Returns titles, URLs, summaries, and publish dates, not full bodies.

• get_blog_post

  Fetch the full body of one published Flamel blog post as Markdown, by slug.

• list_blog_categories

  List the blog categories available for filtering `list_blog_posts`.

• list_case_studies

  List published Flamel customer case studies with their headline results.

• get_case_study

  Fetch one Flamel case study by slug: the challenge, the solution, the results, and customer quotes.

• list_faqs

  List published Flamel FAQ entries: platform capabilities, pricing model, onboarding, integrations, and security. Good for direct factual questions about the product.

• list_testimonials

  List published customer testimonials about Flamel, with the author name, title, and company.