Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MacTech STIG

REMOTE · WWW.MACTECHSOLUTIONSLLC.COM · SCANNED SEP 21

2,029 DISA STIG rules with official check/fix text, CCI mappings, and .ckl checklist export.

0 this week 89 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 87702 tokens (~43/item across 2004 items; 4 tools + 2000 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
  • Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the MacTech STIG MCP server?

MacTech STIG is a hosted endpoint at https://www.mactechsolutionsllc.com/api/mcp/stig, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.mactechsolutionsllc.com

# add to Claude Code
claude mcp add --transport http com-mactechsolutionsllc-www-stig 'https://www.mactechsolutionsllc.com/api/mcp/stig'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mactechsolutionsllc-www-stig": {
      "url": "https://www.mactechsolutionsllc.com/api/mcp/stig"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mactechsolutionsllc-www-stig": {
      "type": "http",
      "url": "https://www.mactechsolutionsllc.com/api/mcp/stig"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-mactechsolutionsllc-www-stig]
url = "https://www.mactechsolutionsllc.com/api/mcp/stig"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mactechsolutionsllc-www-stig": {
      "type": "remote",
      "url": "https://www.mactechsolutionsllc.com/api/mcp/stig",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mactechsolutionsllc-www-stig --url 'https://www.mactechsolutionsllc.com/api/mcp/stig' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-mactechsolutionsllc-www-stig:
    url: "https://www.mactechsolutionsllc.com/api/mcp/stig"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mactechsolutionsllc-www-stig": {
      "Transport": "http",
      "Url": "https://www.mactechsolutionsllc.com/api/mcp/stig"
    }
  }
}
# add to Vellum
assistant mcp add com-mactechsolutionsllc-www-stig -t streamable-http -u 'https://www.mactechsolutionsllc.com/api/mcp/stig'
// mcp.json
{
  "mcpServers": {
    "com-mactechsolutionsllc-www-stig": {
      "type": "http",
      "url": "https://www.mactechsolutionsllc.com/api/mcp/stig"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Sept 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://www.mactechsolutionsllc.com/api/mcp/stig

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.mactechsolutionsllc.com CN=YE1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 6bc046177a97feeca89321e7b01e9e1b0ab
SANs: www.mactechsolutionsllc.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.mactechsolutionsllc.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mactechsolutionsllc.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://stats.mactechsolutionsllc.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https://vault.mactechsolutionsllc.com https://stats.mactechsolutionsllc.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-ancestors 'none';
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.mactechsolutionsllc.com/api/mcp/stig Verified 200
http (plaintext) http://www.mactechsolutionsllc.com/api/mcp/stig HTTPS enforced 301 https://www.mactechsolutionsllc.com/api/mcp/stig
MCP tools · 4 exposed · ~684 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
export_stig_checklist ~211

No description provided.

NameTypeReqDescription
findingsarray
host_fqdnstring
host_ipstring
host_namestring
productstringyes
severitystring
NameTypeReqDescription
benchmarkstringyes
cklstringyes
filenamestringyes
notestringyes
rule_countnumberyes
status_countsobjectyes

No examples provided.

get_stig_rule ~108

No description provided.

NameTypeReqDescription
sv_idstringyes
NameTypeReqDescription
automation_levelstringyes
automation_sourcestringyes
benchmarkstringyes
categorystringyes
check_textstringyes
descriptionstringyes
fix_textstringyes
nist_idstringyes
productstringyes
severitystringyes
severity_categorystringyes
sv_idstringyes
titlestringyes

No examples provided.

list_stig_benchmarks ~45

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_stig ~320

No description provided.

NameTypeReqDescription
automationstring
formatstring
limitinteger
offsetinteger
productstring
querystringyes
severitystring

No output schema declared.

No examples provided.

Common questions

What is the MacTech STIG MCP server?

MacTech STIG is an MCP server listed in the public MCP registry as com.mactechsolutionsllc.www/stig. 2,029 DISA STIG rules with official check/fix text, CCI mappings, and .ckl checklist export. This page covers its hosted endpoint (https://www.mactechsolutionsllc.com/api/mcp/stig).

Is the MacTech STIG MCP server safe to use?

MacTech STIG scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Does the MacTech STIG MCP server require authentication?

No. We connected to MacTech STIG without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MacTech STIG MCP server still maintained?

MacTech STIG is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.