docs: align hosted endpoint documentation (#980)

Co-authored-by: CharlieHelps <charlie@charlielabs.ai>

Author: charliecreates[bot]

.changeset/hosted-endpoint-docs.md

@@ -0,0 +1,5 @@
+---
+"hevy-mcp": patch
+---
+
+Update the published Node package documentation to use the current hosted MCP endpoint.

packages/node/README.md

@@ -80,7 +80,7 @@ so your client does not need Node.js, Bun, Docker, or a local server process.
 Production URL:
 
 ```text
-https://hevy.chrisdoc.dev/mcp
+https://mcp.hevy-mcp.dev/mcp
 ```
 
 The endpoint uses Streamable HTTP. Send your Hevy API key as a bearer token on
@@ -95,7 +95,7 @@ Codex, then add the hosted server:
 ```bash
 export HEVY_API_KEY=your-hevy-api-key
 codex mcp add hevy \
-  --url https://hevy.chrisdoc.dev/mcp \
+  --url https://mcp.hevy-mcp.dev/mcp \
   --bearer-token-env-var HEVY_API_KEY
 ```
 
@@ -111,7 +111,7 @@ Clients that accept a remote MCP URL and fixed headers commonly use this shape:
 {
 	"mcpServers": {
 		"hevy": {
-			"url": "https://hevy.chrisdoc.dev/mcp",
+			"url": "https://mcp.hevy-mcp.dev/mcp",
 			"headers": {
 				"Authorization": "Bearer your-hevy-api-key"
 			}
@@ -363,7 +363,7 @@ corresponding delete tools.
 The production MCP server is live at:
 
 ```text
-https://hevy.chrisdoc.dev/mcp
+https://mcp.hevy-mcp.dev/mcp
 ```
 
 It is the quickest way to use `hevy-mcp`: there is nothing to install or keep
@@ -377,7 +377,7 @@ Clients must send their Hevy API key as a fixed authorization header:
 {
 	"mcpServers": {
 		"hevy": {
-			"url": "https://hevy.chrisdoc.dev/mcp",
+			"url": "https://mcp.hevy-mcp.dev/mcp",
 			"headers": {
 				"Authorization": "Bearer your-hevy-api-key"
 			}