2,029 DISA STIG rules with official check/fix text, CCI mappings, and .ckl checklist export.
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/mcp/stig4 tools · 408mssearch_stigSearch DISA STIG hardening rules across RHEL 8, RHEL 9, Windows 11, Windows Server 2022, and Cisco IOS Router NDM benchmarks - by keyword (matched against rule IDs and titles first, then descriptions), filterable by product, severity (high/medium/low, mapping to CAT I/II/III), category, and automat…Search DISA STIG hardening rules across RHEL 8, RHEL 9, Windows 11, Windows Server 2022, and Cisco IOS Router NDM benchmarks - by keyword (matched against rule IDs and titles first, then descriptions), filterable by product, severity (high/medium/low, mapping to CAT I/II/III), category, and automat…
| Parameter | Type | Description |
|---|---|---|
| query* | string | Keyword or rule id fragment, e.g. "ssh banner" or "SV-257777" |
| product | string | Limit to one benchmark |
| severity | string | high=CAT I, medium=CAT II, low=CAT III |
| automation | string | — |
| limit | integer | Max results per page (default 20) |
| offset | integer | Skip this many matches. Pass the next_offset from a previous response to reach results beyond the first page. |
| format | string | "summary" (default) returns each rule inline as JSON. "links" returns MCP resource links, which hosts can render as pickable items the user opens on demand. No… |
get_stig_ruleGet the complete detail for one DISA STIG rule by its SV id (from search_stig): the requirement discussion, the exact check procedure an assessor runs, the fix text, severity, NIST control mapping, and whether it is SCAP-automatable. Call this when the user needs to implement or verify a specific r…Get the complete detail for one DISA STIG rule by its SV id (from search_stig): the requirement discussion, the exact check procedure an assessor runs, the fix text, severity, NIST control mapping, and whether it is SCAP-automatable. Call this when the user needs to implement or verify a specific r…
| Parameter | Type | Description |
|---|---|---|
| sv_id* | string | Rule id, e.g. "SV-257777r991589_rule" (fragments matched if unique) |
list_stig_benchmarksList the DISA STIG benchmarks this server covers, with versions, rule counts, and severity breakdowns. Call this first when unsure whether a platform is covered.List the DISA STIG benchmarks this server covers, with versions, rule counts, and severity breakdowns. Call this first when unsure whether a platform is covered.
No input schema was published for this tool.
export_stig_checklistGenerate a DISA STIG Viewer checklist (.ckl XML) for a benchmark, optionally filtered by severity and pre-populated with findings. This is the artifact an assessment actually hands over - STIG Viewer opens it, eMASS ingests it, and a POA&M is written from it. Rules you do not supply a status for co…Generate a DISA STIG Viewer checklist (.ckl XML) for a benchmark, optionally filtered by severity and pre-populated with findings. This is the artifact an assessment actually hands over - STIG Viewer opens it, eMASS ingests it, and a POA&M is written from it. Rules you do not supply a status for co…
| Parameter | Type | Description |
|---|---|---|
| product* | string | Which benchmark to build the checklist from |
| severity | string | Limit to one severity, e.g. high for a CAT I-only checklist |
| host_name | string | Asset hostname recorded in the checklist |
| host_ip | string | — |
| host_fqdn | string | — |
| findings | array | Per-rule results. Anything omitted stays Not_Reviewed - an unreviewed rule must never be reported as passing. |
4 of 4 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.
2,029 DISA STIG rules with official check/fix text, CCI mappings, and .ckl checklist export.
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.