com.clauxel.mcptoollicense/mcptoollicense-mcp

Official registry Other

Remote MCP for tool license checks, vendor policy review, alternatives, and license receipts.

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

  • license parser
  • customer policy rules
  • tool allowlist
  • structured verdict JSON
  • alternative suggestions

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 mcptoollicense-mcp 'https://mcptoollicense.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mcptoollicense-mcp": {
            "type": "http",
            "url": "https://mcptoollicense.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 Tool License Gate
  2. Start Here
  3. Remote MCP
  4. Reading Order
  5. Audience
  6. Capabilities
  7. Public-Safe Boundary

MCP Tool License Gate

Check third-party tool rights before an agent calls them.

MCP Tool License Gate is a paid remote MCP gate for tool name, vendor URL, license text, intended use, customer policy, data class, alternatives, and license receipts.

This is a public documentation project for MCP Tool License Gate. The structure is modeled after the public documentation pattern used by MiroFish: a short front door, a clear reading order, practical guides, reference pages, and public-safe architecture notes.

Start Here

Remote MCP

Reading Order

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

Audience

MCP platform owners, security reviewers, procurement teams, and agent builders.

Capabilities

  • license parser
  • customer policy rules
  • tool allowlist
  • structured verdict JSON
  • alternative suggestions

Public-Safe Boundary

This repository 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.mcptoollicense/mcptoollicense-mcp?

Remote MCP for tool license checks, vendor policy review, alternatives, and license receipts.

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

It runs as a remote server. In Claude Code: claude mcp add --transport http mcptoollicense-mcp 'https://mcptoollicense.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.mcptoollicense/mcptoollicense-mcp need an API key?

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

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

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

Who maintains com.clauxel.mcptoollicense/mcptoollicense-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.