check_non_compete_enforceability — contracts MCP Tool Read-only
check_non_compete_enforceability
(check non compete enforceability) is one of 8 tools on the
contracts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_non_compete_enforceability from your client
- Claude Code contracts check_non_compete_enforceability run in your project directory
- Claude Desktop contracts check_non_compete_enforceability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor contracts check_non_compete_enforceability ~/.cursor/mcp.json
- VS Code contracts check_non_compete_enforceability .vscode/mcp.json
- Zed contracts check_non_compete_enforceability ~/.config/zed/settings.json
- Windsurf contracts check_non_compete_enforceability ~/.codeium/windsurf/mcp_config.json
- Cline contracts check_non_compete_enforceability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI contracts check_non_compete_enforceability ~/.gemini/settings.json
- Grok contracts check_non_compete_enforceability .mcp.json (in your project root)
- ChatGPT contracts check_non_compete_enforceability Settings → Connectors → Advanced → Developer mode
- Claude.ai contracts check_non_compete_enforceability Settings → Connectors → Add custom connector
- LangChain contracts check_non_compete_enforceability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http contracts https://www.pactlio.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.