MCP Risk Ledger MCP

com.clauxel.mcpriskledgerPublished by mcpriskledger.clauxel.comOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A paid remote MCP server that produces intake risk reports, tool reviews, approvals, and readiness checks for MCP servers.

What you can do
This remote MCP server is described as a paid service for server intake risk reporting, tool review, approvals, and readiness assessment. It is intended to help an assistant evaluate MCP servers before they are adopted. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
When to use it
Consider it when you need a structured risk or readiness review of an MCP server before approving or installing it. It is aimed at intake and approval workflows rather than general-purpose tasks.
Requirements
A remote streamable HTTP endpoint at the provider's host. Authentication is required: a bearer token sent in the Authorization header, issued after checkout and an MCP token claim. No packages or environment variables are declared.
Before you install
It is a paid service, so using it involves a checkout and likely spending money. The Authorization bearer token is a secret and must be handled carefully. The server is remote, so requests and any submitted server details are sent to a third party.

Installation

In SourceWeft

  1. Open MCP Risk Ledger MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.clauxel.mcpriskledger%2Fmcpriskledger-mcp/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": {
    "risk-ledger": {
      "type": "http",
      "url": "https://mcpriskledger.clauxel.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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. v0.1.0LatestSep 16, 2026

Score

39% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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