MCP

MCP安全风控

提供方 FerrLabs · 包名 @ferrlabs/mcp

安全风控 Streamable HTTP OAuth 授权 社区 / 第三方 ClaudeCursor
查看接入方式

FerrLabs MCP is a Model Context Protocol server that exposes the unified FerrLabs API for FerrFlow, FerrVault, FerrTrack, FerrGrowth, FerrFleet and FerrLens to AI assistants, with stdio/HTTP transports and OAuth or token authentication for local development, CI/scripted and headless integrations.

一句话选型结论

按资料字段整理

MCP 属于安全风控类 MCP 服务器,Streamable HTTP,OAuth 授权,可直接接入 Claude、Cursor,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式Streamable HTTP 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Blend Deployment Model Context Protocol AI assistant integration TypeScript Unified API OAuth authentication Secrets management Project tracking Website operations SEO audit

支持客户端

适用场景

Blend DeploymentModel Context ProtocolAI assistant integration

安装与配置

Streamable HTTP OAuth 授权
新一代远程传输,替代 SSE
npx -y @ferrlabs/mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP当前 未标注 Streamable HTTP 远程部署 有 2026-10-10
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方FerrLabs上游标注的维护方 FerrLabs
分类安全风控本站按上游分类展示
连接方式Streamable HTTP新一代远程传输,替代 SSE
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@ferrlabs/mcp · node本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-10-10上游最后核验时间

详细介绍

19.4 KB
来自项目仓库与上游目录的原文,未做删改

FerrLabs MCP

Let your AI assistant drive the FerrLabs suite.

A Model Context Protocol server exposing FerrFlow, FerrVault,

FerrTrack, FerrGrowth, FerrFleet and FerrLens through the unified FerrLabs API.

npm · FerrLabs · Changelog

Runs locally over stdio, or over Streamable HTTP behind a gateway. The first tool call that needs
auth opens a browser for an OAuth loopback flow and saves the token, so there is no environment
variable to set up front.

Quick Start

Add to your MCP client configuration (Claude Code, Cursor, etc.):```json
{
"mcpServers": {
"ferrlabs": {
"command": "npx",
"args": ["-y", "@ferrlabs/mcp"]
}
}
}


The first time you call a tool that needs auth, the MCP opens `auth.ferrlabs.com` in your default browser (OAuth 2.0 loopback PKCE). After you click Allow, the token is saved locally and reused for future sessions. No env var required.

### CI / scripted / headless use

Bypass the browser dance by injecting a token directly:```json
{
  "mcpServers": {
    "ferrlabs": {
      "command": "npx",
      "args": ["-y", "@ferrlabs/mcp"],
      "env": { "FERRLABS_API_TOKEN": "fl_..." }
    }
  }
}

Create the token from app.ferrlabs.com → Settings → API Tokens. It's forwarded as x-api-token to api.ferrlabs.com.

MCP servers

This repo ships @ferrlabs/mcp, the unified entrypoint (orgs, billing, profile, public stats, docs), and @ferrlabs/mcp-core, the shared core every FerrLabs MCP server is built on. The product servers live next to their product. Add only the servers you need to your client config.

Package Repo Targets Base URL env
@ferrlabs/mcp this repo api.ferrlabs.com (unified) API_URL
@ferrvault/mcp FerrVault api.ferrvault.com FERRVAULT_API_URL
@ferrtrack/mcp FerrTrack api.ferrtrack.com FERRTRACK_API_URL
@ferrgrowth/mcp FerrGrowth api.ferrgrowth.com FERRGROWTH_API_URL
@ferrfleet/mcp FerrFleet api.ferrfleet.com FERRFLEET_API_URL
@ferrlens/mcp FerrLens api.ferrlens.com FERRLENS_API_URL

