# MacTech CMMC / NIST 800-171 (remote · www.mactechsolutionsllc.com)

NIST 800-171 controls and 800-171A objectives, crosswalks, exact SPRS scoring, POA&M generation.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-13

## Components

- remote · `www.mactechsolutionsllc.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-mactechsolutionsllc-www-cmmc/api-mcp.md), [page](https://verifymcp.io/servers/com-mactechsolutionsllc-www-cmmc/api-mcp)

## Channel facts

- Endpoint: `https://www.mactechsolutionsllc.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-13.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 8429 tokens (~36/item across 233 items; 13 tools + 220 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (8% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http com-mactechsolutionsllc-www-cmmc https://www.mactechsolutionsllc.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-mactechsolutionsllc-www-cmmc]
url = "https://www.mactechsolutionsllc.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mactechsolutionsllc-www-cmmc": {
      "type": "remote",
      "url": "https://www.mactechsolutionsllc.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mactechsolutionsllc-www-cmmc --url https://www.mactechsolutionsllc.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mactechsolutionsllc-www-cmmc:
    url: "https://www.mactechsolutionsllc.com/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-mactechsolutionsllc-www-cmmc": {
      "type": "http",
      "url": "https://www.mactechsolutionsllc.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-12 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-09 (score 74, +10)

We did not load change detail this far back for this component, so this day may have recorded more than is shown.

- [security] Tool “list_level1_practices” rewrote its description, which is the text the model reads
- [security] Tool “generate_poam_entries” rewrote its description, which is the text the model reads
- [security] Tool “get_assessment_objectives” rewrote its description, which is the text the model reads
- [functional regression] Resource “3.1.4 — Access Control” was removed
- [functional regression] Resource “3.13.8 — System & Communications Protection” was removed
- [functional regression] Resource “3.1.3 — Access Control” was removed
- [functional regression] Resource “3.13.6 — System & Communications Protection” was removed
- [functional regression] Resource “3.13.5 — System & Communications Protection” was removed
- [functional regression] Resource “3.6.1 — Incident Response” was removed
- [functional regression] Resource “3.10.3 — Physical Protection” was removed
- [functional regression] Resource “3.11.2 — Risk Assessment” was removed
- [functional regression] Resource “3.3.3 — Audit & Accountability” was removed
- [functional regression] Resource “3.10.6 — Physical Protection” was removed
- [functional regression] Resource “3.4.4 — Configuration Management” was removed
- [functional regression] Resource “3.12.4 — Security Assessment” was removed
- [functional regression] Resource “3.1.22 — Access Control” was removed
- [functional regression] Resource “3.3.5 — Audit & Accountability” was removed
- [functional regression] Resource “3.1.8 — Access Control” was removed
- [functional regression] Resource “3.14.1 — System & Information Integrity” was removed
- [functional regression] Resource “3.7.5 — Maintenance” was removed
- [functional regression] Resource “3.10.2 — Physical Protection” was removed
- [functional regression] Resource “3.7.3 — Maintenance” was removed
- [functional regression] Resource “3.12.3 — Security Assessment” was removed
- [functional regression] Resource “3.1.13 — Access Control” was removed
- [functional regression] Resource “3.4.9 — Configuration Management” was removed
- [functional regression] Resource “3.5.5 — Identification & Authentication” was removed
- [functional regression] Resource “3.8.1 — Media Protection” was removed
- [functional regression] Resource “3.10.1 — Physical Protection” was removed
- [functional regression] Resource “3.6.3 — Incident Response” was removed
- [functional regression] Resource “3.13.11 — System & Communications Protection” was removed
- [functional regression] Resource “3.13.7 — System & Communications Protection” was removed
- [functional regression] Resource “3.7.1 — Maintenance” was removed
- [functional regression] Resource “3.4.3 — Configuration Management” was removed
- [functional regression] Resource “3.14.6 — System & Information Integrity” was removed
- [functional regression] Resource “3.13.4 — System & Communications Protection” was removed
- [functional regression] Resource “3.11.3 — Risk Assessment” was removed
- [functional regression] Resource “3.1.14 — Access Control” was removed
- [functional regression] Resource “3.3.2 — Audit & Accountability” was removed
- [functional regression] Resource “3.1.2 — Access Control” was removed
- [functional regression] Resource “3.1.11 — Access Control” was removed
- [functional regression] Resource “3.5.11 — Identification & Authentication” was removed
- [functional regression] Resource “3.14.2 — System & Information Integrity” was removed
- [functional regression] Resource “3.8.8 — Media Protection” was removed
- [functional regression] Resource “3.8.5 — Media Protection” was removed
- [functional regression] Resource “3.13.3 — System & Communications Protection” was removed
- [functional regression] Resource “3.7.6 — Maintenance” was removed
- [functional regression] Resource “3.7.4 — Maintenance” was removed
- [functional regression] Resource “3.1.7 — Access Control” was removed
- [functional regression] Resource “3.13.15 — System & Communications Protection” was removed
- [functional regression] Resource “3.1.10 — Access Control” was removed
- [functional regression] Resource “3.3.8 — Audit & Accountability” was removed
- [functional regression] Resource “3.2.2 — Awareness & Training” was removed
- [functional regression] Resource “3.3.7 — Audit & Accountability” was removed
- [functional regression] Resource “3.13.10 — System & Communications Protection” was removed
- [functional regression] Resource “3.8.9 — Media Protection” was removed
- [functional regression] Resource “3.4.5 — Configuration Management” was removed
- [functional regression] Resource “3.13.1 — System & Communications Protection” was removed
- [functional regression] Resource “3.5.7 — Identification & Authentication” was removed
- [functional regression] Resource “3.5.4 — Identification & Authentication” was removed
- [functional regression] Resource “3.14.5 — System & Information Integrity” was removed
- [functional regression] Resource “3.1.16 — Access Control” was removed
- [functional regression] Resource “3.1.21 — Access Control” was removed
- [functional regression] Resource “3.8.7 — Media Protection” was removed
- [functional regression] Resource “3.9.2 — Personnel Security” was removed
- [functional regression] Resource “3.1.18 — Access Control” was removed
- [functional regression] Resource “3.3.1 — Audit & Accountability” was removed
- [functional regression] Resource “3.5.10 — Identification & Authentication” was removed
- [functional regression] Resource “3.5.1 — Identification & Authentication” was removed
- [functional regression] Resource “3.5.8 — Identification & Authentication” was removed
- [functional regression] Resource “3.8.4 — Media Protection” was removed
- [functional regression] Resource “3.13.12 — System & Communications Protection” was removed
- [functional regression] Resource “3.2.1 — Awareness & Training” was removed
- [functional regression] Resource “3.12.1 — Security Assessment” was removed
- [functional regression] Resource “3.13.9 — System & Communications Protection” was removed
- [functional regression] Resource “3.1.9 — Access Control” was removed
- [functional regression] Resource “3.1.20 — Access Control” was removed
- [functional regression] Resource “3.1.5 — Access Control” was removed
- [functional regression] Resource “3.1.15 — Access Control” was removed
- [functional regression] Resource “3.3.9 — Audit & Accountability” was removed
- [functional regression] Resource “3.3.4 — Audit & Accountability” was removed
- [functional regression] Resource “3.5.6 — Identification & Authentication” was removed
- [functional regression] Resource “3.14.4 — System & Information Integrity” was removed
- [functional regression] Resource “3.10.4 — Physical Protection” was removed
- [functional regression] Resource “3.8.6 — Media Protection” was removed
- [functional regression] Resource “3.1.6 — Access Control” was removed
- [functional regression] Resource “3.2.3 — Awareness & Training” was removed
- [functional regression] Resource “3.14.7 — System & Information Integrity” was removed
- [functional regression] Resource “3.13.16 — System & Communications Protection” was removed
- [functional regression] Resource “3.5.3 — Identification & Authentication” was removed
- [functional regression] Resource “3.1.19 — Access Control” was removed
- [functional regression] Resource “3.3.6 — Audit & Accountability” was removed
- [functional regression] Resource “3.7.2 — Maintenance” was removed
- [functional regression] Resource “3.13.2 — System & Communications Protection” was removed
- [functional regression] Resource “3.11.1 — Risk Assessment” was removed
- [functional regression] Resource “3.13.14 — System & Communications Protection” was removed
- [functional regression] Resource “3.8.3 — Media Protection” was removed
- [functional regression] Resource “3.13.13 — System & Communications Protection” was removed
- [functional regression] Resource “3.9.1 — Personnel Security” was removed
- [functional regression] Resource “3.1.1 — Access Control” was removed
- [functional regression] Resource “3.5.9 — Identification & Authentication” was removed
- [functional regression] Resource “3.4.2 — Configuration Management” was removed
- [functional regression] Resource “3.14.3 — System & Information Integrity” was removed
- [functional regression] Resource “3.1.12 — Access Control” was removed
- [functional regression] Resource “3.5.2 — Identification & Authentication” was removed
- [functional regression] Resource “3.8.2 — Media Protection” was removed
- [functional regression] Resource “3.4.6 — Configuration Management” was removed
- [functional regression] Resource “3.12.2 — Security Assessment” was removed
- [functional regression] Resource “3.4.8 — Configuration Management” was removed
- [functional regression] Resource “3.4.1 — Configuration Management” was removed
- [functional regression] Resource “3.4.7 — Configuration Management” was removed
- [functional regression] Resource “3.10.5 — Physical Protection” was removed
- [functional regression] Resource “3.1.17 — Access Control” was removed
- [functional regression] Resource “3.6.2 — Incident Response” was removed
- [functional] Too many changes on this day to record them all, so 40 were dropped
- [functional] First check of Tool coverage: 8
- [functional] New resource “3.13.12 - System & Communications Protection”
- [functional] New resource “3.1.15 - Access Control”
- [functional] New resource “3.13.5 - System & Communications Protection”
- [functional] New resource “3.1.13 - Access Control”
- [functional] New resource “3.6.1 - Incident Response”
- [functional] New resource “3.1.9 - Access Control”
- [functional] New resource “3.13.3 - System & Communications Protection”
- [functional] New resource “3.10.2 - Physical Protection”
- [functional] New resource “3.13.16 - System & Communications Protection”
- [functional] New resource “3.8.1 - Media Protection”
- [functional] New resource “3.12.4 - Security Assessment”
- [functional] New resource “3.13.7 - System & Communications Protection”
- [functional] New resource “3.14.3 - System & Information Integrity”
- [functional] New resource “3.13.2 - System & Communications Protection”
- [functional] New resource “3.2.1 - Awareness & Training”
- [functional] New resource “3.5.7 - Identification & Authentication”
- [functional] New resource “3.5.6 - Identification & Authentication”
- [functional] New resource “3.2.3 - Awareness & Training”
- [functional] New resource “3.4.3 - Configuration Management”
- [functional] New resource “3.13.13 - System & Communications Protection”
- [functional] New resource “3.5.10 - Identification & Authentication”
- [functional] New resource “3.8.7 - Media Protection”
- [functional] New resource “3.3.8 - Audit & Accountability”
- [functional] New resource “3.3.6 - Audit & Accountability”
- [functional] New resource “3.5.8 - Identification & Authentication”
- [functional] New resource “3.14.6 - System & Information Integrity”
- [functional] New resource “3.1.20 - Access Control”
- [functional] New resource “3.13.6 - System & Communications Protection”
- [functional] New resource “3.12.1 - Security Assessment”
- [functional] New resource “3.7.3 - Maintenance”
- [functional] New resource “3.10.6 - Physical Protection”
- [functional] New resource “3.10.3 - Physical Protection”
- [functional] New resource “3.5.1 - Identification & Authentication”
- [functional] New resource “3.5.9 - Identification & Authentication”
- [functional] New resource “3.1.17 - Access Control”
- [functional] New resource “3.6.2 - Incident Response”
- [functional] New resource “3.8.2 - Media Protection”
- [functional] New resource “3.1.4 - Access Control”
- [functional] New resource “3.4.6 - Configuration Management”
- [functional] New resource “3.1.18 - Access Control”
- [functional] New resource “3.14.5 - System & Information Integrity”
- [functional] New resource “3.5.5 - Identification & Authentication”
- [functional] New resource “3.4.5 - Configuration Management”
- [functional] New resource “3.1.3 - Access Control”
- [functional] New resource “3.5.3 - Identification & Authentication”
- [functional] New resource “3.14.1 - System & Information Integrity”
- [functional] New resource “3.1.6 - Access Control”
- [functional] New resource “3.1.2 - Access Control”
- [functional] New resource “3.1.22 - Access Control”
- [functional] New resource “3.3.3 - Audit & Accountability”
- [functional] New resource “3.1.12 - Access Control”
- [functional] New resource “3.7.2 - Maintenance”
- [functional] New resource “3.9.1 - Personnel Security”
- [functional] New resource “3.8.6 - Media Protection”
- [functional] New resource “3.1.7 - Access Control”
- [functional] New resource “3.12.3 - Security Assessment”
- [functional] New resource “3.10.1 - Physical Protection”
- [functional] New resource “3.8.5 - Media Protection”
- [functional] New resource “3.7.6 - Maintenance”
- [functional] New resource “3.1.21 - Access Control”
- [functional] New resource “3.1.8 - Access Control”
- [functional] New resource “3.12.2 - Security Assessment”
- [functional] New resource “3.8.3 - Media Protection”
- [functional] New resource “3.4.1 - Configuration Management”
- [functional] New resource “3.8.8 - Media Protection”
- [functional] New resource “3.1.5 - Access Control”
- [functional] New resource “3.1.1 - Access Control”
- [functional] New resource “3.3.1 - Audit & Accountability”
- [functional] New resource “3.5.11 - Identification & Authentication”
- [functional] New resource “3.13.8 - System & Communications Protection”
- [functional] New resource “3.3.2 - Audit & Accountability”
- [functional] New resource “3.10.4 - Physical Protection”
- [functional] New resource “3.13.11 - System & Communications Protection”
- [functional] New resource “3.14.1 — System & Information Integrity”
- [functional] New resource “3.6.2 — Incident Response”
- [functional] New resource “3.13.6 — System & Communications Protection”
- [functional] New tool “crosswalk_revisions”
- [functional] New tool “scope_assessment”
- [functional] New tool “check_contract_type_eligibility”
- [functional] New tool “lookup_clause”
- [functional] New tool “lookup_rev3_requirement”

### 2026-08-08 (score 64)

First indexed and scored.

## MCP tools (13)

### `lookup_control` (~235 tokens)

Look up a NIST 800-171 control

Get one NIST SP 800-171 Rev 2 security requirement by number (e.g. "3.5.3"): the full requirement text, its control family, and its exact DoD Assessment Methodology (SPRS) point weight, including the sliding-scale rules for 3.5.3 (MFA) and 3.13.11 (FIPS cryptography). Call this when the user asks what a specific 800-171 or CMMC Level 2 control requires or how many SPRS points it is worth. Pass sections to get the 800-171A assessment objectives and the framework crosswalk in the same call instead of three.

Input parameters:

- `control` (string, required): Control number, e.g. "3.1.1" or "3.13.11"
- `sections` (array): Extra views to include: "objectives" for the 800-171A assessment objectives (how an assessor tests it), "crosswalk" for the 800-53 / CSF 2.0 / SOC 2 mappings. Omit for the requirement and its weight…

### `list_controls` (~183 tokens)

List NIST 800-171 controls

List NIST SP 800-171 Rev 2 requirements with their DoD Assessment Methodology (SPRS) weights, optionally filtered by control family name or by point weight (5, 3, or 1). Call this to enumerate the 110 CMMC Level 2 controls, to find all 5-point (highest-impact) requirements, or to see everything in one family such as Access Control. Returns identifiers and weights only - use lookup_control for one requirement's full text, or pass verbose to include every requirement's text at roughly twenty times the size.

Input parameters:

- `family` (string): Filter by control family
- `verbose` (boolean): Include the full requirement text for every result. Off by default: an unfiltered verbose listing is ~25× larger and is rarely what the question needs.
- `weight`: Filter by DoD assessment point weight

### `calculate_sprs_score` (~263 tokens)

Calculate an SPRS score

Compute an exact SPRS score per the DoD Assessment Methodology: start at 110 and subtract each unimplemented requirement's Annex A weight (floor −203). Pass the control numbers that are NOT implemented; optionally pass 3.5.3 and/or 3.13.11 as partially implemented for their sliding-scale values (MFA for privileged/remote only = −3; encryption present but not FIPS-validated = −3). Also reports whether the score clears the 88-point conditional CMMC Level 2 certification threshold and flags a missing SSP (3.12.4), which blocks SPRS submission entirely.

Input parameters:

- `not_implemented` (array, required): Rev 2 control numbers not implemented, e.g. ["3.5.3", "3.11.2"]. An empty array means all 110 implemented (score 110). Rev 3 identifiers are rejected - there is no DoD scoring methodology for Rev 3.
- `partially_implemented` (array): Sliding-scale controls at their partial value: 3.5.3 (MFA for privileged and remote users only) and/or 3.13.11 (encryption employed but not FIPS-validated). Deducts 3 instead of 5.

Output parameters:

- `conditional_note` (string)
- `deductions` (array)
- `meets_conditional_level_2_threshold` (boolean): Whether the score reaches 88. Clearing it is necessary but not sufficient - every open item must also be POA&M-eligible.
- `missing_ssp` (string): Present when 3.12.4 is unimplemented, in which case no score can be submitted to SPRS at all.
- `scale` (string)
- `sprs_score` (number): The computed score, from 110 down to the -203 floor.
- `total_points_deducted` (number)
- `unknown_controls` (array): Inputs that matched no requirement - treat as caller error, not as implemented.

### `get_assessment_objectives` (~127 tokens)

Get 800-171A assessment objectives for a control

Get the official NIST SP 800-171A assessment objectives for one NIST SP 800-171 Rev 2 requirement - the exact "Determine if..." objectives a CMMC Level 2 assessor scores, plus the potential assessment methods (what an assessor examines, who they interview, what they test). Call this when the user asks how a control is assessed, what evidence an assessor will look for, or how to prepare a specific control for a C3PAO assessment.

Input parameters:

- `control` (string, required): Control number, e.g. "3.5.3"

### `crosswalk_control` (~200 tokens)

Crosswalk a control across frameworks

Map a security control across frameworks: NIST SP 800-171 Rev 2 ↔ NIST SP 800-53 (FedRAMP Moderate) ↔ NIST CSF 2.0 ↔ SOC 2 Trust Services Criteria. Accepts an 800-171 number ("3.5.3"), an 800-53 id ("AC-2"), a CSF category ("PR.AA" style / "GV.RM"), or a SOC 2 criterion ("CC6"). Call this when the user asks what a control corresponds to in another framework, or how existing FedRAMP/SOC 2/CSF work maps onto CMMC. These are practitioner mappings, not the NIST-published authoritative crosswalk.

Input parameters:

- `control` (string, required): A control id from any supported framework, e.g. "3.1.1", "AC-2", "GV.RM", or "CC6"

### `determine_cmmc_level` (~208 tokens)

Determine required CMMC level

Determine which CMMC level (1, 2, or 3) applies to a defense contractor based on the data they handle and the clauses in their contracts, and - separately - which assessment type may actually be designated today. Those are not the same question: CMMC Phase II was suspended on 13 July 2026, so C3PAO and DIBCAC assessments cannot currently be designated even where the level calls for one. Call this when the user asks "what CMMC level do I need", whether FCI-only work needs CMMC, or what DFARS 252.204-7012/7019/7020/7021 imply.

Input parameters:

- `contract_clauses` (array): FAR/DFARS clauses present in their contracts, if known
- `handles_cui` (string, required): Does the organization store, process, or transmit Controlled Unclassified Information (CUI) - e.g. technical data, drawings, specs above general descriptive material?

### `list_level1_practices` (~66 tokens)

List the 17 CMMC Level 1 practices

List all 17 CMMC Level 1 basic safeguarding practices with their FAR 52.204-21 clause citations - the complete requirement set for contractors handling Federal Contract Information (FCI) only. Call this when the user asks what CMMC Level 1 requires.

### `generate_poam_entries` (~123 tokens)

Generate POA&M entries for control gaps

Turn a list of unimplemented NIST SP 800-171 controls into structured Plan of Action & Milestones (POA&M) entries - deficiency description, planned remediation, priority derived from the SPRS weight, and target dates per DoD-aligned governance (90 days for high-priority items, 180 for standard). Also returns the governance rules a POA&M must satisfy to survive a CMMC assessment. Call this when the user has assessment gaps and needs a remediation plan artifact.

Input parameters:

- `gaps` (array, required): The unimplemented or partially implemented controls

### `check_contract_type_eligibility` (~182 tokens)

Can you accept this contract type?

Determine whether a contractor can legally be awarded a given contract type, based on the business systems that type requires. A cost-reimbursement contract may be awarded only if the accounting system is adequate for determining costs (FAR 16.301-3), and T&M billing cannot be substantiated without compliant timekeeping - so this is an eligibility gate, not a preference. Call this before a bid/no-bid, when a solicitation names a contract type, or when someone asks what a pre-award survey will examine. Also returns the SF1408 criteria and the six DFARS business systems whose deficiencies trigger payment withholding after award.

Input parameters:

- `contract_type` (string): The contract type named in the solicitation. Omit to compare all types.
- `include_sf1408` (boolean): Include the SF1408 pre-award accounting system survey criteria.

### `lookup_clause` (~240 tokens)

Look up a FAR/DFARS cybersecurity clause

Explain what a FAR or DFARS cybersecurity clause obliges a contractor to do: what triggers it, the concrete duties, the reporting deadlines, what it flows down to subcontractors, and which other clauses come with it. Covers 52.204-21, 252.204-7008, 252.204-7012, 252.204-7019, 252.204-7020, 252.204-7021, 252.239-7010. Call this when someone asks "my contract has 7012 in it, what do I have to do", which clauses require CMMC, what flows down to a subcontractor, or how long they have to report an incident. Does NOT reproduce clause text verbatim - the text is law, it gets amended, and quoting a stale copy into a contract dispute is worse than a citation; each answer links the authoritative text at acquisition.gov.

Input parameters:

- `clause` (string): Clause number - "7012", "252.204-7012", or "DFARS 252.204-7012" all work. Omit to list every clause covered.

### `scope_assessment` (~191 tokens)

Determine CMMC assessment scope

Work out which assets fall inside a CMMC assessment boundary, and what each category obliges. Returns the DoD asset categories (CUI Asset, Security Protection Asset, Contractor Risk Managed Asset, Specialized Asset, Out-of-Scope) with how each is treated at assessment, plus the CUI categories that most often pull a defense contractor into scope unexpectedly. Call this when someone asks what is in scope, how to reduce assessment cost, whether an enclave helps, or whether a specific system counts. Scope decides the size and cost of the whole engagement, so getting it wrong is expensive in both directions.

Input parameters:

- `include_cui_categories` (boolean): Include the common CUI categories and the traps that hide them. Useful when the contractor is unsure whether they hold CUI at all.
- `level` (required): CMMC level being scoped. Level 1 has no asset taxonomy - everything touching FCI is in scope.

### `lookup_rev3_requirement` (~263 tokens)

Look up a NIST 800-171 Rev 3 requirement (advisory)

Get one NIST SP 800-171 REVISION 3 requirement by its zero-padded number (e.g. "03.01.01"): the requirement statement, its organization-defined parameters, the 800-171A Rev 3 assessment objectives, and whether it was withdrawn. Rev 3 has 97 active requirements of 130 numbered across 17 families, with 88 ODPs and 422 objectives. IMPORTANT: Rev 3 is NOT currently binding for DoD contracts - DFARS 252.204-7012 is pinned to Rev 2 by class deviation, and SPRS scores Rev 2 only. Use lookup_control for anything contractual; use this when the user is planning ahead, doing civilian-agency CUI work, or has explicitly asked about Rev 3. Identifiers differ between revisions and collide: Rev 2's 3.1.1 is not Rev 3's 03.01.01.

Input parameters:

- `requirement` (string, required): Rev 3 requirement number, e.g. "03.01.01" or "3.1.1" (zero-padded automatically). This is a Rev 3 identifier - it is NOT the same requirement as the Rev 2 control with the similar number.

### `crosswalk_revisions` (~161 tokens)

Compare 800-171 Rev 2 and Rev 3

Explain how NIST SP 800-171 Rev 2 and Rev 3 differ, and what happened to a specific requirement between them. Call this when someone is implementing Rev 3 early, holds a Rev 3 citation and needs the Rev 2 obligation, or asks which revision applies to them. Answers the question DoD guidance forces on early adopters: assessments still run against Rev 2, so Rev 2 gaps must be closed regardless of what has been built to Rev 3.

Input parameters:

- `requirement` (string): Optional: a specific requirement in either scheme, e.g. "3.5.3" (Rev 2) or "03.05.03" (Rev 3). Omit for the structural summary alone.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mactechsolutionsllc-www-cmmc/api-mcp#diagnostics

## Score history

- 2026-08-13: 77
- 2026-08-12: 77
- 2026-08-11: 76
- 2026-08-10: 75
- 2026-08-09: 74
- 2026-08-08: 64

## Links

- Remote endpoint: https://www.mactechsolutionsllc.com/api/mcp
- Website: https://www.mactechsolutionsllc.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-mactechsolutionsllc-www-cmmc/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mactechsolutionsllc-www-cmmc/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-mactechsolutionsllc-www-cmmc/api-mcp