Screenata Compliance MCP

Gérez la conformité SOC 2, HIPAA, ISO 27001 et ISO 42001 : évaluez le niveau de préparation, les politiques, les tests, les risques et les preuves, enquêtez sur les échecs et préparez-vous aux audits. MCP hébergé avec autorisation de l’espace de travail via OAuth.

Serveur MCP hébergé

npx add-mcp 'https://api.screenata.com/mcp'

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

Screenata MCP and compliance skill

Connect your AI assistant to your Screenata compliance workspace through the Model Context Protocol (MCP).

Review compliance status, investigate failing tests, read policies, collect evidence, and prepare for an audit from an MCP client. Screenata supports SOC 2, HIPAA, ISO 27001, and ISO 42001; available data depends on the frameworks enabled in your workspace.

Hosted server

SettingValue
MCP endpointhttps://api.screenata.com/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.1, Authorization Code with PKCE
Account requiredScreenata account with access to a workspace
Local server installationNone

This repository contains the public connection guide, an installable compliance skill, and LobeHub marketplace metadata for Screenata's hosted MCP service. The server runs on Screenata's infrastructure. This repository does not contain a self-hostable server or Screenata's application backend.

Connect

Use an MCP client that supports remote Streamable HTTP servers and OAuth discovery.

  1. Open your client's MCP server or connector settings.
  2. Add a remote server named Screenata.
  3. Enter https://api.screenata.com/mcp as the server URL and select Streamable HTTP if asked.
  4. Follow the browser sign-in and consent flow. Select your Screenata workspace and review the requested permissions.
  5. Ask the assistant to call screenata_whoami and confirm the workspace before making changes.

Client settings differ. A client that supports only local stdio processes or cannot complete OAuth will not connect directly to this hosted service. No local npm package, database, cloud-provider credentials, or Screenata backend checkout is needed.

LobeHub

Add the endpoint above as a remote MCP server and complete Screenata's OAuth flow. This repository includes lhm.plugin.json for marketplace publication; its presence does not mean the marketplace listing has already been published or validated.

Install the compliance skill

The screenata-compliance skill teaches your agent how to work with SOC 2, HIPAA, ISO 27001, and ISO 42001 programs using Screenata's hosted tools. It covers readiness reviews, failing tests, approved fixes, evidence collection, policy drafting, and audit preparation.

Requires Node.js 22.20 or later for the skills CLI. From your project directory:

npx skills add Screenata/screenata-mcp --skill screenata-compliance

Select your coding agent when prompted. To install specifically for Claude Code or Codex:

npx skills add Screenata/screenata-mcp --skill screenata-compliance -a claude-code
npx skills add Screenata/screenata-mcp --skill screenata-compliance -a codex

Installing the skill adds instructions. It does not connect your account or configure an MCP server. Complete the connection steps separately, then ask your agent to use screenata-compliance for the task. A Screenata account and authorized workspace connection are required for live data and actions.

Read the skill instructions before installing. They contain workflow guidance only; no application backend or embedded credentials are included.

Things to ask

  • "Which Screenata workspace am I connected to?"
  • "How is our SOC 2 compliance program doing?"
  • "Show failing tests and explain what needs fixing."
  • "Read our access control policy."
  • "What evidence is missing for the active audit cycle?"
  • "What should we work on next?"
  • "Prepare a remediation plan for this failing test. Show me the changes before applying anything."

Tools

The authenticated server's tools/list response is authoritative for current tool names, parameters, and annotations. The table below describes the public interface; availability and successful execution depend on your permissions and workspace configuration.

ToolPurpose
screenata_whoamiIdentify the connected user, organization, workspace, and credential permissions.
screenata_statusReview program readiness and framework coverage.
screenata_testsList tests, filter their status, and find tests an agent can act on.
screenata_controlsList framework controls and, for a selected audit cycle, review conclusions.
screenata_test_detailRead a test's latest results, findings, instructions, and remediation guidance.
screenata_test_runStart a native check for a test.
screenata_test_run_statusRetrieve a test run's progress and result.
screenata_test_remedy_preparePrepare a remediation plan without applying it.
screenata_test_remedy_executeApply an explicitly approved remediation plan.
screenata_test_remedy_undoRoll back the most recent applied remediation for a test.
screenata_gapsFind missing or stale evidence and policy-to-test coverage gaps.
screenata_risksRead and filter the risk register.
screenata_policiesList policies and their approval status.
screenata_policy_detailRead a policy's content and linked claims.
screenata_policy_questionsRetrieve the questions needed to draft a policy.
screenata_policy_answerRecord an answer the user explicitly supplied.
screenata_policy_draftQueue a policy draft from recorded answers for review in Screenata.
screenata_assessReview automated infrastructure check results and provider connection progress.
screenata_assess_stateRecord the user's choice to skip or reconsider a provider.
screenata_next_actionsGet prioritized next actions for an audit cycle.
screenata_audit_checkCheck audit blockers and warnings.
screenata_submit_evidenceSubmit redacted text evidence for a test, with optional dry-run preview.
screenata_scanTrigger a scan for a connected provider, with optional dry-run preview.
screenata_assign_taskAssign a test to a team member, with optional dry-run preview.
search_workspace_docsSearch the connected workspace's compliance documentation.
get_document_by_titleRetrieve a compliance document by full or partial title.

Binary evidence uploads such as screenshots and PDFs use Screenata's other interfaces, not the text evidence MCP tool.

Permissions and data handling

OAuth consent binds access to a Screenata workspace. Tools enforce their required scopes. Read capabilities include compliance, controls, policies, and risks; additional permissions cover test execution, remediation, policy changes, scans, evidence submission, assignments, and audit checks.

  • Review the workspace and granted scopes before using the connection.
  • Write tools can change workspace records or connected infrastructure. Review plans and obtain explicit user approval before applying remediation, replacing policy content, or rolling back changes.
  • Policy answers must come from the user. An assistant must not invent attestations.
  • Keep cloud-provider secrets out of prompts and tool arguments. Configure integrations through Screenata.
  • Submit redacted technical evidence. Do not send patient records, payment card data, government identifiers, or authentication secrets through these tools.
  • Information returned by Screenata is sent to your MCP client and may be processed by its AI provider. Choose a client and provider appropriate for your organization's data requirements.

Troubleshooting

SymptomWhat to check
HTTP 401 before sign-inExpected for unauthenticated requests. Complete OAuth through your MCP client.
Permission denied for a toolReconnect and approve the required scope, and confirm your workspace access.
Browser GET returns HTTP 405The endpoint accepts MCP POST requests. A browser address-bar visit is not a connection test.
Client cannot connectConfirm support for Streamable HTTP and OAuth discovery, then check the endpoint URL.
No results or wrong workspaceCall screenata_whoami, confirm the workspace, and check connected integrations and enabled frameworks.
HTTP 429Respect Retry-After and retry after the rate-limit window.

OAuth discovery documents are available at:

Support

Visit Screenata for the product and the Screenata app to manage your workspace. Use GitHub issues for connection-guide or marketplace metadata problems. Do not post private evidence, workspace data, or credentials in public issues.

License

The files in this repository are licensed under the MIT License. That license applies to this repository's documentation and metadata; it does not license the hosted Screenata service or its private backend implementation.