NIST 800-171 controls and 800-171A objectives, crosswalks, exact SPRS scoring, POA&M generation.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://www.mactechsolutionsllc.com/api/mcp13 tools · 424mslookup_controlGet 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 w…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 w…
| Parameter | Type | Description |
|---|---|---|
| control* | string | 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.… |
list_controlsList 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…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…
| Parameter | Type | Description |
|---|---|---|
| family | string | Filter by control family |
| weight | — | Filter by DoD assessment point weight |
| 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. |
calculate_sprs_scoreCompute 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 (MF…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 (MF…
| Parameter | Type | Description |
|---|---|---|
| not_implemented* | array | 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 i… |
| 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). De… |
get_assessment_objectivesGet 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 a…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 a…
| Parameter | Type | Description |
|---|---|---|
| control* | string | Control number, e.g. "3.5.3" |
crosswalk_controlMap 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…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…
| Parameter | Type | Description |
|---|---|---|
| control* | string | A control id from any supported framework, e.g. "3.1.1", "AC-2", "GV.RM", or "CC6" |
determine_cmmc_levelDetermine 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…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…
| Parameter | Type | Description |
|---|---|---|
| handles_cui* | string | Does the organization store, process, or transmit Controlled Unclassified Information (CUI) - e.g. technical data, drawings, specs above general descriptive ma… |
| contract_clauses | array | FAR/DFARS clauses present in their contracts, if known |
list_level1_practicesList 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.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.
No input schema was published for this tool.
generate_poam_entriesTurn a list of unimplemented NIST SP 800-171 controls into structured Plan of Action & Milestones (POA&M) entries, and - the part that decides whether the plan is usable - sort them by eligibility under 32 CFR 170.21. Most gaps CANNOT go on a CMMC Level 2 POA&M: the rule bars every requirement wort…Turn a list of unimplemented NIST SP 800-171 controls into structured Plan of Action & Milestones (POA&M) entries, and - the part that decides whether the plan is usable - sort them by eligibility under 32 CFR 170.21. Most gaps CANNOT go on a CMMC Level 2 POA&M: the rule bars every requirement wort…
| Parameter | Type | Description |
|---|---|---|
| gaps* | array | The unimplemented or partially implemented controls |
| conditionalStatusDate | string | Conditional CMMC Status Date (YYYY-MM-DD), if one exists. The 180-day closeout window runs from this date - NOT from the day the plan is written - so without i… |
check_contract_type_eligibilityDetermine 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…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…
| Parameter | Type | Description |
|---|---|---|
| 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_clauseExplain 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-…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-…
| Parameter | Type | Description |
|---|---|---|
| clause | string | Clause number - "7012", "252.204-7012", or "DFARS 252.204-7012" all work. Omit to list every clause covered. |
scope_assessmentWork 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…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…
| Parameter | Type | Description |
|---|---|---|
| level* | — | CMMC level being scoped. Level 1 has no asset taxonomy - everything touching FCI is in scope. |
| 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. |
lookup_rev3_requirementGet 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, wi…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, wi…
| Parameter | Type | Description |
|---|---|---|
| requirement* | string | 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 cont… |
crosswalk_revisionsExplain 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 o…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 o…
| Parameter | Type | Description |
|---|---|---|
| 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. |
13 of 13 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
NIST 800-171 controls and 800-171A objectives, crosswalks, exact SPRS scoring, POA&M generation.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.