@miraigent/free-ai-ops-mcp 0.1.41 → 0.1.42

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## [0.1.42] - 2026-07-18
+
+### Changed
+
+- Clarified that the public help header prints the package version and added
+  smoke-test coverage for that header so npm users can spot stale `npx` cache
+  behavior before editing MCP client configuration.
+
 ## [0.1.41] - 2026-07-17
 
 ### Changed

package/README.md

@@ -53,7 +53,10 @@ If you are checking the package from npm search, run the public help first:
     npx -y free-ai-ops-mcp@npm:@miraigent/free-ai-ops-mcp --help
 
 The help output lists the available MCP tools, the one-command smoke test, and
-the public-safe boundary before you send any JSON-RPC input.
+the public-safe boundary before you send any JSON-RPC input. The first line
+also prints `Miraigent Free AI Ops MCP <version>`, which is the quickest way to
+confirm whether `npx` is using the current public package or a stale local
+cache.
 
 If a local npx cache or desktop MCP client appears stale, compare it with the
 public registry version before changing private client configuration:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@miraigent/free-ai-ops-mcp",
-  "version": "0.1.41",
+  "version": "0.1.42",
   "description": "Free MCP server for developers adding human review gates, prompt risk checks, FAQ review, and CRM note safety to AI tools.",
   "homepage": "https://github.com/Miraigent/miraigent-free-ai-ops-mcp",
   "type": "module",

package/scripts/smoke-test.mjs

@@ -22,6 +22,7 @@ await new Promise((resolve, reject) => {
 });
 
 assert.match(helpStdout, /npx -y free-ai-ops-mcp@npm:@miraigent\/free-ai-ops-mcp/);
+assert.match(helpStdout, new RegExp(`Miraigent Free AI Ops MCP ${packageJson.version.replaceAll('.', '\\.')}`));
 assert.match(helpStdout, /human_review_gate/);
 assert.match(helpStdout, /Do not paste secrets/);
 assert.match(helpStdout, /private memory behavior/);