Mcpscopeconsent Mcp

com.clauxel.mcpscopeconsentPublished by mcpscopeconsent.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

Remote MCP for MCP consent scope receipt, structured receipts, audit logs, and reviewer-ready eviden

VerifiedStreamable HTTPWeb executableProductivity & Workflow Security & Monitoring

Server details

Identifier: com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to mcpscopeconsent.clauxel.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.clauxel.mcpscopeconsent%2Fmcpscopeconsent-mcp.svg)](https://sourceweft.com/mcp/com.clauxel.mcpscopeconsent%2Fmcpscopeconsent-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted remote MCP server for checking MCP scope consent, issuing consent receipts, explaining scope policy, logging tool calls and exporting audit evidence.

What you can do: Check and explain consent scope: verify scope consent and describe the applicable scope policy
Issue consent receipts: generate structured receipts for consent decisions
Log and export audit evidence: record tool calls and export scope audit records for reviewers
Return structured tool-call output suitable for governance documentation
When to use it: Meant for AI governance teams, policy reviewers, trust and safety leads and compliance operators who need a record of what an assistant was permitted to do and reviewer-ready evidence of consent decisions.
Requirements: A remote streamable HTTP endpoint; no local package or runtime is needed. Production calls require an Authorization header carrying a bearer token obtained from the product website. The README also points to pricing and checkout pages, so access may be paid.

Before you install

The bearer token is a credential and must be kept private. The server issues receipts and logs tool calls, so it records activity about your assistant's tool use; consider what that data contains and where it is sent. Pricing and checkout pages suggest a paid product. The public repository is documentation only and contains no production source code.

Installation

In SourceWeft

Open Mcpscopeconsent Mcp in the dashboard and add it to a workspace.
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.mcpscopeconsent%2Fmcpscopeconsent-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": {
    "mcpscopeconsent": {
      "type": "http",
      "url": "https://mcpscopeconsent.clauxel.com/mcp"
    }
  }
}

README

MCP Scope Consent

MCP Scope Consent is a hosted remote MCP for MCP consent scope receipt.

This repository is a public documentation project for MCP Scope Consent. Its structure follows the public documentation pattern used by MiroFish: a short front door, a clear reading order, practical guides, reference pages, and a public-safe boundary.

Start Here

Remote MCP

Endpoint: https://mcpscopeconsent.clauxel.com/mcp
Server card: https://mcpscopeconsent.clauxel.com/server-card.json
Registry name: com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp
Tools: check_scope_consent, issue_consent_receipt, explain_scope_policy, log_tool_call, export_scope_audit

Reading Order

Audience

AI governance teams, policy reviewers, trust and safety leads, and compliance operators.

Capabilities

Streamable HTTP MCP endpoint
Bearer-token access for production calls
Structured tool-call output
Receipt-oriented evidence export
Public server card and registry metadata
MCP tool: check_scope_consent
MCP tool: issue_consent_receipt
MCP tool: explain_scope_policy
MCP tool: log_tool_call
MCP tool: export_scope_audit

Public-Safe Boundary

This repository contains documentation only. It does not contain production source code, credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths.

Source: README.md at commit 885cbd5

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.0LatestSep 16, 2026

Score

60% 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
License10 pts