Skip to content
External endpointresponds

MacTech CMMC / NIST 800-171

NIST 800-171 control lookup and exact SPRS scoring with official DoD assessment weights, for CMMC.

Endpoint URL
https://www.mactechsolutionsllc.com/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
149 ms
Response record
2 of 2 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.mactechsolutionsllc.www/cmmc

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
mactech-cmmc
Version
1.2.0
Capability keys
tools, completions, resources, prompts
Tool names
lookup_control, list_controls, calculate_sprs_score, get_assessment_objectives, crosswalk_control, determine_cmmc_level, list_level1_practices, generate_poam_entries, check_contract_type_eligibility, lookup_clause, scope_assessment, lookup_rev3_requirement, crosswalk_revisions
Instructions excerpt

MacTech Solutions CMMC / NIST SP 800-171 reference server. Provides the full 110-requirement catalog of NIST SP 800-171 Rev 2 with the official DoD Assessment Methodology (Annex A) point weights (deduction pool 313, score range -203 to 110), and computes exact SPRS scores. Also serves the official NIST SP 800-171A assessment objectives (320 objectives - how assessors test each control), framework crosswalks to NIST 800-53/FedRAMP Moderate, CSF 2.0, and SOC 2, CMMC level determination (FCI vs CUI), the 17 Level 1 practices, and structured POA&M generation for gaps. Use it for defense-contractor cybersecurity compliance questions: what a control requires, how it is assessed, how much it is worth, what a given implementation state scores, and how to plan remediation. AUTHORITY: this server answers for NIST SP 800-171 REVISION 2, deliberately. NIST withdrew Rev 2 on 14 May 2024 in favour of Rev 3, but DoD did not follow: class deviation 2024-O0013 R1 pins DFARS 252.204-7012 to Rev 2 until

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 181ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 149ms