mcpbeat

MCP Risk Ledger MCP Server

com.clauxel.mcpriskledger/mcpriskledger-mcp
answering

MCP Risk Ledger MCP is answering right now. Last checked 8 min ago.

Paid remote MCP for server intake risk reports, tool review, approvals, and readiness.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
1038 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add mcpriskledger-mcp --transport http https://mcpriskledger.clauxel.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcpriskledger-mcp": {
      "url": "https://mcpriskledger.clauxel.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcpriskledger-mcp]
url = "https://mcpriskledger.clauxel.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcpriskledger-mcp": {
      "url": "https://mcpriskledger.clauxel.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcpriskledger-mcp": {
      "url": "https://mcpriskledger.clauxel.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcpriskledger.clauxel.com/mcp streamable-http needs key 1220 ms 8 min ago

MCP Risk Ledger MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for MCP Risk Ledger MCP?
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 MCP Risk Ledger MCP 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 1038 ms. The bar chart above shows every period we have measured.
How do I connect MCP Risk Ledger MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does MCP Risk Ledger MCP need an API key?
Yes. Every time we knock, MCP Risk Ledger MCP answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is MCP Risk Ledger MCP?
It answers our handshake in 1038 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.