English Français العربية

com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp

Official registry Security

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

Source code Documentation

What can you do with com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp?

  • 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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http mcpscopeconsent-mcp 'https://mcpscopeconsent.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcpscopeconsent-mcp": {
            "type": "http",
            "url": "https://mcpscopeconsent.clauxel.com/mcp",
            "headers": {
                "Authorization": "<Bearer token from the product website.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. MCP Scope Consent
  2. Start Here
  3. Remote MCP
  4. Reading Order
  5. Audience
  6. Capabilities
  7. Public-Safe Boundary

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

Reading Order

  1. Quickstart
  2. Evaluation guide
  3. Checkout and pricing
  4. Workflow notes
  5. Security model
  6. Public link reference

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.

Frequently asked questions

What is com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp?

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

How do I install com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http mcpscopeconsent-mcp 'https://mcpscopeconsent.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains com.clauxel.mcpscopeconsent/mcpscopeconsent-mcp?

It is published by clauxel. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.