@miraigent/free-ai-ops-mcp 0.1.32 → 0.1.34

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [0.1.34] - 2026-07-09
+
+### Changed
+
+- Added a README version-check command so npm and GitHub users can confirm the
+  public registry version before debugging local npx or desktop MCP client
+  cache behavior.
+
+## [0.1.33] - 2026-07-08
+
+### Changed
+
+- Added a minimal README parsing example that shows MCP users how to read the
+  JSON tool result from `content[0].text` before wiring the package into a
+  desktop client or private workflow.
+
 ## [0.1.32] - 2026-07-07
 
 ### Added

package/README.md

@@ -55,6 +55,14 @@ If you are checking the package from npm search, run the public help first:
 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.
 
+If a local npx cache or desktop MCP client appears stale, compare it with the
+public registry version before changing private client configuration:
+
+    npm view @miraigent/free-ai-ops-mcp version
+
+The version printed by `npm view` should match the version shown in the package
+help output and in the MCP `initialize` response.
+
 If the result is unclear, open a Tried It feedback issue with synthetic input
 only. A useful issue can be as small as:
 
@@ -136,6 +144,26 @@ files.
 After the smoke test runs, look for the status field from the tool you called
 before changing client configuration or private workflows.
 
+In raw JSON-RPC output, MCP wraps each tool result inside `content[0].text`.
+Parse that text value as JSON before you check the returned decision:
+
+    const response = JSON.parse(lineFromStdout);
+    const toolResult = JSON.parse(response.result.content[0].text);
+    console.log(toolResult.gateStatus);
+
+For the bundled smoke-test session, that prints `stop`. Use the parsed
+`gateStatus`, `recommendation`, or `recommendedStatus` field from the relevant
+tool before changing a desktop MCP client config or connecting private data.
+
+If you only need a terminal check, you can copy the final JSON-RPC line from the
+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>'
+
+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.
+
 For `human_review_gate`:
 
 - `auto_ok`: the synthetic draft looks low risk, but the tool still does not

package/package.json

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