_ registry / mcp streamable-http · checked 1h ago

flamel-docs

https://docs.flamel.ai

Registry code: 38d74a1788a6ba84

api record

Read-only access to Flamel's product documentation: how the platform works, how to set it up, and how each solution behaves. Call get_docs_overview first if you have no context on Flamel. Use search_flamel_docs when you do not already know which page answers a question, then get_doc_page to read it in full. Flamel's vocabulary matters: a Hub is corporate, a Workspace is one location, a Playbook is a packaged campaign the Hub ships to Workspaces. No authentication is required and nothing here writes. For marketing content see https://www.flamel.ai/mcp; for the authenticated product API see…

endpoint
https://docs.flamel.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is flamel-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is flamel-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does flamel-docs have?
4 tools: search_flamel_docs, get_doc_page, get_docs_overview, list_docs_tree.
Is flamel-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
1,035ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 384 checks · signed record
  • degraded → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search product documentation
  • read a documentation page
  • list documentation pages
takes → gives
text → text
tools
4 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_docs_overview reads open 5h ago

    Orient yourself: what Flamel is, how the docs are organised, the vocabulary the product uses (Hub, Workspace, Playbook), and where to go for marketing content or the authenticated product API. Start here if you have no context.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_docs_tree reads open 5h ago

    List every Flamel documentation page grouped by section, with titles, slugs, and URLs. Use this to understand what documentation exists before searching, or to find the exact slug for `get_doc_page`.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "section": {
      "type": "string",
      "description": "Restrict to a top-level section, e.g. \"solutions\" or \"manage\". Omit for everything."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • search_flamel_docs reads unknown 1h ago

    Full-text search across every Flamel documentation page. Returns matching page titles, URLs, slugs, and an excerpt around the match. Use this first when you do not already know which page answers the question.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum results (1-25). Defaults to 8."
    },
    "query": {
      "type": "string",
      "description": "What to look for, e.g. \"connect a Facebook page\" or \"playbook approval\"."
    },
    "section": {
      "type": "string",
      "description": "Restrict to a top-level section, e.g. \"solutions\", \"manage\", \"reference\", \"release-notes\", \"api\"."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • get_doc_page reads unknown 5h ago

    Fetch one Flamel documentation page in full, as Markdown, by slug. The slug is the path after the domain, e.g. `solutions/blog/ai-assistant`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Page slug or full URL, e.g. \"start/quickstart-hub\" or \"https://docs.flamel.ai/start/quickstart-hub\"."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 38d74a1788a6ba84.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/38d74a1788a6ba84/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/38d74a1788a6ba84/badge.svg)](https://brick.blue/agent/38d74a1788a6ba84?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on flamel.ai 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.