Tool lists, product variables and development notes for each product server are in the mcp/ README of its repo. All servers except @ferrlens/mcp and @ferrvault/mcp share the same auth resolution (env token or OAuth loopback, see below). @ferrvault/mcp talks to the FerrVault API, which refuses fft_* API tokens; its auth is documented in FerrVault. @ferrlens/mcp is anonymous: the FerrLens free tools take no account, it never sends a token and never opens the OAuth flow, and the API rate limits each caller by IP. Register several at once:```json
{
"mcpServers": {
"ferrlabs": { "command": "npx", "args": ["-y", "@ferrlabs/mcp"] },
"ferrvault": { "command": "npx", "args": ["-y", "@ferrvault/mcp"] },
"ferrtrack": { "command": "npx", "args": ["-y", "@ferrtrack/mcp"] },
"ferrgrowth": { "command": "npx", "args": ["-y", "@ferrgrowth/mcp"] },
"ferrfleet": { "command": "npx", "args": ["-y", "@ferrfleet/mcp"] },
"ferrlens": { "command": "npx", "args": ["-y", "@ferrlens/mcp"] }
}
}


Tools marked **destructive** below are irreversible or high-impact (spend quota, switch live serving, delete data). MCP clients should gate them behind a confirmation.

### `@ferrlabs/mcp` (unified)

| Tool                                                                                               | Scope  | Notes                                                                                                            |
| -------------------------------------------------------------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------------------------- |
| `get_stats`, `health_check`, `fetch_docs`                                                          | public | No auth required                                                                                                 |
| `get_me`, `update_me`, `export_my_account`, `list_my_sessions`, `revoke_my_session`                | auth   | Current user                                                                                                     |
| `list_orgs`, `get_org`, `get_org_overview`, `get_org_usage`, `update_org`, `list_org_audit`        | auth   | Organizations                                                                                                    |
| `list_org_members`, `invite_org_member`, `remove_org_member`, `update_org_member_role`             | auth   | `invite_org_member` emails an invitation the invitee must accept; `remove_org_member` is **destructive**         |
| `list_teams`, `create_team`, `update_team`, `delete_team`, `add_team_member`, `remove_team_member` | auth   | `delete_team` is **destructive**                                                                                 |
| `list_projects`, `list_vaults`, `list_issues`                                                      | auth   | Cross-product lists                                                                                              |
| `list_subscriptions`, `activate_subscription`, `update_subscription`, `cancel_subscription`        | auth   | `cancel_subscription` is **destructive**                                                                         |
| `list_tokens`, `create_token`, `revoke_token`                                                      | auth   | `create_token` is disabled unless `FERRLABS_MCP_ALLOW_TOKEN_REVEAL=1`; `revoke_token` is **destructive**         |
| `list_org_tokens`, `create_org_token`, `revoke_org_token`                                          | auth   | `create_org_token` is disabled unless `FERRLABS_MCP_ALLOW_TOKEN_REVEAL=1`; `revoke_org_token` is **destructive** |

FerrFlow CLI-specific tools (`dry_run`, `validate_config`, `read_config`, `read_changelog`, `list_release_tags`, `record_event`) were removed in v4.0.0. They required either a local FerrFlow CLI install or HMAC signing the MCP doesn't do. Use the FerrFlow CLI directly or fetch docs via `fetch_docs("ferrflow", "docs/...")`.

## Resources and prompts

Tools are not the only surface. A resource is content a client attaches once and keeps, instead of spending a turn on a tool call and leaving a blob in the transcript.

| Server          | Resource                         | What it holds                                                                    |
| --------------- | -------------------------------- | -------------------------------------------------------------------------------- |
| `@ferrlabs/mcp` | `ferrlabs://org/{slug}/overview` | member count, active subscriptions per product, pending invites, recent activity |
| `@ferrlabs/mcp` | `ferrlabs://org/{slug}/usage`    | current-period metered usage per product, with the tier limit                    |

The org resources enumerate themselves, so a client can browse them. Resource handlers call the same fetch functions the tools use, so a path is defined once. Capabilities are declared by the SDK when a resource or prompt is registered, so a server that exposes neither advertises neither. The product servers document their own resources and prompts in their repos.

## Stack

| Component | Technology                         |
| --------- | ---------------------------------- |
| Runtime   | Node.js 22+                        |
| Language  | TypeScript                         |
| MCP SDK   | @modelcontextprotocol/sdk          |
| Transport | stdio (default) or Streamable HTTP |

## Configuration

