@bicharts/chart-mcp 0.6.89 → 0.6.91
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/README.md +3 -1
- package/dist/check-chart.mjs +94 -94
- package/dist/index.mjs +85 -85
- package/package.json +3 -3
- package/skills/bic-charts/SKILL.md +26 -15
package/README.md
CHANGED
|
@@ -270,7 +270,7 @@ else:
|
|
|
270
270
|
There's no usage counter: the service counts calls from the requests it receives.
|
|
271
271
|
`assess_data_shape` never sends anything - it profiles your data locally, telemetry on or off.
|
|
272
272
|
|
|
273
|
-
Set `BIC_MCP_TELEMETRY=0` in the server's environment to turn all three off.
|
|
273
|
+
Set `BIC_MCP_TELEMETRY=0` (`false`, `off` and `no` work too, in any case) in the server's environment to turn all three off.
|
|
274
274
|
|
|
275
275
|
Three other things leave your machine, none of them telemetry:
|
|
276
276
|
|
|
@@ -310,6 +310,8 @@ and `GET /healthz`. What's different from the local server:
|
|
|
310
310
|
- **Each request it sends says it came from the hosted server,** and an `X-BIC-Client-IP` header on the incoming
|
|
311
311
|
request is passed on, so the service's limits apply to the person rather than to the server. Run it yourself only
|
|
312
312
|
behind something that checks callers, since it trusts that header.
|
|
313
|
+
- **The service records the names of the arguments each tool call passes, never their values:** which settings
|
|
314
|
+
agents use, counted without reading what anyone asked for. The local server sends nothing of the kind.
|
|
313
315
|
|
|
314
316
|
## The agent skill (recommended)
|
|
315
317
|
|