MCP Server Scf

Name: MCP Server Scf
Author: MarkAC007

作者：MarkAC007版本 3.4.2i★ –i在你的电脑上运行

注册名称app.scfcontrolsplatform/mcp-server-scf

安装

概览

作者提供的说明（英文原文）

MCP server for the SCF Controls Platform — 187 tools for controls, evidence, risk, and TPRM.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 0 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：SCF_API_KEY, SCF_API_URL

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 0 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： SCF_API_KEY, SCF_API_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "scf": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-scf"
      ],
      "env": {
        "SCF_API_KEY": "your-value",
        "SCF_API_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add scf --env SCF_API_KEY=your-value --env SCF_API_URL=your-value -- npx -y mcp-server-scf

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "scf": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-scf"
      ],
      "env": {
        "SCF_API_KEY": "your-value",
        "SCF_API_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "scf": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-scf"
      ],
      "env": {
        "SCF_API_KEY": "your-value",
        "SCF_API_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

SCF_API_KEY 机密必填 env
Your SCF Controls Platform API key. Generate in your self-hosted instance at Settings > API Keys. Starts with the scf_ prefix.
SCF_API_URL 必填 env
Base URL of your self-hosted SCF Controls Platform instance (e.g. http://localhost:8000). Required — the platform is self-hosted; there is no hosted default.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

! 注意
作者与仓库一致
发布者（scfcontrolsplatform.app）不是仓库所有者（MarkAC007）；可能是其他人代为上架的
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32545 个服务器的 0%
发布到注册中心的时间比此分类中其他 32545 个服务器的 43% 更新
基础检查结果等于或优于此分类中其他 32545 个服务器的 32%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MCP Server Scf 安全吗？

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：SCF_API_KEY, SCF_API_URL

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（3.4.2）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Python MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

Python MCP

作者：Files-com

Local-only Python MCP server for the Files.com API.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

mcp-server-scf

Security compliance controls, frameworks, and risk management for AI agents.

Give your AI assistant access to 1,451 SCF security controls, 354+ framework mappings (NIST 800-53, ISO 27001, SOC 2, FedRAMP, GDPR), evidence tracking, risk registers, and vendor risk management — all through the Model Context Protocol.

Built for the [SCF Controls Platform](https://scfcontrolsplatform.com/). Maintained by ComplianceGenie.io.

🆕 The platform is now open-source, self-hosted software. The SCF Controls Platform — SCF-native GRC tooling for the free Secure Controls Framework content — is published under AGPL-3.0 at [scf-controls-platform-oss](https://github.com/MarkAC007/scf-controls-platform-oss). Companies download and host it themselves via Docker Compose.

Having trouble? → docs/troubleshooting.md · API key setup → docs/authentication.md · How it works → docs/architecture.md

Overview

mcp-server-scf connects AI assistants to the SCF Controls Platform via MCP, enabling natural language interaction with your compliance program. Your AI can browse the full SCF control catalog, track implementation progress, manage evidence collection, assess risks, and monitor third-party vendors — all without leaving your editor or chat.

42 tools over 225 platform operations, in 16 groups. Each tool is one noun and direction — scf_vendor_read, scf_vendor_write — and its method argument picks the operation; the method description explains each one. Read tools are readOnlyHint: true, so a client can allow them all at once.

Only the core groups are in the tool list at startup (26 tools, about 27k tokens of schema instead of 71k). Call scf_load_tools with the groups you need — or all — and the rest appear; the server sends notifications/tools/list_changed. A client that ignores that notification can set SCF_LOAD_ALL_TOOLS=true to get everything up front. Per-group docs list every method with its parameters; docs/migration-consolidation.md maps each pre-v4 tool name to its tool and method.

Group	Loaded	Operations	Tools
catalog	core	8	`scf_catalog_read`
controls	core	15	`scf_control_read`, `scf_control_write`
evidence	core	25	`scf_evidence_read`, `scf_evidence_write`, `scf_evidence_file_read`, `scf_evidence_file_write`, `scf_list_evidence_tasks`, `scf_evidence_task_write`
assessments	core	17	`scf_assessment_read`, `scf_assessment_write`
risk	core	19	`scf_risk_read`, `scf_risk_write`, `scf_custom_risk_read`, `scf_custom_risk_write`
vendors	core	23	`scf_vendor_read`, `scf_vendor_write`, `scf_vendor_record_write`
systems	core	19	`scf_system_read`, `scf_system_write`, `scf_capability_theme_read`
organization	core	12	`scf_org_read`, `scf_update_org_settings`, `scf_user_read`, `scf_mark_notifications_read`
teams	on demand	11	`scf_team_read`, `scf_team_write`
collaboration	on demand	7	`scf_collaboration_read`, `scf_collaboration_write`
documents	on demand	15	`scf_document_read`, `scf_document_write`
engagements	on demand	16	`scf_engagement_read`, `scf_engagement_write`
assurance	on demand	19	`scf_assurance_read`, `scf_assurance_write`
catalog-reconciliation	on demand	9	`scf_catalog_reconciliation_read`, `scf_catalog_reconciliation_write`
webhooks	on demand	6	`scf_webhook_read`, `scf_webhook_write`
journey	on demand	4	`scf_journey_read`, `scf_journey_write`

Try it with MCP Inspector

Kick the tires without adding the server to a client — MCP Inspector launches a local UI that introspects every tool, its schema, and its description:

npx @modelcontextprotocol/inspector npx -y mcp-server-scf

Inspector opens on http://localhost:6274 and connects to mcp-server-scf over stdio. You'll see the 26 core tools (set SCF_LOAD_ALL_TOOLS=true for all 42), each with a method picker and its Zod schema rendered as a live form.

Live tool calls need your instance's URL and an API key — export SCF_API_URL and SCF_API_KEY in the same shell before launching Inspector, or set them under the "Environment Variables" tab inside the Inspector UI. Without them, you can still browse schemas and descriptions; tool calls return a configuration error.

Quick Start

1. Self-host the platform & get an API key

The SCF Controls Platform is open-source software you host yourself — there is no sign-up. Deploy it from scf-controls-platform-oss (a Docker Compose stack with bundled PostgreSQL, Redis, and MinIO), then:

Set an API_KEY in the platform's .env (generate one with openssl rand -hex 32), or create a key in Settings → API Keys once the app is running.
Note your instance's API URL — http://localhost:8000 by default, or your deployed host.

Use that key as SCF_API_KEY and the instance URL as SCF_API_URL (see Configuration).

2. Install — one-click

Pick the route for your client.

Claude Desktop — the one-click path is the signed [.mcpb Desktop Extension](#claude-desktop-extension-mcpb) below. Claude Desktop does not register a custom URL scheme, so there is no clickable deeplink; instead you drag the .mcpb onto Settings → Extensions and paste your API key once. See anthropics/claude-code#26952 for the upstream tracking issue.

Cursor — click the badge below. Cursor registers the cursor:// scheme, so the deeplink opens the IDE with the server config pre-filled:

After install, edit the pre-filled SCF_API_URL to point at your instance — there is no hosted default.

Prefer to edit config by hand, or on a client without a deeplink (Windsurf, Docker)? See [3. Manual config](#3-manual-config) below.

Claude Desktop Extension (.mcpb)

For Claude Desktop ≥ 0.11.0, the easiest install is a signed .mcpb bundle — no JSON editing, no npx runtime, no Node required on the host:

Download mcp-server-scf- .mcpb from the latest GitHub release.
Double-click the file (or drag it onto Claude Desktop → Settings → Extensions).
When prompted, paste your scf_… API key. It's stored in your OS keychain, not in a config file.
Claude Desktop restarts the server and the core tools are avai

只显示了开头部分；其余内容请在仓库中阅读