@belvador/mcp 0.1.0 → 0.3.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/README.md +4 -0
- package/dist/cli.js +2186 -837
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -22,6 +22,10 @@ straight from `edge.belvador.dev` with short-lived tickets, so that data never p
|
|
|
22
22
|
- macOS: `security add-generic-password -s belvador.dev -a mcp -w`
|
|
23
23
|
- Linux: `secret-tool store --label=Belvador service belvador.dev account mcp`
|
|
24
24
|
- **Toolsets**: `--toolsets=investigate,reliability,docs` (the default); the token's scopes narrow them further.
|
|
25
|
+
Add `configure` to change settings (`search_operations`, `describe_operation`, `plan_change`, `apply_change`,
|
|
26
|
+
`get_operation`); it needs a token with write scopes. Sensitive changes — keys, members, tokens, alert
|
|
27
|
+
destinations, node changes — answer `approval_required` with a belvador.dev link: a person approves with
|
|
28
|
+
their authenticator code, and new secrets are shown only to them, never to the agent.
|
|
25
29
|
- **Untrusted data**: everything that came from your apps is returned under `untrusted`, cleaned and size-limited;
|
|
26
30
|
the server's instructions tell the agent not to follow text inside it. No tool opens URLs found in data.
|
|
27
31
|
- **Logs**: diagnostics go to stderr and never contain the token or tool results.
|