Nizh

com.nizhPublished by nizh.comOfficial publisherv1.0.0Updated Oct 24, 2026

Compliance frameworks (SOC 2, ISO 27001, CMMC, NIST, more) delivered to AI agents as MCP tools.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that gives AI assistants tools for compliance frameworks such as SOC 2, ISO 27001, CMMC and NIST.

What you can do
Provides compliance framework content (SOC 2, ISO 27001, CMMC, NIST and others) to an assistant as MCP tools, so the assistant can work with framework material directly rather than from general knowledge. The registry lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs to reference or work with established security and compliance frameworks, for example while preparing for or discussing an audit.
Requirements
A remote MCP endpoint at mcp.nizh.com over streamable HTTP; no packages, environment variables or headers are declared. The manifest declares no authentication, so check whether the service requires an account or key.
Before you install
The manifest declares no authentication and no credentials, so verify with the provider what data is sent and how access is controlled. The specific tools and any write actions are not documented in the supplied material.

Installation

In SourceWeft

  1. Open Nizh in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.nizh%2Fnizh/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nizh": {
      "type": "http",
      "url": "https://mcp.nizh.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.