Remove deprecated is_exclusive field from MCP specification

[Copilot]

The is_exclusive field in MCP server configuration is superseded by compliance level tagging and is no longer used.

Changes

Backend

• Removed is_exclusive from MCPServerConfig Pydantic model
• Removed is_server_exclusive() method from MCPToolManager
• Removed field from API responses and CLI output

Configuration

• Cleaned all JSON config files (8 files in config/, mocks/, scripts/)

Frontend

• Removed from demo fallback data and public config

Documentation

• Updated admin guide to remove field description and examples
• Updated copilot instructions and mock README

The compliance_level field provides access control without the exclusivity constraint.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• astral.sh
  • Triggering command: curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>phase out is_exclusive for mcp specification</issue_title>
<issue_description>The compliance tagging supersedes this. is_exclusive is no longer needed.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes phase out is_exclusive for mcp specification #61

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[garland3]

tested and it works.

[github-actions]

🔒 Security Scan Results

Security Scan Summary

Scan Results

Python SAST (Bandit)

⚠️ Security issues found in Python code

Recommendations

• Review all SARIF files uploaded to GitHub Security tab
• Address high and critical severity vulnerabilities immediately
• Run npm audit fix and pip-audit locally to fix dependencies
• Consider implementing additional security controls

[github-actions]

🔒 Security Scan Results

Security Scan Summary

Scan Results

Python SAST (Bandit)

⚠️ Security issues found in Python code

Recommendations

• Review all SARIF files uploaded to GitHub Security tab
• Address high and critical severity vulnerabilities immediately
• Run npm audit fix and pip-audit locally to fix dependencies
• Consider implementing additional security controls