Mcptoollicense Mcp
Wire your coding agent to verify third-party tool licenses, vendor policies, and safer alternatives before you adopt or ship dependencies.
Overview
MCP Tool License Gate is a MCP server for the Ship phase that checks tool licenses, reviews vendor policy, suggests alternatives, and returns license receipts for agent workflows.
What is this MCP server?
- Remote streamable-http MCP at mcptoollicense.clauxel.com with Bearer authorization
- Tool license checks with vendor policy review and documented alternatives
- License receipts suitable for audit trails and agent decision logs
- Publisher tags: mcp, license-check, tool-governance, remote-mcp
- Open-source implementation on GitHub (clauxel/mcp-tool-license-gate)
- Registry version 1.0.0
- 1 remote streamable-http endpoint documented in server metadata
- 4 publisher registry tags: mcp, license-check, tool-governance, remote-mcp
What problem does it solve?
Solo builders adopting libraries and SaaS tools through agents rarely capture whether vendor licenses actually allow production use until something breaks compliance.
Who is it for?
Indie builders stacking MCP servers and third-party APIs who want the agent to pause on license risk instead of silently adding non-compliant tools.
Skip if: Teams that only need generic open-source license scanning in CI without agent-facing policy review or remote MCP tooling.
What do I get? / Deliverables
After you register the remote MCP with a Bearer token, your agent can run governed license checks and keep receipts you can reference before and after you ship integrations.
- Structured license check results for named tools or vendors
- Policy review notes and suggested alternative tools when risk is high
- License receipts suitable for logging alongside agent actions
Recommended MCP Servers
Journey fit
License and vendor-policy mistakes surface hardest at ship time, so the canonical shelf is Ship with a security lens even though checks help earlier in the journey. Tool-governance and compliance gates belong on the security subphase because they reduce legal and supply-chain risk in production-bound work.
How it compares
Remote MCP license-governance integration, not a local SPDX scanner or a single Claude skill markdown file.
Common Questions / FAQ
Who is MCP Tool License Gate for?
It is for solo and indie builders using Claude Code, Cursor, or similar agents who add paid or restricted third-party tools and want license checks inside the agent loop.
When should I use MCP Tool License Gate?
Use it before committing to a vendor during validate, when adding integrations in build, and again in ship security review when dependencies change.
How do I add MCP Tool License Gate to my agent?
Register the remote MCP URL https://mcptoollicense.clauxel.com/mcp (streamable-http) in your client and set Authorization to a Bearer token from the Clauxel product site.