Security Controls MCP Server

▶ Try this MCP instantly via Ansvar Gateway

50 free queries/day · no card required · OAuth signup at ansvar.eu/gateway

One endpoint, one OAuth signup, access from any MCP-compatible client.

Connect

Claude Code (one line):

claude mcp add ansvar --transport http https://gateway.ansvar.eu/mcp

Claude Desktop / Cursor — add to claude_desktop_config.json (or mcp.json):

{
  "mcpServers": {
    "ansvar": {
      "type": "url",
      "url": "https://gateway.ansvar.eu/mcp"
    }
  }
}

Claude.ai — Settings → Connectors → Add custom connector → paste https://gateway.ansvar.eu/mcp

First request opens an OAuth flow at ansvar.eu/gateway. After signup, your client is bound to your account; tier (free / premium / team / company) determines fan-out, quota, and which downstream MCPs are reachable.

Self-host this MCP

You can also clone this repo and build the corpus yourself. The schema, fetcher, and tool implementations all live here. What is not in the repo is the pre-built database — TDM and standards-licensing constraints on the upstream sources mean we host the corpus on Ansvar infrastructure rather than redistribute it as a public artifact.

Build your own: run this repo's ingestion script (entry-point varies per repo — typically scripts/ingest.sh, npm run ingest, or make ingest; check the repo root).

Related MCP server: Security Context MCP Server

Overview

THE definitive MCP server for security framework mapping. Makes 1,451 security controls across 262 SCF-mapped frameworks searchable and AI-accessible through Claude, Cursor, or any MCP-compatible client.

Built on the Secure Controls Framework (SCF) by ComplianceForge.

Key capabilities:

• 1,451 security controls across governance, risk, compliance, and technical domains

• 262 SCF-mapped frameworks including ISO 27001, NIST CSF, DORA, PCI DSS, CMMC, and TIBER-EU

• AI Governance: ISO 42001, NIST AI RMF, EU AI Act, Cyber Resilience Act

• Bidirectional mapping between frameworks via SCF rosetta stone

• Bundled public national framework profiles for BIO, KATAKRI, NSM, MSB, CFCS, CCB, and ANSSI

• Optional integration with purchased standards (ISO, NIST 800-53) for official text

• Full-text search across all control descriptions

• Natural language queries instead of framework-specific IDs

Why This Exists

Different frameworks describe the same security measures in different ways. ISO 27001 has one control ID, NIST CSF has another, PCI DSS has yet another — but they're all talking about the same thing.

This MCP server provides instant bidirectional mapping between any two frameworks via the SCF rosetta stone. Ask Claude "What DORA controls does ISO 27001 A.5.15 map to?" and get an immediate answer backed by ComplianceForge's framework database.

Example Queries

• "What does GOV-01 require?"

• "Search for controls about encryption key management"

• "What ISO 27001 controls map to DORA?"

• "List all controls needed for PCI DSS compliance"

• "Which DORA requirements does ISO 27001 A.5.15 satisfy?"

• "Show me all NIST CSF 2.0 controls related to incident response"

• NEW: "What ISO 42001 controls map to NIST AI RMF?"

• NEW: "Show me EU AI Act requirements for high-risk AI systems"

Available Frameworks (262)

AI Governance (NEW in v0.4.0)

• ISO 42001:2023 (149) - AI Management System

• NIST AI RMF 1.0 (158) - AI Risk Management Framework

• NIST AI 600-1 (139) - Generative AI Profile

• EU AI Act (119) - Regulation 2024/1689

• EU Cyber Resilience Act (18)

Core Frameworks

• US Government: NIST 800-53 R5 (777), NIST CSF 2.0 (253), FedRAMP R5 (423), CMMC 2.0 (198/52)

• International Standards: ISO 27001 (51), ISO 27002 (316), ISO 27017 (119), ISO 27018 (70), ISO 27701 (187), ISO 22301 (52)

• US Industry: PCI DSS v4.0.1 (364), SOC 2 (412), HIPAA (136), SOX (2)

• Financial: SWIFT CSCF 2023 (127), FFIEC (231), GLBA (108), DORA (103)

• Cloud: CSA CCM v4 (334), Germany C5 (239)

Regional Coverage (50+ countries)

• APAC: Australia ISM/Essential 8, Singapore MAS TRM, Japan ISMAP, China Cybersecurity Law, India DPDPA

• EU: GDPR (42), NIS2 (68), PSD2 (61), plus 20+ national frameworks

• Americas: US state laws (CA, NY, TX, etc.), Brazil LGPD, Canada PIPEDA

• Middle East/Africa: Saudi SAMA, UAE NIAF, South Africa POPIA

Specialized

• Industrial/OT: IEC 62443 (197), NERC CIP (224), NIST 800-82

• Automotive: ISO/SAE 21434, TISAX, UN R155

• Healthcare/MedDev: HIPAA, HITRUST, CMS MARS-E, IEC 81001-5-1, IMDRF N60/N73, FDA Premarket Cybersecurity

See docs/coverage.md for the complete list of 262 SCF-mapped frameworks.

Tools

Core Tools

version_info() - Get server version, statistics, and top frameworks

• Call this first to understand what data is available

list_frameworks() - List all 262 SCF-mapped frameworks with control counts

get_control(control_id) - Get full details for a specific SCF control

