21RISK MCP Server

by 21risk Your server? Claim it

answering

21RISK is answering right now. Last checked 6 min ago.

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

Uptime history 17 days of history · worst day 91%

17 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

244 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

21RISK does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://21risk.com/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://21risk.com/api/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://21risk.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://21risk.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://21risk.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://21risk.com/api/mcp	streamable-http	sign-in	300 ms	6 min ago

Alternatives to 21RISK

same job, measured the same way

Agent Index

by theagentindex

Free open dataset of compliance, security and risk AI agents and audit firms. Read-only search.

5 tools answering

GDPRWise

by gdprwise

GDPR compliance for SMEs: query and update your processing register, vendors and compliance items

answering

Domera: Swedish building compliance

by domera-proptech

Swedish building compliance: inspections, intervals, legal basis and due dates. Free, read-only.

1 tools answering

Jobsite

by jobsitecerts

Construction safety, training compliance and operations for your company (OAuth sign-in).

answering

agentweb

by brelsfordsoftware-agentweb

NAIC AI model bulletin adoption by state, with citations. Insurance AI compliance data.

3 tools answering

MCP Geracompliance

by geraservicesuk

EU AI Act and GDPR compliance: checks, audits, generate policies.

44 installs/wk local only

Dastra

by dastra

GDPR & privacy compliance: records of processing, data breaches, DSRs, risks, audits, AI systems.

answering

BlueNexus Universal MCP

by bluenexus

Connect your AI to all your data - 200+ sources, intelligently filtered, compliance-ready.

answering

21RISK — questions

Answers built from our own checks of this server.

Why is there no tool list for 21RISK?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is 21RISK working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 244 ms. The bar chart above shows every period we have measured.

How do I connect 21RISK?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to 21RISK?

No API key is involved. 21RISK answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is 21RISK?

It answers our handshake in 244 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.