@miraigent/free-ai-ops-mcp 0.1.22 → 0.1.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +8 -0
- package/README.md +32 -0
- package/mcp/free-ai-ops-server.mjs +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.1.23] - 2026-06-24
|
|
4
|
+
|
|
5
|
+
### Changed
|
|
6
|
+
|
|
7
|
+
- Added README guidance for reading returned MCP status fields so npm and
|
|
8
|
+
GitHub users can choose the next safe action before changing client config or
|
|
9
|
+
connecting private workflows.
|
|
10
|
+
|
|
3
11
|
## [0.1.22] - 2026-06-22
|
|
4
12
|
|
|
5
13
|
### Changed
|
package/README.md
CHANGED
|
@@ -120,6 +120,38 @@ you ran, the public-safe input shape, and the returned status field. Do not
|
|
|
120
120
|
paste private customer records, secrets, internal policy text, or paid product
|
|
121
121
|
files.
|
|
122
122
|
|
|
123
|
+
## Read The Returned Status
|
|
124
|
+
|
|
125
|
+
After the smoke test runs, look for the status field from the tool you called
|
|
126
|
+
before changing client configuration or private workflows.
|
|
127
|
+
|
|
128
|
+
For `human_review_gate`:
|
|
129
|
+
|
|
130
|
+
- `auto_ok`: the synthetic draft looks low risk, but the tool still does not
|
|
131
|
+
send anything.
|
|
132
|
+
- `review_required`: keep a human reviewer in the workflow before sending.
|
|
133
|
+
- `stop`: pause the workflow and resolve the sensitive, payment, complaint,
|
|
134
|
+
privacy, public-facing, or policy issue first.
|
|
135
|
+
|
|
136
|
+
For `prompt_risk_review`:
|
|
137
|
+
|
|
138
|
+
- `review_checklist_required`: document the data-handling checklist before
|
|
139
|
+
running the prompt.
|
|
140
|
+
- `human_review_required`: add a human review step before AI output can affect a
|
|
141
|
+
customer-facing workflow.
|
|
142
|
+
- `stop_before_ai_use`: do not run the prompt until the data-handling rule is
|
|
143
|
+
reviewed.
|
|
144
|
+
|
|
145
|
+
For `faq_candidate_review`, use `recommendedStatus` to decide whether the
|
|
146
|
+
pattern belongs in a public FAQ, internal FAQ, or human-review rule. For
|
|
147
|
+
`ai_safe_crm_note`, check that facts, AI suggestions, human decisions, and next
|
|
148
|
+
actions stay in separate fields.
|
|
149
|
+
|
|
150
|
+
If the status is surprising, open a Tried It feedback issue with synthetic input
|
|
151
|
+
only. The most useful report says which status you expected, which status you
|
|
152
|
+
received, and what extra rule or explanation would have made the result easier
|
|
153
|
+
to use.
|
|
154
|
+
|
|
123
155
|
## Copy A Useful Feedback Result
|
|
124
156
|
|
|
125
157
|
When you open a Tried It feedback issue, the most useful report is the smallest
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@miraigent/free-ai-ops-mcp",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.23",
|
|
4
4
|
"description": "Free MCP server for developers adding human review gates, prompt risk checks, FAQ review, and CRM note safety to AI tools.",
|
|
5
5
|
"homepage": "https://github.com/Miraigent/miraigent-free-ai-ops-mcp",
|
|
6
6
|
"type": "module",
|