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.

Flamel Public Content

REMOTE · WWW.FLAMEL.AI

Read-only MCP server for Flamel.ai's public content: company overview, blog, case studies, FAQs.

Available components

0 this week 91 Trust /100

Last scanned (20 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Marketing and SEO

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 Security83
Transport & Reachability100
Schema Quality & AI Usability85
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 630 tokens (~70/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
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.

  • 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
  • 25 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
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 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
  • 23 Aug 26 0
    • MCP protocol: fail → pass ▲ functional
    • Tool “get_blog_post” now declares an output schema ▲ functional
    • Tool “get_case_study” now declares an output schema ▲ functional
    • Tool “get_company_overview” now declares an output schema ▲ functional
    • Tool “list_blog_categories” now declares an output schema ▲ functional
    • Tool “list_blog_posts” now declares an output schema ▲ functional
    • Tool “list_case_studies” now declares an output schema ▲ functional
    • Tool “list_faqs” now declares an output schema ▲ functional
    • Tool “list_testimonials” now declares an output schema ▲ functional
    • Tool “search_flamel_content” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
  • 11 Aug 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
  • 10 Aug 26 0

    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 16 Oct 2026 · Probed https://www.flamel.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.flamel.ai CN=YR2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 RSA 2048 SHA256-RSA 61eb0050ee1507efcf28877b65239ca2fd6
SANs: www.flamel.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of www.flamel.ai. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
flamel.ai. present 35972 13 Verified
www.flamel.ai. Verified address RRset verified with the apex keys
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=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.googletagmanager.com https://*.google-analytics.com https://*.calendly.com https://*.hotjar.com https://*.hotjar.io https://connect.facebook.net https://snap.licdn.com https://*.apollo.io https://*.openai.com https://*.vector.co https://*.youtube.com https://*.ytimg.com https://*.flamel.ai https://googleads.g.doubleclick.net https://www.googleadservices.com; style-src 'self' 'unsafe-inline' https://*.calendly.com; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https: wss:; frame-src 'self' https://calendly.com https://*.calendly.com https://www.youtube.com https://www.youtube-nocookie.com https://*.facebook.com https://*.vector.co; media-src 'self' https: blob:; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self' https://calendly.com https://*.calendly.com https://*.facebook.com; frame-ancestors 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.flamel.ai/mcp Verified 200
http (plaintext) http://www.flamel.ai/mcp HTTPS enforced 308 https://www.flamel.ai/mcp
MCP tools · 9 exposed · ~537 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
get_blog_post ~56

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

NameTypeReqDescription
slugstringyesPost slug, e.g. "franchise-social-media-strategy". The last path segment of /blog/<slug>.
NameTypeReqDescription
authorstring––
categorystring––
descriptionstring––
markdownstringyes–
publishedDatestring––
readTimestring––
slugstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_case_study ~54

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

NameTypeReqDescription
slugstringyesCase study slug, the last path segment of /case-studies/<slug>.
NameTypeReqDescription
companystring––
descriptionstring––
industrystring––
locationsstring––
markdownstringyes–
quotesarrayyes–
slugstringyes–
statsarrayyes–
titlestringyes–
urlstringyes–

No examples provided.

get_company_overview ~55

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
audiencesarrayyes–
contactobjectyes–
descriptionstringyes–
linksobjectyes–
namestringyes–
solutionsarrayyes–
taglinestringyes–
urlstringyes–

No examples provided.

list_blog_categories ~21

List the blog categories available for filtering `list_blog_posts`.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes–

No examples provided.

list_blog_posts ~111

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

NameTypeReqDescription
categorystring–Category name, e.g. "Social Media", "Strategy", "Paid Advertising", "AI & Automation". Omit for all categories.
limitinteger–How many posts to return (1-50). Defaults to 10.
pageinteger–Page number for pagination. Defaults to 1.
NameTypeReqDescription
pageintegeryes–
postsarrayyes–
totalPagesintegeryes–
totalPostsintegeryes–

No examples provided.

list_case_studies ~22

List published Flamel customer case studies with their headline results.

Input schema present but exposes no named parameters.

NameTypeReqDescription
caseStudiesarrayyes–

No examples provided.

list_faqs ~71

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

NameTypeReqDescription
categorystring–Optional FAQ category filter.
limitinteger–How many entries to return (1-100). Defaults to 50.
NameTypeReqDescription
faqsarrayyes–

No examples provided.

list_testimonials ~62

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

NameTypeReqDescription
featuredboolean–Return only featured testimonials. Defaults to false.
limitinteger–How many to return (1-50). Defaults to 10.
NameTypeReqDescription
testimonialsarrayyes–

No examples provided.

search_flamel_content ~85

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.

NameTypeReqDescription
limitinteger–Maximum results per content type (1-25). Defaults to 5.
querystringyesSearch terms, e.g. "franchise Google Ads playbooks".
NameTypeReqDescription
blogPostsarrayyes–
caseStudiesarrayyes–
faqsarrayyes–
querystringyes–

No examples provided.

Install

How do I install the Flamel Public Content MCP server?

Flamel Public Content is a hosted endpoint at https://www.flamel.ai/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 · www.flamel.ai

# add to Claude Code
claude mcp add --transport http ai-flamel-public-content 'https://www.flamel.ai/mcp'
Common questions

What is the Flamel Public Content MCP server?

Flamel Public Content is an MCP server listed in the public MCP registry as ai.flamel/public-content. Read-only MCP server for Flamel.ai's public content: company overview, blog, case studies, FAQs. This page covers its hosted endpoint (https://www.flamel.ai/mcp).

Is the Flamel Public Content MCP server safe to use?

Flamel Public Content scores 91 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 Flamel Public Content MCP server expose?

Flamel Public Content exposes 9 tools: get_company_overview, search_flamel_content, list_blog_posts, get_blog_post, list_blog_categories, and 4 more. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.

Does the Flamel Public Content MCP server require authentication?

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

Is the Flamel Public Content MCP server still maintained?

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