{
  "markdown": "# mcp-nist-standards\n\nNIST Standards MCP pack\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `nist_control` | Look up the full text of one NIST 800-53 security control or NIST 800-171 CUI security requirement by id — the control statement (requirement prose), discussion/guidance, and related controls. Use for \"what does NIST control AC-2 require\", \"NIST 800-53 AC-2 access control\", \"FedRAMP control SC-7 boundary protection\", \"NIST authenticator management IA-5\", \"NIST CUI control 800-171 3.1.1\". Forgiving id: accepts \"AC-2\", \"ac-2\", \"AC-02\", control enhancements \"AC-2(1)\" or \"AC-2.1\", and CUI ids \"3.1.1\" / \"3.01.01\". Source: SP 800-53 Rev 5 and SP 800-171 Rev 3 (official NIST OSCAL, public domain). Examples: {\"id\":\"AC-2\"}, {\"id\":\"SC-7\"}, {\"id\":\"IA-5\"}, {\"id\":\"AC-2(1)\"}, {\"id\":\"3.1.1\"}. |\n| `nist_control_search` | Keyword search across NIST 800-53 security/privacy controls and NIST 800-171 CUI requirements by title and requirement text. Use when the id is unknown — \"NIST security control for least privilege\", \"NIST control about session lock\", \"NIST 800-53 encryption at rest\", \"NIST cybersecurity control multi-factor authentication\", \"access control / identification and authentication / system and communications protection\". All query tokens must match (case-insensitive AND). Optional family filter (code like \"AC\", \"IA\", \"SC\" or a family name like \"access control\"). Returns matching {id, family, title, snippet}. Source: SP 800-53 Rev 5 + SP 800-171 Rev 3. Examples: {\"query\":\"least privilege\"}, {\"query\":\"multi-factor authentication\",\"family\":\"IA\"}, {\"query\":\"boundary protection\"}. |\n| `nist_control_family` | List every NIST control in a family — the FedRAMP/800-53 control-family baseline. Use for \"list all NIST access control controls\", \"NIST 800-53 AC family\", \"what controls are in identification and authentication\", \"NIST system and communications protection family\". Input a family code (\"AC\", \"IA\", \"SC\", \"AU\", \"SI\", …) or a family name (\"access control\"). Returns the family title plus every control id + title (including enhancements). Source: SP 800-53 Rev 5 (+ SP 800-171 Rev 3). Examples: {\"family\":\"AC\"}, {\"family\":\"identification and authentication\"}, {\"family\":\"SC\"}. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"nist-standards\": {\n      \"url\": \"https://gateway.pipeworx.io/nist-standards/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/nist-standards/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Nist Standards data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4388,
  "sha": "d03a418e58da7416f4ff7d34f0cc7eeac4110d694734c2429d9f32bf3b46c081",
  "repo_slug": "pipeworx-io/mcp-nist-standards",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_nist_standards_a3c2c94f/readme"
}