Framework-driven — map policies and controls to any regulatory framework
← MCP server registry
Security & governancePublic source
Compliance MCP Server
Regulatory compliance engine for ADK-Rust Enterprise agents. Provides 27 MCP tools covering the full compliance lifecycle — frameworks, policies, controls, audits, findings, evidence collection, risk assessments, gap…
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
Audit lifecycle — plan, execute, find, remediate, close
Evidence-based — collect and link evidence to controls for audit readiness
Risk matrix — likelihood x impact scoring with auto-classification
Gap analysis — identify missing controls, untested controls, missing evidence
GDPR built-in — DSAR management with 30-day SLA tracking
Incident response — report, investigate, contain, resolve
Architecture
How Compliance MCP Server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
01
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
02
MCP client
Discovers schemas, sends calls, and receives typed content.
03
Compliance MCP Server
Validates the request and owns 27 documented tool contracts.
04
Domain system
Keeps the API, data, credentials, and business rules behind the server.
This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.
Tool catalog
What can an agent ask Compliance MCP Server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
27 named tools
framework_createRegister framework (GDPR, SOX, HIPAA, ISO27001, PCI-DSS, SOC2, NIST, custom)
see documentationframework_listList all registered frameworks
see documentationpolicy_createCreate policy (data protection, access control, incident response, etc)
see documentationpolicy_listList policies with review status
see documentationcontrol_createCreate control (preventive, detective, corrective) linked to policy
see documentationcontrol_listList controls with testing status
see documentationcontrol_testMark control as tested
see documentationaudit_createCreate audit (internal, external, certification)
see documentationaudit_listList audits with findings count
see documentationfinding_createRecord finding (critical, high, medium, low)
see documentationfinding_updateUpdate status (open, in_progress, remediated, accepted, closed)
see documentationfinding_listList findings with open count
see documentationGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
27 see documentation
- Audit lifecycle — plan, execute, find, remediate, close
- Evidence-based — collect and link evidence to controls for audit readiness
- Incident response — report, investigate, contain, resolve
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
Completion
rmcp
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
Install
cargo install mcp-complianceMCP client configuration
{
"mcpServers": {
"compliance": { "command": "mcp-compliance" }
}
}Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in security & governance.
Approval MCP ServerA multi-stage approval workflow engine for ADK-Rust Enterprise legal and media-content agents. 17 MCP tools: configurable workflow templates, stage rules (all-of / any-of / quorum), decisions with delegation and…17 toolsCredentials Vault MCP ServerScoped, auditable credential access for ADK-Rust Enterprise agents. Provides 8 MCP tools over 5 pluggable vault backends — never exposes raw secrets to LLM context.8 toolsDevice Management MCP ServerYour AI agent becomes a sysadmin. 44 MCP tools that observe, diagnose, and act on real devices — covering device management, endpoint security, and network operations in one server. Cross-platform (macOS, Linux,…44 tools
Source record
Release and repository metadata for this catalog entry.
- Version
- 1.0.0
- License
- Apache-2.0
- Tools
- 27
- Revision
- 71e62a746de7
- Updated
- May 27, 2026
Transportsstdio