• Returns description, domain, weight, PPTDF category, and mappings to all 262 SCF-mapped frameworks

search_controls(query, frameworks=[], limit=10) - Search controls by keyword

• Optional framework filtering

• Full-text search across names and descriptions

get_framework_controls(framework) - Get all controls for a specific framework

• Returns controls organized by domain

map_frameworks(source_framework, target_framework, source_control=None) - Map between frameworks

• Bidirectional mapping via SCF

• Optional filtering to specific source control

Standards Tools

list_available_standards() - List all available standards (SCF + bundled public profiles + imported)

query_standard(standard, query, limit=10) - Search within a bundled public profile or purchased standard

• Bundled public profiles return curated summaries with official source links

• Purchased standards require import first and return clause text from the user's copy

get_clause(standard, clause_id) - Get a specific clause or section

• Bundled public profiles return curated summary sections

• Purchased standards require import first for official clause text

Bundled Public National Profiles

These profiles are available immediately after install and are sourced from official public publications:

• netherlands_bio - Netherlands BIO2

• finland_katakri - Finland KATAKRI 2020

• norway_nsm - Norway NSM Basic Principles for ICT Security

• sweden_msb - Sweden MSB information security and incident reporting profile

• denmark_cfcs - Denmark CFCS cyber defence profile

• belgium_ccb - Belgium CyberFundamentals (CyFun)

• france_anssi - France ANSSI cyber hygiene baseline

See PAID_STANDARDS_GUIDE.md for import instructions.

Add Purchased Standards (Optional)

Import your purchased ISO 27001, NIST SP 800-53, or other standards to get official text alongside SCF descriptions:

# Install import tools
pip install security-controls-mcp[import-tools]

# Import purchased PDF
scf-mcp-import import-standard \
  --file ~/Downloads/ISO-27001-2022.pdf \
  --type iso_27001_2022 \
  --title "ISO/IEC 27001:2022"

# Restart MCP, then query

Your paid content stays private in ~/.security-controls-mcp/ (never committed to git).

Full guide: PAID_STANDARDS_GUIDE.md

Technical Architecture

Data Pipeline: SCF JSON → In-memory index → MCP tools → AI response

Key principles:

• All control text returns verbatim from SCF source with zero LLM paraphrasing

• Framework mappings use ComplianceForge's authoritative crosswalks

• Optional purchased standards stored locally (never committed)

• Search results optimized for AI context windows

Data integrity:

• SCF version locked to 2025.4 for consistency

• All mappings sourced from official SCF framework crosswalks

• User-imported standards require valid licenses

Data Source

Based on SCF 2025.4 (released December 29, 2025)

• 1,451 controls across all domains

• 262 SCF-mapped frameworks with full mapping coverage

• Licensed under Creative Commons (data)

• Source: ComplianceForge SCF

Included data files:

• scf-controls.json - All 1,451 controls with framework mappings

• framework-to-scf.json - Reverse index for framework-to-SCF lookups

More Ansvar MCPs

Full fleet at ansvar.eu/gateway.

Development

Branching Strategy

This repository uses a dev integration branch. Do not push directly to main.

feature-branch → PR to dev → verify on dev → PR to main → deploy

• main is production-ready. Only receives merges from dev via PR.

• dev is the integration branch. All changes land here first.

• Feature branches are created from dev.

Setup

# Clone and install
git clone https://github.com/Ansvar-Systems/security-controls-mcp.git
cd security-controls-mcp
pip install -e '.[dev]'

# Install pre-commit hooks
pre-commit install

# Run tests
pytest tests/ -v

Pre-commit hooks run automatically before each commit:

• Code formatting (black, ruff)

• Linting (ruff check, YAML/JSON validation)

• Tests (pytest, smoke tests, server startup)

Bypass hooks (emergencies only): git commit --no-verify

Important Disclaimers

Not Legal or Compliance Advice: Control text is sourced directly from official SCF data, but this tool should not be used as the sole basis for compliance decisions. Always verify against official framework sources and consult qualified compliance professionals.

AI Content Restrictions: The SCF license explicitly prohibits using AI systems to generate derivative content such as policies, standards, procedures, metrics, risks, or threats based on SCF data. You may query and analyze controls, but not generate derivative compliance artifacts.

Purchased Standards: Optional standards imports require valid licenses. You must own legitimate copies and comply with copyright restrictions. This tool does not include or distribute any copyrighted standards text.

Framework Coverage: While SCF provides comprehensive mappings, not all controls map 1:1 across frameworks. Always review official framework documentation for authoritative requirements.

License

Code: Apache License 2.0 (see LICENSE)

Data: Creative Commons Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0) by ComplianceForge

• Source: Secure Controls Framework (SCF)

• Version: SCF 2025.4 (December 29, 2025)

What you MAY do:

• Query and analyze SCF controls

• Map between frameworks

• Reference controls in your own work (with attribution)

• Use this MCP server to understand control requirements

What you MAY NOT do:

• Use AI to generate policies or procedures based on SCF controls

• Create derivative frameworks or modified versions for distribution

• Remove or modify control definitions

For complete terms: SCF Terms & Conditions

More Open Source from Ansvar

We maintain a family of MCP servers for compliance and security professionals:

Browse all projects: ansvar.eu/open-source

Built by: Ansvar Systems (Stockholm, Sweden)