Local MCP capabilities provider for Expo
MacTech STIG is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
2,029 DISA STIG rules with official check/fix text, CCI mappings, and .ckl checklist export.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mactech-stig-mcp https://www.mactechsolutionsllc.com/api/mcp/stig
# 2 — ask your agent for something these tools do
# search_stig, get_stig_rule, list_stig_benchmarks and 1 more
MacTech STIG costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mactech-stig-mcp https://www.mactechsolutionsllc.com/api/mcp/stigReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 automation level. Call this when the user asks how to harden one of these platforms, what a STIG requires, o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keyword or rule id fragment, e.g. "ssh banner" or "SV-257777" |
| product | string | no | Limit to one benchmark |
| severity | string | no | high=CAT I, medium=CAT II, low=CAT III |
| automation | string | no | — |
| limit | integer | no | Max results per page (default 20) |
| offset | integer | no | Skip this many matches. Pass the next_offset from a previous response to reach results beyond the first page. |
| format | string | no | "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. Not smaller - the title and severity you ne |
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 rule.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sv_id | string | yes | Rule id, e.g. "SV-257777r991589_rule" (fragments matched if unique) |
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 parameter schema on file.
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 come out as Not_Reviewed. Call this when the user wants a checklist, a scan result recorded, or evidenc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | Which benchmark to build the checklist from |
| severity | string | no | Limit to one severity, e.g. high for a CAT I-only checklist |
| host_name | string | no | Asset hostname recorded in the checklist |
| host_ip | string | no | — |
| host_fqdn | string | no | — |
| findings | array | no | Per-rule results. Anything omitted stays Not_Reviewed - an unreviewed rule must never be reported as passing. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MacTech STIG or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish MacTech STIG can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.