MYASP.NET MCP · BETA
Beta Changelog
BetaRelease notes for the myASP.NET Developer Platform Beta.
Beta
Security hardening and reduced surface
- Visitor Statistics, Schedule Tasks, and Outgoing Port rules are not accessible through generic website-function tools.
- Advanced Custom Backup, backup upload, database import, and database restore tools remain outside MCP discovery.
- Windows Node.js and ASP.NET application paths use strict website-relative validation.
- Drawer responses drop unknown fields by default, writes use durable idempotency, and API-key validation is protected by pre-authentication throttling.
- The obsolete MCP OAuth-pairing implementation and identity-link fallback were removed.
Beta
Initial public Beta documentation
- API-key authentication for MCP clients; OAuth is not required.
- Existing-plan resource discovery for Windows and Linux hosting.
- Website create, update, runtime, safe drawer, environment-secret, and delete operations.
- Domain mapping, DNS record management, and separate free-SSL lifecycle.
- MSSQL, MySQL, and PostgreSQL database, user, and credential workflows.
- Email-domain and mailbox lifecycle, passwordless profile updates, quota changes, mail-client settings, and same-mailbox SMTP tests.
- GitHub-owned deployment using IIS WebDeploy for compatible Windows plans and FTPS for Linux plans.
- Durable idempotency, exact confirmations, sanitized outputs, and operation status.
Beta compatibilityWe aim to preserve existing tool names and required-field behavior throughout Beta. Additive fields and new tools may appear as the platform expands.