mcp-databnf 2.1.0 → 2.1.2
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 +18 -0
- package/README.md +4 -4
- package/dist/bnf/client.js +1 -1
- package/dist/bnf/client.js.map +1 -1
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/server.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 2.1.2
|
|
4
|
+
|
|
5
|
+
- **Every tool is documented, with its arguments and what its answer carries.**
|
|
6
|
+
The README is written for a person deciding whether to install and for a
|
|
7
|
+
program installing on its own, and a test holds both halves to what the server
|
|
8
|
+
registers.
|
|
9
|
+
- **The privacy policy travels in the package.** It states the hosts contacted,
|
|
10
|
+
what a request carries, what is held and for how long.
|
|
11
|
+
- **The manifest names every tool the server registers**, which a host reads
|
|
12
|
+
before installing anything.
|
|
13
|
+
|
|
14
|
+
## 2.1.1
|
|
15
|
+
|
|
16
|
+
- **The bundle builds again.** The manifest carried an argument schema on each
|
|
17
|
+
tool, which the packer refuses: a tool is a name and a description. Nothing
|
|
18
|
+
the npm package holds changed, and 2.1.0 reached npm without a bundle or a
|
|
19
|
+
release beside it.
|
|
20
|
+
|
|
3
21
|
## 2.1.0
|
|
4
22
|
|
|
5
23
|
- **The client entry point publishes `parseEntityId` and the `EntityId` type.**
|
package/README.md
CHANGED
|
@@ -60,7 +60,7 @@ Node 24 or later is required, and no environment variable has to be set.
|
|
|
60
60
|
"mcpServers": {
|
|
61
61
|
"databnf": {
|
|
62
62
|
"command": "docker",
|
|
63
|
-
"args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-databnf:2.1.
|
|
63
|
+
"args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-databnf:2.1.2"]
|
|
64
64
|
}
|
|
65
65
|
}
|
|
66
66
|
}
|
|
@@ -72,7 +72,7 @@ because a TTY rewrites the stream. The container needs outbound HTTPS to
|
|
|
72
72
|
|
|
73
73
|
### Bundle, without npm
|
|
74
74
|
|
|
75
|
-
Download `mcp-databnf-2.1.
|
|
75
|
+
Download `mcp-databnf-2.1.2.mcpb` from
|
|
76
76
|
[the latest release](https://github.com/smeet666/mcp-databnf/releases/latest) and
|
|
77
77
|
open it. A client that supports MCP bundles installs it on its own, with no npm
|
|
78
78
|
and no configuration file to edit. The bundle carries its dependencies, so
|
|
@@ -384,7 +384,7 @@ renseigner.
|
|
|
384
384
|
"mcpServers": {
|
|
385
385
|
"databnf": {
|
|
386
386
|
"command": "docker",
|
|
387
|
-
"args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-databnf:2.1.
|
|
387
|
+
"args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-databnf:2.1.2"]
|
|
388
388
|
}
|
|
389
389
|
}
|
|
390
390
|
}
|
|
@@ -397,7 +397,7 @@ identifiant.
|
|
|
397
397
|
|
|
398
398
|
### Bundle, sans npm
|
|
399
399
|
|
|
400
|
-
Téléchargez `mcp-databnf-2.1.
|
|
400
|
+
Téléchargez `mcp-databnf-2.1.2.mcpb` depuis
|
|
401
401
|
[la dernière publication](https://github.com/smeet666/mcp-databnf/releases/latest)
|
|
402
402
|
et ouvrez-le. Un client qui gère les bundles MCP l'installe seul, sans npm et
|
|
403
403
|
sans fichier de configuration à modifier. Le bundle emporte ses dépendances, donc
|