Modern MCP protocol compatibility
The hosted endpoint supports established initialization flows and the current stateless protocol generation. The production package stays on the supported v1 SDK while split v2 SDK packages and the final protocol revision are still in beta.
Supported protocol behavior
Section titled “Supported protocol behavior”Established clients can initialize with:
2025-03-262025-06-182025-11-25
Modern clients can use:
server/discoverMCP-Protocol-VersionandMcp-Methodheaders- inline protocol and client metadata
- required
resultType: "complete"result discriminators - explicit cache lifetime and scope on list responses
- stateless tool, prompt, and resource requests
The canonical hosted endpoint is:
https://mcp.axint.ai/mcpLocal stdio remains supported
Section titled “Local stdio remains supported”{ "mcpServers": { "axint": { "command": "npx", "args": ["-y", "-p", "@axint/compiler", "axint-mcp"] } }}Use local stdio when project source, paths, and artifacts must stay on the machine. Use hosted HTTP when the client needs a remote connection and the requested tool’s data boundary is acceptable.
Production verification
Section titled “Production verification”npm run mcp:production:checkRelease automation checks:
- hosted package identity
- tool and prompt inventory
- established initialization
- modern discovery and stateless requests
- cache and result metadata
CI separately connects with the current official split TypeScript beta client.