Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Flarelink

NPM · @FLARELINK/MCP · SCANNED AUG 3

Build on the Flarelink stack — Cloudflare auth, D1, and R2 — from your AI coding tools.

Available components

+18 this week 71 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @flarelink/mcp

# add to Claude Code
claude mcp add dev-flarelink-mcp -- npx -y @flarelink/mcp
# add to Codex CLI
codex mcp add dev-flarelink-mcp -- npx -y @flarelink/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-flarelink-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@flarelink/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-flarelink-mcp --command npx --arg -y --arg @flarelink/mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-flarelink-mcp:
    command: "npx"
    args: ["-y", "@flarelink/mcp"]
// mcp.json
{
  "mcpServers": {
    "dev-flarelink-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@flarelink/mcp"
      ]
    }
  }
}
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.

  • 2 Aug 26 +11
    • Install scripts: pass → unverified security
    • Provenance: fail → unverified security
    • Known CVEs: unverified → partial security
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.23 functional
    • Licence: MIT functional
  • 1 Aug 26 +5
    • Known CVEs: partial → unverified security
    • Malware scan: unverified → pass security
    • Dependency health: partial → unverified functional
  • 31 Jul 26 +20
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 53

    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 3 Aug 2026 · Analysed npm/@flarelink/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 11 exposed · ~608 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.

Tool Tokens
flarelink_cost_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.

NameTypeReqDescription
featurestringOptional: describe the feature/data shape (e.g. "user avatar uploads") for targeted hints.

No output schema declared.

No examples provided.

flarelink_get_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.

NameTypeReqDescription
patternstringyesWhich pattern to fetch. Use flarelink_list_patterns to see the options.

No output schema declared.

No examples provided.

flarelink_list_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 ~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 ~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 ~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 ~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.

NameTypeReqDescription
databaseIdstringyesD1 database id (uuid) — from flarelink_list_databases.
paramsarrayValues bound to the ? placeholders, in order.
sqlstringyesSQL with ? placeholders for any values.

No output schema declared.

No examples provided.

flarelink_scaffold ~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 ~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.

NameTypeReqDescription
surfacestringWhich surface to return. Defaults to all.

No output schema declared.

No examples provided.

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 ~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.