deploy-mcp 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,45 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2025-01-15
+
+### Added
+
+- Initial release of deploy-mcp
+- MCP server for deployment status tracking
+- Vercel adapter with full API integration
+- Professional landing page with AI tools configuration
+- Support for multiple AI assistants:
+  - Claude Desktop (official support)
+  - VS Code with GitHub Copilot
+  - Cursor AI
+  - Windsurf IDE
+  - Continue.dev
+  - Cline
+- Comprehensive configuration examples and documentation
+- TypeScript with strict mode
+- ESLint + Prettier with automated formatting
+- Vitest testing framework
+- Husky pre-commit hooks
+- Cloudflare Workers deployment
+- Feature-based adapter architecture
+- Professional package.json scripts
+- Security policy and community guidelines
+
+### Technical Details
+
+- Node.js 22+ requirement
+- Updated MCP SDK to 1.11.2
+- Zero runtime dependencies for core functionality
+- Strict TypeScript compilation
+- Automated code quality checks
+- Professional open source project structure
+
+[Unreleased]: https://github.com/alexpota/deploy-mcp/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/alexpota/deploy-mcp/releases/tag/v0.1.0

package/LICENSE

@@ -0,0 +1,55 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

package/README.md

@@ -0,0 +1,499 @@
+<div align="center">
+
+# deploy-mcp
+
+**Universal Deployment Tracker for AI Assistants**
+
+Track deployments across all platforms directly in your AI conversation.  
+No more context-switching. No more dashboard hunting.
+
+[![npm version](https://img.shields.io/npm/v/deploy-mcp.svg?style=for-the-badge&color=ff6b6b)](https://www.npmjs.com/package/deploy-mcp)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg?style=for-the-badge)](https://github.com/alexpota/deploy-mcp/blob/main/LICENSE)
+[![Website](https://img.shields.io/badge/website-deploy--mcp.io-ff8e53?style=for-the-badge)](https://deploy-mcp.io)
+
+</div>
+
+---
+
+## Demo
+
+```
+// In your AI conversation:
+"Check my latest Vercel deployment"
+
+// Claude's Response:
+✅ **Status**: Success  
+🌐 **Live URL**: https://my-app.vercel.app  
+⏱️ **Deployment Time**: 45 seconds  
+📅 **Last Deployed**: January 15, 2025 at 10:30 UTC  
+🌍 **Environment**: Production  
+
+**Latest Commit**:
+- SHA: `abc123ef`
+- Message: "Update homepage hero section"
+- Author: John Doe
+
+Everything looks good - your deployment is live and running successfully!
+```
+
+**Just ask your AI**: *"What's the status of my latest deployment?"*  
+Get instant answers without leaving your conversation.
+
+## Features
+
+<table>
+<tr>
+<td width="50%">
+
+**Universal AI Support**  
+Built for the Model Context Protocol. Works seamlessly with Claude Desktop, VS Code, Cursor, Windsurf, Continue.dev, Cline, and any MCP-compatible AI assistant.
+
+**Secure & Private**  
+Your API tokens stay local on your machine. Never sent to third parties or logged anywhere.
+
+**Lightning Fast**  
+Get deployment status in under 2 seconds. Optimized for developer productivity.
+
+</td>
+<td width="50%">
+
+**Zero Context Switching**  
+Check deployment status without leaving your AI conversation.
+
+**Universal Platform Support**  
+Currently supports Vercel, with Netlify, Railway, and Render coming soon.
+
+**Real-time Status**  
+Get instant deployment status through AI conversation.
+
+**Open Source**  
+Fully transparent, community-driven development.
+
+</td>
+</tr>
+</table>
+
+## Why deploy-mcp?
+
+**The Problem**: Developers context-switch 10-20 times per day to check deployment status, losing 23 minutes of focus each time.
+
+**The Solution**: deploy-mcp brings deployment status directly into your AI conversation. No more alt-tabbing, no more dashboard hunting, no more broken flow state.
+
+Built for the modern developer who uses AI assistants as part of their daily workflow.
+
+## Quick Start
+
+**Get started in under 30 seconds:**
+
+```bash
+npx deploy-mcp
+```
+
+That's it! The server is now running and ready to be configured in your AI assistant.
+
+## Configuration
+
+### AI Assistants
+
+<details>
+<summary><strong>Claude Desktop</strong> ✅</summary>
+
+**Official MCP support** - Ready to use today
+
+**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`  
+**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`  
+**Linux**: `~/.config/Claude/claude_desktop_config.json`
+
+</details>
+
+<details>
+<summary><strong>VS Code</strong> ✅</summary>
+
+**Official MCP support** - Generally available in VS Code 1.102+
+
+Add to workspace `.vscode/mcp.json` or global `~/.vscode/mcp.json`
+
+Requires GitHub Copilot subscription and MCP policy enabled by organization.
+</details>
+
+<details>
+<summary><strong>Cursor AI</strong> ✅</summary>
+
+**Official MCP support** - Available with one-click installation
+
+Navigate to Cursor Settings → MCP or create `~/.cursor/mcp.json`
+
+</details>
+
+<details>
+<summary><strong>Windsurf IDE</strong> ✅</summary>
+
+**Official MCP support** - Native integration with Cascade
+
+Navigate to Windsurf Settings → Advanced Settings → Cascade or edit `~/.codeium/windsurf/mcp_config.json`
+
+</details>
+
+<details>
+<summary><strong>Continue.dev</strong> ✅</summary>
+
+**Official MCP support** - Available in agent mode
+
+Add to your `config.json` with different structure:
+
+```json
+{
+  "experimental": {
+    "modelContextProtocolServer": {
+      "transport": {
+        "type": "stdio",
+        "command": "npx",
+        "args": ["-y", "deploy-mcp"]
+      },
+      "env": {
+        "VERCEL_TOKEN": "your-vercel-token"
+      }
+    }
+  }
+}
+```
+
+Or create `.continue/mcpServers/` folder in your workspace.
+</details>
+
+<details>
+<summary><strong>Cline (VS Code)</strong> ✅</summary>
+
+**Official MCP support** - Can create and install tools automatically
+
+Cline can install deploy-mcp through natural language:
+- Ask: *"Add the deploy-mcp tool to check Vercel deployments"*
+- Or manually configure via MCP Servers icon → Advanced MCP Settings
+
+</details>
+
+**+ Any MCP-compatible tool**  
+Works with all AI assistants that support [Model Context Protocol](https://modelcontextprotocol.io)
+
+### MCP Configuration
+
+All AI tools (except Continue.dev) use the same configuration:
+
+```json
+{
+  "mcpServers": {
+    "deploy-mcp": {
+      "command": "npx",
+      "args": ["-y", "deploy-mcp"],
+      "env": {
+        "VERCEL_TOKEN": "your-vercel-token"
+      }
+    }
+  }
+}
+```
+
+💡 Replace `your-vercel-token` with your actual Vercel API token from [vercel.com/account/tokens](https://vercel.com/account/tokens)
+
+
+### Getting API Tokens
+
+<details>
+<summary><strong>Vercel</strong></summary>
+
+1. Go to [Vercel Dashboard](https://vercel.com/account/tokens)
+2. Click **"Create Token"**
+3. Give it a descriptive name (e.g., "deploy-mcp")
+4. Select appropriate scope (read-only is sufficient)
+5. Copy the token and add it to your configuration
+
+</details>
+
+<details>
+<summary><strong>Netlify</strong> (Coming Soon)</summary>
+
+1. Go to [Netlify User Settings](https://app.netlify.com/user/applications#personal-access-tokens)
+2. Click **"New access token"**
+3. Give it a descriptive name
+4. Copy the token
+</details>
+
+<details>
+<summary><strong>Railway</strong> (Coming Soon)</summary>
+
+Railway integration is on our roadmap. [Star the repo](https://github.com/alexpota/deploy-mcp) to get notified!
+</details>
+
+<details>
+<summary><strong>Render</strong> (Coming Soon)</summary>
+
+Render integration is on our roadmap. [Star the repo](https://github.com/alexpota/deploy-mcp) to get notified!
+</details>
+
+## Usage Examples
+
+### In Your AI Conversation
+
+Once configured, simply ask your AI assistant:
+
+```
+You: Check my latest Vercel deployment
+
+
+Assistant: I'll check your latest Vercel deployment for you.
+
+✅ **Status**: Success
+🌐 **Live URL**: https://my-app.vercel.app
+⏱️ **Deployment Time**: 45 seconds
+📅 **Last Deployed**: January 15, 2025 at 10:30 UTC
+🌍 **Environment**: Production
+
+**Latest Commit**:
+- SHA: `abc123ef`
+- Message: "Update homepage hero section"
+- Author: John Doe
+
+Everything looks good - your deployment is live and running successfully!
+```
+
+### More Examples
+
+- `"Is my website deployment finished?"`
+- `"Show me the deployment status for project-xyz"`
+- `"Check if the production deployment succeeded"`
+- `"What's the status of my latest deploy?"`
+
+
+## MCP Tools Reference
+Retrieve the latest deployment status for a project.
+
+<details>
+<summary><strong>Parameters</strong></summary>
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `platform` | string | ✓ | Deployment platform (`vercel`, `netlify`, etc.) |
+| `project` | string | ✓ | Project name or ID |
+| `token` | string | ✗ | API token (uses env variable if not provided) |
+
+</details>
+
+<details>
+<summary><strong>Response Format</strong></summary>
+
+```typescript
+{
+  status: "success" | "failed" | "building" | "error",
+  url: string,
+  projectName: string,
+  platform: string,
+  timestamp: string,
+  duration: number,
+  environment: "production" | "preview" | "development",
+  commit: {
+    sha: string,
+    message: string,
+    author: string
+  }
+}
+```
+
+</details>
+
+## Development
+
+For contributors who want to help develop deploy-mcp.
+
+### Prerequisites
+
+- Node.js 22 or higher
+- npm, yarn, or pnpm
+
+### Local Development
+
+```bash
+# Clone the repository
+git clone https://github.com/alexpota/deploy-mcp.git
+cd deploy-mcp
+
+# Install dependencies
+npm install
+
+# Run in development mode  
+npm run dev
+```
+
+### Testing
+
+```bash
+# Run tests
+npm test
+
+# Type checking
+npm run lint
+```
+
+### Building & Deployment
+
+```bash
+# Build TypeScript
+npm run build
+
+# Deploy worker to Cloudflare
+npm run deploy
+
+# Development worker server
+npm run dev:worker
+```
+
+## Project Structure
+
+```
+deploy-mcp/
+├── src/
+│   ├── index.ts              # MCP server entry point
+│   ├── worker.ts             # Cloudflare Worker for website
+│   ├── adapters/             # Platform adapters (new structure)
+│   │   ├── base/             # Base adapter framework
+│   │   │   ├── adapter.ts    # Abstract base class
+│   │   │   ├── types.ts      # Common interfaces
+│   │   │   └── index.ts      # Base exports
+│   │   ├── vercel/           # Vercel platform support
+│   │   │   ├── index.ts      # Main adapter class
+│   │   │   ├── types.ts      # Vercel-specific types
+│   │   │   ├── api.ts        # API client
+│   │   │   └── __tests__/    # Vercel tests
+│   │   └── index.ts          # All adapter exports
+│   ├── core/
+│   │   ├── mcp-handler.ts    # MCP protocol implementation
+│   │   └── tools.ts          # MCP tool definitions
+│   ├── server/
+│   │   └── badge.ts          # SVG badge generation (v0.2.0)
+│   └── types.ts              # TypeScript definitions
+├── tests/                    # Integration tests
+├── dist/                     # Compiled output
+├── wrangler.toml            # Cloudflare config
+├── tsconfig.json            # TypeScript config
+└── package.json             # Project metadata
+```
+
+## Security
+
+### Our Security Commitments
+
+- **Local-Only Tokens** - Your API tokens never leave your machine
+- **No Data Collection** - We don't track, log, or store any user data
+- **Direct API Calls** - All platform APIs are called directly from your local MCP server
+- **Open Source** - Full transparency with auditable code
+- **Badge Service** - Coming in v0.2.0 with webhook-based live deployment badges
+
+### Best Practices
+
+1. **Use Read-Only Tokens** - When possible, create tokens with minimal permissions
+2. **Rotate Tokens Regularly** - Update your tokens periodically
+3. **Environment Variables** - Store tokens in environment variables, not in code
+4. **Git Ignore** - Never commit configuration files with tokens
+
+## Platform Support
+
+<table>
+  <thead>
+    <tr>
+      <th>Platform</th>
+      <th>Status</th>
+      <th>Features</th>
+      <th>Documentation</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td><strong>Vercel</strong></td>
+      <td><strong>✓ Supported</strong></td>
+      <td>Full deployment tracking with real-time status updates</td>
+      <td><a href="https://deploy-mcp.io/docs/vercel">View Guide</a></td>
+    </tr>
+    <tr>
+      <td><strong>Netlify</strong></td>
+      <td><strong>Coming Soon</strong></td>
+      <td>In active development</td>
+      <td>Coming soon</td>
+    </tr>
+    <tr>
+      <td><strong>Railway</strong></td>
+      <td><strong>Planned</strong></td>
+      <td>On the roadmap</td>
+      <td>-</td>
+    </tr>
+    <tr>
+      <td><strong>Render</strong></td>
+      <td><strong>Planned</strong></td>
+      <td>On the roadmap</td>
+      <td>-</td>
+    </tr>
+  </tbody>
+</table>
+
+Want support for another platform? [Open an issue](https://github.com/alexpota/deploy-mcp/issues/new) or submit a PR\!
+
+## Contributing
+
+We love contributions\! Whether it's a bug fix, new feature, or platform support, we'd love to have you.
+
+### Quick Start
+
+1. Fork the repository
+2. Create your feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+### Adding Platform Support
+
+Want to add support for a new platform? Here's how:
+
+1. **Create an adapter folder** in `src/adapters/your-platform/`
+2. **Implement the interface**:
+   ```typescript
+   export class YourPlatformAdapter extends BaseAdapter {
+     async getDeploymentStatus(project: string, token: string) {
+       // Your implementation
+     }
+   }
+   ```
+3. **Add tests** in `src/adapters/your-platform/__tests__/`
+4. **Update docs** with setup instructions
+5. **Submit a PR** and we'll review it\!
+
+See our [Contributing Guide](CONTRIBUTING.md) for more details.
+
+## License
+
+This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
+
+## Acknowledgments
+
+- Built with [Model Context Protocol SDK](https://github.com/modelcontextprotocol/sdk) by Anthropic
+- Hosted on [Cloudflare Workers](https://workers.cloudflare.com) for global edge performance
+- Icons from [Feather Icons](https://feathericons.com) and [Heroicons](https://heroicons.com)
+
+## Community & Support
+
+<div align="center">
+  <a href="https://github.com/alexpota/deploy-mcp/discussions">
+    <img src="https://img.shields.io/badge/GitHub-Discussions-181717?style=for-the-badge&logo=github" alt="GitHub Discussions" />
+  </a>
+  <a href="https://github.com/alexpota/deploy-mcp/issues">
+    <img src="https://img.shields.io/badge/Report-Issues-ff6b6b?style=for-the-badge&logo=github" alt="Report Issues" />
+  </a>
+  <a href="mailto:alex.potapenko.dev@gmail.com">
+    <img src="https://img.shields.io/badge/Email-alex.potapenko.dev@gmail.com-ff6b6b?style=for-the-badge&logo=gmail" alt="Email" />
+  </a>
+</div>
+
+---
+
+<div align="center">
+  <p>Made with ❤️ by <a href="https://github.com/alexpota">Alex Potapenko</a> and contributors</p>
+  <p><a href="https://deploy-mcp.io">deploy-mcp.io</a> • <a href="https://github.com/alexpota/deploy-mcp">GitHub</a> • <a href="https://www.npmjs.com/package/deploy-mcp">NPM</a></p>
+</div>
+

package/SECURITY.md

@@ -0,0 +1,61 @@
+# Security Policy
+
+## Supported Versions
+
+We take security seriously and provide security updates for the following versions:
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 0.1.x   | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in deploy-mcp, please help us maintain the security of the project by reporting it responsibly.
+
+### How to Report
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please send an email to: **alex.potapenko.dev@gmail.com**
+
+Include the following information:
+- Description of the vulnerability
+- Steps to reproduce the issue
+- Potential impact assessment
+- Any suggested fixes or mitigations
+
+### Response Timeline
+
+- **Initial Response**: Within 48 hours of receiving your report
+- **Status Update**: Weekly updates on investigation progress
+- **Resolution**: Security fixes are prioritized and typically released within 7-14 days
+
+### Disclosure Policy
+
+- We will acknowledge receipt of your vulnerability report within 2 business days
+- We will provide regular updates on our investigation and remediation timeline
+- We will notify you when the vulnerability has been fixed
+- We will publicly disclose the vulnerability details after a fix has been released and deployed
+
+### Security Best Practices
+
+When using deploy-mcp in production:
+
+1. **API Token Security**: Store tokens in environment variables, never in code or version control
+2. **Token Permissions**: Use read-only API tokens when possible to minimize risk
+3. **Token Rotation**: Regularly rotate API tokens for enhanced security
+4. **Network Security**: Ensure secure connections when accessing deployment platforms
+5. **Updates**: Keep deploy-mcp and its dependencies up to date
+
+### Security Features
+
+deploy-mcp includes several security-conscious design decisions:
+
+- **Local-only token storage** - API tokens never leave your machine
+- **No data collection** - Zero tracking or analytics of user data
+- **Direct API calls** - All requests go directly to deployment platforms
+- **Input validation** using Zod schemas to prevent injection attacks
+- **Minimal dependencies** to reduce supply chain risks
+- **Strict TypeScript** compilation to catch potential issues at build time
+
+Thank you for helping keep deploy-mcp and the Node.js ecosystem secure.