Claw GRC

com.clawgrcPublished by clawgrc.comOfficial publisherv1.0.0Updated Oct 29, 2026

AI-native GRC: compliance scores, security findings, tickets and agent trust tiers.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote Claw GRC endpoint that lets an assistant work with governance, risk and compliance data: compliance scores, security findings, tickets and agent trust…

What you can do
  • Read compliance scores and security findings for the organization
  • Work with tickets related to governance, risk and compliance work
  • Look up agent trust tiers
  • Access is through a hosted API authenticated with an API key; no tool list is published, so exact operations are not documented here.
When to use it
Useful when an assistant should answer questions or help act on GRC posture — compliance scoring, security findings, remediation tickets and agent trust levels — without leaving the chat for the Claw GRC dashboard.
Requirements
A remote MCP endpoint at api.clawgrc.com over streamable HTTP. A Claw GRC account and an API key (starts with cgrc_) created in the dashboard under Settings, API keys, sent in the X-API-Key header. No local runtime or packages needed.
Before you install
The API key is a secret sent in the X-API-Key header; keep it out of logs and shared transcripts. The server exposes compliance and security data, which is sensitive, and may allow changes to tickets or findings — confirm before any write. Tool list is not published, so review what it can do after connecting.

Installation

In SourceWeft

  1. Open Claw GRC in the dashboard and add it to a workspace.
  2. Connect X-API-Key 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.clawgrc%2Fmcp/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": {
    "claw-grc": {
      "type": "http",
      "url": "https://api.clawgrc.com/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 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.