@fidacy/mcp 0.5.1 → 0.6.0
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 +14 -0
- package/dist/core.js +1 -1
- package/dist/index.js +612 -452
- package/dist/lib.js +3 -3
- package/dist/nudges.d.ts +1 -1
- package/dist/postinstall.d.ts +2 -0
- package/dist/postinstall.js +255 -0
- package/dist/register.d.ts +28 -3
- package/dist/setup.d.ts +27 -0
- package/package.json +3 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.6.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- Ask for the operator's email in the terminal, at install time. `npm i @fidacy/mcp` now prompts for it right after install, and `npx @fidacy/mcp setup` runs the same prompt on demand. The address registers immediately, so the install is identified from the first moment rather than anonymous until someone stumbles onto a claim link.
|
|
8
|
+
|
|
9
|
+
The prompt only appears when a human is actually there. Under `npx -y` (how MCP hosts launch the server), inside Docker builds, in CI, or with piped input, it exits instantly and silently — an install script that waits for input does not fail, it hangs forever, taking the host or the pipeline with it. `FIDACY_NONINTERACTIVE=1` forces that behaviour for anyone scripting installs. It also never fails an install: any error leaves exit code 0, because a firewall that refuses to install over a prompt is worse than one that never asked. If the network is down when you answer, the address is kept on disk and registers on the next start.
|
|
10
|
+
|
|
11
|
+
## 0.5.2
|
|
12
|
+
|
|
13
|
+
### Patch Changes
|
|
14
|
+
|
|
15
|
+
- Move the one-time setup ask onto a channel the model actually receives. 0.5.1 put it in the MCP handshake `instructions`, which turns out to reach nobody on Claude Code — asked directly, a live agent there answered "NO INSTRUCTIONS VISIBLE", because that host does not pass server instructions to the model. Tool results do arrive (that is how the block attribution and the activation wall get through), so the ask now rides the first payment decision instead: once per install, only while no email is on record, and explicitly telling the agent to drop it for good if the operator would rather not.
|
|
16
|
+
|
|
3
17
|
## 0.5.1
|
|
4
18
|
|
|
5
19
|
### Patch Changes
|
package/dist/core.js
CHANGED
|
@@ -488,7 +488,7 @@ function resolveMandateRules(cfg) {
|
|
|
488
488
|
}
|
|
489
489
|
|
|
490
490
|
// src/telemetry.ts
|
|
491
|
-
var CLIENT_VERSION = true ? "0.
|
|
491
|
+
var CLIENT_VERSION = true ? "0.6.0" : "dev";
|
|
492
492
|
function bandOf(amount) {
|
|
493
493
|
if (typeof amount !== "number" || !Number.isFinite(amount) || amount <= 0) return void 0;
|
|
494
494
|
if (amount < 10) return "lt10";
|