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

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [0.1.43] - 2026-07-19
+
+### Changed
+
+- Added a README command that extracts and parses the bundled JSON-RPC smoke-test
+  result without copy-pasting response lines, plus smoke-test coverage so the
+  public proof path stays visible for npm users.
+
+## [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:
@@ -197,6 +200,15 @@ smoke-test output and inspect the wrapped text field with Node:
 
     node -e 'const r=JSON.parse(process.argv[1]); console.log(JSON.parse(r.result.content[0].text));' '<paste one response line here>'
 
+To avoid copying any response text at all, run the bundled public sample and
+parse only its final synthetic tool-call response:
+
+    npx -y free-ai-ops-mcp@npm:@miraigent/free-ai-ops-mcp < examples/mcp-json-rpc-session/sample-session.jsonl | tail -n 1 | node -e 'process.stdin.on("data", c => { const r = JSON.parse(c); console.log(JSON.parse(r.result.content[0].text).gateStatus); })'
+
+That prints `stop` for the bundled support-reply example. If it does, the
+package is returning the expected MCP result shape and you can debug client
+configuration separately from tool behavior.
+
 Paste only the synthetic response from the public example. Do not paste private
 customer records or desktop client logs into shell history, screenshots, or
 GitHub issues.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@miraigent/free-ai-ops-mcp",
-  "version": "0.1.41",
+  "version": "0.1.43",
   "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

@@ -3,6 +3,7 @@ import assert from 'node:assert';
 import { readFile } from 'node:fs/promises';
 
 const packageJson = JSON.parse(await readFile(new URL('../package.json', import.meta.url), 'utf8'));
+const rootReadme = await readFile(new URL('../README.md', import.meta.url), 'utf8');
 
 const helpChild = spawn(process.execPath, ['mcp/free-ai-ops-server.mjs', '--help'], {
   stdio: ['ignore', 'pipe', 'inherit']
@@ -22,10 +23,13 @@ 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/);
 assert.match(helpStdout, /github\.com\/Miraigent\/miraigent-free-ai-ops-mcp\/issues\/new\/choose/);
+assert.match(rootReadme, /tail -n 1 \| node -e/);
+assert.match(rootReadme, /console\.log\(JSON\.parse\(r\.result\.content\[0\]\.text\)\.gateStatus\)/);
 
 const requests = [
   { jsonrpc: '2.0', id: 1, method: 'initialize', params: {} },