Flarelink
NPM · @FLARELINK/MCP · SCANNED SEP 20
Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 628 tokens (~52/item across 12 items; 11 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the Flarelink MCP server?
Flarelink runs locally as an npm package, launched with npx -y @flarelink/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @flarelink/mcp
claude mcp add dev-flarelink-mcp -- npx -y @flarelink/mcp
{
"mcpServers": {
"dev-flarelink-mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
} {
"servers": {
"dev-flarelink-mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
} codex mcp add dev-flarelink-mcp -- npx -y @flarelink/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-flarelink-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@flarelink/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-flarelink-mcp --command npx --arg -y --arg @flarelink/mcp
mcp_servers:
dev-flarelink-mcp:
command: "npx"
args: ["-y", "@flarelink/mcp"] {
"McpServers": {
"dev-flarelink-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@flarelink/mcp"
]
}
}
} assistant mcp add dev-flarelink-mcp -t stdio -c npx -a -y @flarelink/mcp
{
"mcpServers": {
"dev-flarelink-mcp": {
"command": "npx",
"args": [
"-y",
"@flarelink/mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.83 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@flarelink/mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
flarelink_cost_patterns Cloudflare cost-optimization patterns ~68
Design guidance (not a live usage meter) for keeping a Cloudflare bill near zero. Optionally describe the feature you are building to get targeted hints first.
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | – | Optional: describe the feature/data shape (e.g. "user avatar uploads") for targeted hints. |
No output schema declared.
No examples provided.
flarelink_get_pattern Get a Flarelink code pattern ~90
Return the canonical, copy-pasteable code for one Flarelink-stack recipe (auth setup, route guards, identifier-safe D1 queries, R2 uploads/presigning, wrangler bindings, SDK usage). Prefer these over inventing your own — they encode the security + cost rules.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | Which pattern to fetch. Use flarelink_list_patterns to see the options. |
No output schema declared.
No examples provided.
flarelink_list_buckets Flarelink — list R2 buckets ~25
List the R2 buckets attached to the active Flarelink project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flarelink_list_databases Flarelink — list D1 databases ~36
List the D1 databases attached to the active Flarelink project (id, name, whether it hosts the auth module).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flarelink_list_patterns List Flarelink code patterns ~33
List the available canonical code patterns (keys + what each is for). Use flarelink_get_pattern to fetch one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flarelink_list_projects Flarelink — list projects ~23
List the Flarelink projects on the active Cloudflare connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flarelink_query_database Flarelink — query a D1 database ~121
Run a SQL statement against one of the project's D1 databases via Flarelink. Use bound parameters (? placeholders + params) — never concatenate user input. Returns rows + query meta (duration, rows_read/written). This runs with full database access; prefer SELECT unless you intend to write.
| Name | Type | Req | Description |
|---|---|---|---|
| databaseId | string | yes | D1 database id (uuid) — from flarelink_list_databases. |
| params | array | – | Values bound to the ? placeholders, in order. |
| sql | string | yes | SQL with ? placeholders for any values. |
No output schema declared.
No examples provided.
flarelink_scaffold Scaffold a Flarelink-stack app ~47
How to bootstrap a complete, working Flarelink-stack app (auth + D1 + R2): clone command, one-click deploy, file map, and where to add features.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flarelink_sdk_reference @flarelink/client SDK reference ~63
Signatures and return shapes for the @flarelink/client SDK (auth / storage / db). Use when the app talks to a hosted Flarelink auth Worker rather than embedding better-auth.
| Name | Type | Req | Description |
|---|---|---|---|
| surface | string | – | Which surface to return. Defaults to all. |
No output schema declared.
No examples provided.
flarelink_stack_overview Flarelink stack overview ~58
Read this first. The Flarelink stack (Cloudflare auth via better-auth + KV sessions, D1, R2), its cardinal rules, and the two deployment shapes. Call before building auth/database/file features on Cloudflare.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flarelink_whoami Flarelink — who am I ~44
Verify the FLARELINK_API_KEY and show the signed-in user plus the active Cloudflare connection and project. Call this first to confirm management tools are wired up.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Flarelink MCP server?
Flarelink is an MCP server listed in the public MCP registry as dev.flarelink/mcp. Build on the Flarelink stack, Cloudflare auth, D1, and R2, from your AI coding tools. This page covers its npm package (@flarelink/mcp).
Is the Flarelink MCP server safe to use?
Flarelink scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Flarelink MCP server expose?
Flarelink exposes 11 tools: flarelink_stack_overview, flarelink_scaffold, flarelink_list_patterns, flarelink_get_pattern, flarelink_sdk_reference, and 6 more. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.
Is the Flarelink MCP server still maintained?
Flarelink is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Flarelink MCP server under?
Flarelink declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.