| Variable                          | Description                                                                                                                                                                                                                                                         | Default                                                                       |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| `API_URL`                         | FerrLabs API base URL (no `/v1` suffix, paths are prefixed in code)                                                                                                                                                                                                 | `https://api.ferrlabs.com`                                                    |
| `FERRLABS_AUTH_URL`               | Auth SPA base URL (where the OAuth browser flow lands)                                                                                                                                                                                                              | `https://auth.ferrlabs.com`                                                   |
| `FERRLABS_API_TOKEN`              | Pre-provisioned token. Bypasses the OAuth flow. Use for CI / scripted environments.                                                                                                                                                                                 | _(unset)_                                                                     |
| `FERRFLOW_API_TOKEN`              | **Deprecated**, accepted as a fallback for backward compatibility with v3.x.                                                                                                                                                                                        | _(unset)_                                                                     |
| `FERRLABS_MCP_NO_OAUTH`           | Set to `1` to disable the OAuth fallback. Then `FERRLABS_API_TOKEN` becomes required.                                                                                                                                                                               | unset                                                                         |
| `FERRLABS_MCP_TOKEN_PATH`         | Override the path where the OAuth-acquired token is persisted.                                                                                                                                                                                                      | `%APPDATA%\ferrlabs\mcp\token.json` / `~/.config/ferrlabs/mcp/token.json`     |
| `FERRLABS_MCP_NO_PERSIST`         | Set to `1` to keep the token in memory only (re-auth on every cold start).                                                                                                                                                                                          | unset                                                                         |
| `FERRLABS_MCP_ALLOWED_API_HOSTS`  | Extra hosts a token may be sent to, comma separated. The FerrLabs product APIs are allowed by default; anything else is refused. Loopback is always allowed.                                                                                                        | —                                                                             |
| `FERRLABS_MCP_ALLOW_TOKEN_REVEAL` | Set to `1` to let `create_token` mint a token (and `create_server_token` in `@ferrgrowth/mcp`) and return its secret. Off by default: the secret is shown once, so the tool has to put it in its response, and tool results are persisted to the client transcript. | —                                                                             |
| `FERRLABS_MCP_MAX_TOOL_BYTES`     | Ceiling on a single tool response, in bytes. Beyond it the payload is cut and explicitly marked as incomplete.                                                                                                                                                      | `100000`                                                                      |
| `FERRLABS_MCP_MODE`               | Transport: `stdio` (default) or `http` (Streamable HTTP). `--http` also selects http.                                                                                                                                                                               | `stdio`                                                                       |
| `PORT`                            | Port for the HTTP transport (`FERRLABS_MCP_MODE=http`).                                                                                                                                                                                                             | `3000`                                                                        |
| `HOST`                            | Bind address for the HTTP transport.                                                                                                                                                                                                                                | `127.0.0.1` (`0.0.0.0` in the Docker image or with `FERRLABS_MCP_BIND_ALL=1`) |
| `FERRLABS_MCP_PUBLIC_URL`         | URL clients reach the HTTP transport at. Advertised as the OAuth `resource` and in the 401 challenge; request headers are never used for it. Required when `HOST` is not loopback.                                                                                  | `http://127.0.0.1:$PORT` on loopback                                          |
| `FERRLABS_MCP_ALLOWED_HOSTS`      | Host headers the HTTP transport answers, comma separated, ports ignored. Anything else gets a 421, except the health endpoints.                                                                                                                                     | the host of `FERRLABS_MCP_PUBLIC_URL`, or the loopback names                  |

### Checking the version

Every server binary prints its name and version and exits when passed `--version` (or `-v`), without starting a transport:```bash
npx -y @ferrtrack/mcp --version
# ferrtrack 9.5.0

Clients get the same value at runtime in the serverInfo of the MCP initialize response.

HTTP transport

By default the server runs over stdio. Set FERRLABS_MCP_MODE=http (or pass --http) to expose the MCP over Streamable HTTP on HOST:PORT (0.0.0.0:3000 by default), which is the mode the Docker image runs. Requests carry the bearer token in the Authorization header. Run the HTTP transport behind a gateway (e.g. Traefik) that terminates TLS and applies rate limiting / request-size caps; do not expose it directly on an untrusted network. Each bearer is checked against GET /auth/me on the authorization server (FERRLABS_AUTH_URL, default https://api.ferrlabs.com) before a server is built: a rejected token gets a 401 and an unreachable auth server gets a 503. Accepted tokens are cached for 60 seconds. The token is still forwarded to the product APIs, since the authorization server does not yet issue audience-bound or exchangeable tokens.

Bound to anything other than loopback, the server refuses to start without FERRLABS_MCP_PUBLIC_URL. That URL is the only source of the OAuth resource identifier, so a forged Host or X-Forwarded-Host cannot make the server advertise someone else's host, and its hostname is the default Host allowlist:```bash
FERRLABS_MCP_MODE=http HOST=0.0.0.0 FERRLABS_MCP_PUBLIC_URL=https://mcp.ferrlabs.com npx -y @ferrlabs/mcp


### How auth resolution works

On the first authenticated tool call, the MCP looks for a token in this order:

