Compliance

com.screenataPublished by screenata.comOfficial publisherv1.0.0Updated Oct 24, 2026

Manage compliance controls, policies, and audit readiness for SOC 2, HIPAA, ISO 27001 and more.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant manage compliance controls, policies and audit readiness for frameworks such as SOC 2, HIPAA and ISO 27001.

What you can do
Manage compliance controls for frameworks such as SOC 2, HIPAA and ISO 27001, as described by the provider. Work with policies and audit readiness through the assistant. No individual tools are listed in the available material, so the exact operations are not documented here.
When to use it
Useful when an organization runs a compliance program and wants an assistant to help track controls, policies and audit preparation for standards like SOC 2, HIPAA or ISO 27001.
Requirements
A remote endpoint at api.screenata.com reached over streamable HTTP. OAuth authentication is required, so a Screenata account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server handles compliance and audit material, which is sensitive internal data. It requires OAuth sign-in, so review which account and permissions you grant. The available material does not describe whether tools write, change or delete records; confirm this before relying on it for audit data.

Installation

In SourceWeft

  1. Open Compliance in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.screenata%2Fcompliance/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "compliance": {
      "type": "http",
      "url": "https://api.screenata.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

56% 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
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.