21RISK

com.21riskPublished by 21risk.comOfficial publisherv1.0.0Updated Oct 24, 2026

Read and update your 21RISK data: sites, audits, compliance, actions, claims and insurance values.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Lets an assistant read and update 21RISK data such as sites, audits, compliance, actions, claims and insurance values.

What you can do
This is a remote MCP endpoint for the 21RISK risk and compliance platform. According to the registry description, it lets an assistant read and update records covering sites, audits, compliance, actions, claims and insurance values. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when an assistant should work with an organization's 21RISK risk, audit and insurance data, for example to look up sites or audits or to keep actions and compliance records current.
Requirements
A remote endpoint at 21risk.com over streamable HTTP. OAuth authentication is required, so a 21RISK account with access to the relevant data is needed. No environment variables or headers are declared.
Before you install
The server can update data, not just read it, so changes to sites, audits, compliance, actions, claims and insurance values may be written back to the platform. Access is granted through OAuth to your 21RISK account; review which permissions you approve. Specific tools and their side effects are not listed in the manifest.

Installation

In SourceWeft

  1. Open 21RISK 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.21risk%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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "21risk": {
      "type": "http",
      "url": "https://21risk.com/api/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 15, 2026

Score

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