MacTech CMMC / NIST 800-171 is answering right now. Last checked moments ago. It exposes 13 tools.
NIST 800-171 controls and 800-171A objectives, crosswalks, exact SPRS scoring, POA&M generation.
Uptime history
33 days of history · worst day 99%
33 days agonow
100.0%
Uptime 24h
93 of 93 checks
13
Tools
read from the server
378 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 25
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
9 Aug
9 tool descriptions were rewritten11 times that day
check_contract_type_eligibility, determine_cmmc_level, generate_poam_entries and 6 more
9 Aug
7 tools changed the parameters they ask for8 times that day
calculate_sprs_score, determine_cmmc_level, list_controls and 4 more
9 Aug
5 tools appeared
check_contract_type_eligibility, crosswalk_revisions, lookup_clause and 2 more
9 Aug
a tool changed version
and 3 more, back to 9 August 2026
Nothing serious here today
Today is the operative word: we check MacTech CMMC / NIST 800-171 every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.
run in your terminal
claude mcp add cmmc --transport http https://www.mactechsolutionsllc.com/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"cmmc": {
"url": "https://www.mactechsolutionsllc.com/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.cmmc]
url = "https://www.mactechsolutionsllc.com/api/mcp".cursor/mcp.json
{
"mcpServers": {
"cmmc": {
"url": "https://www.mactechsolutionsllc.com/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"cmmc": {
"url": "https://www.mactechsolutionsllc.com/api/mcp"
}
}
}Available tools 13
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
lookup
lookup_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.
lookup_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.
lookup_rev3_requirement
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.
crosswalk
crosswalk_control
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.
crosswalk_revisions
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.
assessment
get_assessment_objectives
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.
calculate
calculate_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.
contract
check_contract_type_eligibility
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.
controls
list_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.
determine
determine_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.
generate
generate_poam_entries
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.
level1
list_level1_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.
scope
scope_assessment
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://www.mactechsolutionsllc.com/api/mcp | streamable-http | answering | 374 ms | 0 min ago |
Alternatives to MacTech CMMC / NIST 800-171
same job, measured the same wayCosmic
by cosmicjs
Manage Cosmic CMS content, media, object types, and AI generation from any MCP client.
Universal Test Framework
by phoenice-labs
Polyglot MCP test generation with 8-section contract enforcement across Python, TS, Java, Go, C++.
Ads AI Creator MCP
by rocnubie
Ads AI Creator generates ad creatives, copy, and visuals using AI so marketers can iterate on
Generect MCP
by generect
B2B lead generation and company search through Generect Live API for sales prospecting.
Zod Contract Mock Forge MCP
by vola-trebla
MCP server for deterministic mock generation and API contract scaffolding using Zod schemas
AI Architect MCP Spec
by cdeust
PRD verification and host-driven generation with multi-judge consensus across 17 MCP tools.
Pentagonal MCP
by achilles1089
AI smart contract forge — 8-agent security audits, generation, and compilation across 8 chains
S
EventEdge Oracle
by arakelproof-edge
Prediction-market intelligence for conservative cross-market pricing edges and live signals.
MacTech CMMC / NIST 800-171 — questions
Answers built from our own checks of this server.
What can MacTech CMMC / NIST 800-171 do?
It exposes 13 tools, read directly from the server on our last check. Among them: calculate_sprs_score, check_contract_type_eligibility, crosswalk_control, crosswalk_revisions, determine_cmmc_level, generate_poam_entries and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is MacTech CMMC / NIST 800-171 mostly used for?
Its tools cluster around lookup and crosswalk. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is MacTech CMMC / NIST 800-171 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 93 of 93 checks got a reply (100.0%), average response time 378 ms. The bar chart above shows every period we have measured.
How do I connect MacTech CMMC / NIST 800-171?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MacTech CMMC / NIST 800-171 need an API key?
No. MacTech CMMC / NIST 800-171 completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MacTech CMMC / NIST 800-171?
It answers our handshake in 378 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.