
这个寄存器包含用于遵守Cow的MCP服务器. 它利用四个专门的服务器——规则、透视、工作流程和助理——实现GRC任务自动化、执行合规规则和.
概览
MCP(Model Context Protocol)服务器被设计用于处理AI代理商的结构化请求,执行特定域的操作,并返回上下文感应. 遵义Cow MCP服务器能够与Claude桌面和Goose桌面/CLI等兼容MCP的主机进行无缝集成,实现安全,模块化,智能化的合规自动化. 遵义Cow MCP服务器支持与您MCP主机实现无缝本地集成. 核心是评估、证据和遵约状况等数据的持续吸收。 服务器从 : - 用于语义搜索的矢量存储 - 结构数据的关系数据库 - 关系查询的图表数据库 - 证据文物的文件存储系统 我们把遵义牛的MCP工具组织成四个不同的服务器。 在MCP生态系统中,每台服务器使用的工具较少,结果更好,性能更好.
概述(AI 翻译)
□ 目录
- 导言
- 词汇表
- 结构
- MCP服务器
- 开始
- 先决条件
- 认证
- 安装
- 配置
- MCP 主机设置
- 克劳德桌面
- 鹅桌面/CLI
- 在当地运行
- 工具参考
- 财务问题
– – . . .
□ 导言
MCP(Model Context Protocol)服务器被设计用于处理AI代理商的结构化请求,执行特定域的操作,并返回上下文感应. 遵义Cow MCP服务器能够与Claude桌面和Goose桌面/CLI等兼容MCP的主机进行无缝集成,实现安全,模块化,智能化的合规自动化.
– – . . .
□ 词汇表
关键词 描述 实例 |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- • 遵守或安全控制,以确保遵守条例、标准和政策 评估********* ********* ******************************** ********************************************************************************************************************************************************************************************************* ** 评估运行** * 在评估中核实某一时期的控制措施,包括收集证据
本页由 AI 翻译,技术细节请以原文为准。
README
以下为原文 README 节选,完整内容请查看原文。
ComplianceCow MCP Servers
Table of Contents
- Introduction
- Glossary
- Architecture
- MCP Servers
- Getting Started
- MCP Host Setup
- Running Locally
- Tools Reference
- FAQ
Introduction
MCP (Model Context Protocol) servers are designed to process structured requests from AI agents, perform domain-specific operations, and return context-aware responses. The ComplianceCow MCP servers enable seamless integration with MCP-compatible hosts like Claude Desktop and Goose Desktop/CLI for secure, modular, and intelligent compliance automation.
Glossary
| Keyword | Description | Example |
|---|---|---|
| Control | A compliance or security control that needs to be implemented to ensure adherence to regulations, standards, and policies | Ensure MFA is enabled for all users |
| Assessment | A collection of controls organized hierarchically, representing an industry standard or cybersecurity framework | PCI DSS 4.0 |
| Assessment Run | The verification of controls in an assessment for a given time period, including evidence collection | - |
| Check | A rule or verification for compliance or conformance | Check if MFA is enabled for all AWS users |
| Resource Type | Category or class of resources | AWS EC2, AWS S3 |
| Resource | Instance of a resource type for which checks are performed | Specific EC2 instances, GitHub repositories |
| Asset | A group of resources of various types | AWS services, Kubernetes, GitHub |
| Evidence | Data aggregated through checks against resources for a given control | CSV file with AWS users and their MFA status |
| Action | Activity (automated or manual) to respond or remediate based on conditions | Create a JIRA ticket for non-compliant EC2 instance |
| Rule | A reusable automation unit that executes tasks and generates evidence | AWS MFA Compliance Check Rule |
| Workflow | An event-driven automation sequence with conditions and activities | Alert workflow on critical finding |
Architecture
The ComplianceCow MCP servers support the STDIO transport mechanism for seamless local integration with your MCP host. At the core is the Compliance Graph, which continuously ingests data such as assessment runs, evidence, and compliance status. The server actively pulls information from:
- Vector stores for semantic search
- Relational databases for structured data
- Graph databases for relationship queries
- File storage systems for evidence artifacts
MCP Servers
We have organized ComplianceCow’s MCP tools into 4 distinct servers.
安装
This server does not publish a one-line install command.
Open the repository installation guide 新手?先看 mcpskill.org 教程 →配置
{
"mcpServers": {
"ComplianceCow-Rules": {
"command": "<UV_BIN_PATH>",
"args": [
"--directory",
"<PATH_TO_COW_MCP_REPO>",
"run",
"main.py"
],
"env": {
"CCOW_HOST": "<YOUR_CCOW_HOST>",
"CCOW_CLIENT_ID": "<YOUR_CLIENT_ID>",
"CCOW_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>",
"MCP_TOOLS_TO_BE_INCLUDED": "rules"
}
},
"ComplianceCow-Insights": {
"command": "<UV_BIN_PATH>",
"args": [
"--directory",
"<PATH_TO_COW_MCP_REPO>",
"run",
"main.py"
],
"env": {
"CCOW_HOST": "<YOUR_CCOW_HOST>",
"CCOW_CLIENT_ID": "<YOUR_CLIENT_ID>",
"CCOW_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>",
"MCP_TOOLS_TO_BE_INCLUDED": "insights"
}
},
"ComplianceCow-Workflow": {
"command": "<UV_BIN_PATH>",
"args": [
"--directory",
"<PATH_TO_COW_MCP_REPO>",
"run",
"main.py"
],
"env": {
"CCOW_HOST": "<YOUR_CCOW_HOST>",
"CCOW_CLIENT_ID": "<YOUR_CLIENT_ID>",
"CCOW_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>",
"MCP_TOOLS_TO_BE_INCLUDED": "workflow"
}
},
"ComplianceCow-Assistant": {
"command": "<UV_BIN_PATH>",
"args": [
"--directory",
"<PATH_TO_COW_MCP_REPO>",
"run",
"main.py"
],
"env": {
"CCOW_HOST": "<YOUR_CCOW_HOST>",
"CCOW_CLIENT_ID": "<YOUR_CLIENT_ID>",
…