1. In-memory cache (set during this MCP process's lifetime)
2. `FERRLABS_API_TOKEN` (or `FERRFLOW_API_TOKEN`) env var
3. Persisted token file (`FERRLABS_MCP_TOKEN_PATH`)
4. **OAuth 2.0 loopback PKCE flow**: opens the user's browser at `FERRLABS_AUTH_URL` (`auth.ferrlabs.com`, the login SPA), captures the callback on `http://127.0.0.1:54321/cb`, then exchanges the code for a session token via `POST /v1/auth/exchange` on `API_URL` (`api.ferrlabs.com`). Token is persisted to step 3 for future sessions.

If you set `FERRLABS_MCP_NO_OAUTH=1`, step 4 is skipped, which is what you want in CI where opening a browser would hang.

> **Auth host split.** `auth.ferrlabs.com` is the user-facing login SPA (where the browser `authorize` step lands); `api.ferrlabs.com` performs the token exchange and serves the OAuth discovery metadata used by the HTTP transport. Configure `FERRLABS_AUTH_URL` for the former and `API_URL` for the latter. They are not interchangeable.

## Smoke test

`pnpm smoke` builds the server, spawns it over stdio, runs the MCP `initialize`/`tools/list` handshake, then calls `health_check` and `get_stats` against the real `api.ferrlabs.com`. Useful to confirm the server boots, registers all tools, and the API is reachable. Exits non-zero on any failure.```
[PASS] initialize handshake, serverInfo: ferrlabs@6.5.0
[PASS] tools/list, N tools registered
[PASS] tools/call health_check, {"status":"ready", ...}
[PASS] tools/call get_stats, total_releases=N

Smoke: 4/4 OK

FerrVault MCP

@ferrvault/api-mcp was merged into @ferrvault/mcp, which now talks to the FerrVault API directly instead of the unified FerrLabs API. The former @ferrvault/mcp tools (get_vault, list_secrets, create_secret, ...) are gone, replaced by the *_ferrvault_* tools. See the FerrVault MCP README.

Migrating the sub-MCP package names

The four product sub-MCPs moved to their product's npm scope in 8.0.0. The unified server and the shared core did not move.

Old name New name
@ferrlabs/mcp-vault @ferrvault/mcp
@ferrlabs/mcp-track @ferrtrack/mcp
@ferrlabs/mcp-growth @ferrgrowth/mcp
@ferrlabs/mcp-fleet @ferrfleet/mcp
@ferrlabs/mcp unchanged
@ferrlabs/mcp-core unchanged

Update the package name in your MCP client config; nothing else changes. Tools, arguments and environment variables are identical, and the servers still target the same product APIs.

npm has no redirect for a renamed package. The old names stay installable at 7.0.2 forever and are deprecated with a pointer here, but they receive no further releases, security fixes included. Move off them.

The binaries were renamed to match, so ferrlabs-mcp-track is now ferrtrack-mcp. That matters only if you invoke them directly rather than through npx. The GHCR images moved the same way, from ghcr.io/ferrlabs/mcp-track to ghcr.io/ferrlabs/ferrtrack-mcp; the old image tags stay published but stop receiving new versions.

Migrating from @ferrflow/mcp v3.x

v4.0.0 renames the package and points the MCP at the unified FerrLabs API. To migrate:

  1. Replace @ferrflow/mcp with @ferrlabs/mcp in your MCP client config.
  2. Rename FERRFLOW_API_TOKEN → FERRLABS_API_TOKEN (the old name still works for one release).
  3. If you were overriding API_URL=https://api.ferrflow.com, drop the override. The default is now https://api.ferrlabs.com.

Tokens issued by the legacy FerrFlow-only API are not valid against the unified API. Create a fresh one from app.ferrlabs.com.

License

Mozilla Public License 2.0, see LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP 怎么安装?

在客户端按下面的安装命令接入:npx -y @ferrlabs/mcp。对应的包名是 @ferrlabs/mcp。装完在客户端配置里引用同一个包或端点。

MCP 怎么在 Claude、Cursor 里配置?

它的传输方式是Streamable HTTP,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

MCP 支持哪些客户端?

资料标注支持 Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP 能提供哪些能力?

资料显示能力标签包括 Blend Deployment、Model Context Protocol、AI assistant integration、TypeScript、Unified API、OAuth authentication。具体工具清单以官方文档为准。

MCP 需要什么运行环境?

运行时为 node;属于远程端点,不需要在本地装运行时。

MCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为Streamable HTTP。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-10-10。