How a SaaS MCP server and its authorization server meet the MCP spec: protected resource metadata, Client ID Metadata Documents, a DCR fallback and API keys.
The attacks a SaaS company's MCP server is exposed to, from prompt injection to tool poisoning and SSRF, and the defenses the MCP spec and OWASP set out.
What an MCP server adds on top of your API: runtime tool discovery, descriptions the model reads, per-user OAuth, and tools designed around jobs, not endpoints.
The rules each directory's reviewers check for MCP connectors and plugins on Claude, ChatGPT and Cursor, from the platforms' docs, and how to check them first.