@veilio-inc/mcp 0.3.1 → 0.3.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/README.md +47 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -15,6 +15,7 @@ tools/call anonymize_file { "path": "src/gateway.ts" }
|
|
|
15
15
|
Language: TypeScript / JavaScript
|
|
16
16
|
Placeholders in map: 7
|
|
17
17
|
Namespace: local
|
|
18
|
+
Custom rules: none
|
|
18
19
|
Credentials detected — 1 critical:
|
|
19
20
|
critical line 2:24 Stripe secret key — sk_l…MNOP (31 chars) (redacted, not recoverable)
|
|
20
21
|
|
|
@@ -27,13 +28,19 @@ tools/call anonymize_file { "path": "src/gateway.ts" }
|
|
|
27
28
|
}
|
|
28
29
|
```
|
|
29
30
|
|
|
31
|
+
Two more lines appear when they apply, and both are the model's only warning
|
|
32
|
+
that the masking did not cover something: one when no language marker matched
|
|
33
|
+
(the file was masked as TypeScript, which may be wrong), and one counting the
|
|
34
|
+
**comment prose left exactly as written** — names and ticket numbers in comments
|
|
35
|
+
are still real.
|
|
36
|
+
|
|
30
37
|
## Tools
|
|
31
38
|
|
|
32
39
|
| Tool | Purpose |
|
|
33
40
|
|---|---|
|
|
34
41
|
| `anonymize_file` | Read a file and return only its masked form. **Preferred.** |
|
|
35
42
|
| `anonymize_text` | Mask text the agent already holds (a user paste). Not for file contents. |
|
|
36
|
-
| `restore_text` | Swap placeholders back and strip AI-generated noise. |
|
|
43
|
+
| `restore_text` | Swap placeholders back and strip AI-generated noise — the team's placeholders too, under the rule below. |
|
|
37
44
|
| `scan_secrets` | Detect credentials without modifying anything, and without putting the values in context. |
|
|
38
45
|
| `symbol_map_summary` | Placeholder counts by kind. Returns keys only, never real names. |
|
|
39
46
|
|
|
@@ -53,16 +60,18 @@ Setup for Claude Code, Claude Desktop, Xcode, Cursor and VS Code, plus troublesh
|
|
|
53
60
|
}
|
|
54
61
|
```
|
|
55
62
|
|
|
56
|
-
`--root <dir>` scopes every path the server will read; `--map <path>` overrides the symbol-map location. Paths outside the root are refused — the server reads files on the agent's behalf, so traversal would make it an arbitrary-file-read primitive.
|
|
63
|
+
`--root <dir>` (or `-r`) scopes every path the server will read; `--map <path>` (or `-m`) overrides the symbol-map location. Paths outside the root are refused — the server reads files on the agent's behalf, so traversal would make it an arbitrary-file-read primitive.
|
|
57
64
|
|
|
58
65
|
## Team namespace (Team plan and above)
|
|
59
66
|
|
|
60
67
|
Sign in once with the `veilio` CLI — `veilio login` — and every anonymize
|
|
61
68
|
result from this server states which namespace produced its placeholders:
|
|
62
69
|
|
|
63
|
-
- **`team`** — resolved against the team's shared dictionary,
|
|
64
|
-
|
|
65
|
-
|
|
70
|
+
- **`team`** — resolved against the team's shared dictionary, read at startup,
|
|
71
|
+
so every teammate's agent produces the same placeholder for the same
|
|
72
|
+
identifier. Reused for the life of the process, with one exception: run
|
|
73
|
+
`veilio team unlock` after the server started and the next call says it is
|
|
74
|
+
loading the team's maps rather than making you restart the agent.
|
|
66
75
|
- **`local`** — resolved locally: not signed in, no team key unlocked on this
|
|
67
76
|
machine, offline, or the plan doesn't include shared dictionaries. This is the
|
|
68
77
|
normal, fully-functional state for anyone not on a paid team — the server never
|
|
@@ -81,11 +90,44 @@ whole reports `local` too, because a namespace missing a teammate's newest map
|
|
|
81
90
|
would restore their placeholders wrong. An older self-hosted Cloud that still
|
|
82
91
|
merges server-side is honoured as it is, with no key needed here.
|
|
83
92
|
|
|
93
|
+
The `local` line says which of those it was — `local (the team key is locked on
|
|
94
|
+
this machine - run \`veilio team unlock\`)` or `local (could not read the team's
|
|
95
|
+
maps: …)` — so a fallback is never read as agreement.
|
|
96
|
+
|
|
84
97
|
The account's custom rules are fetched at startup the same way and applied to
|
|
85
98
|
every anonymize call. Each result states their source: `from Cloud`, `cached`
|
|
86
99
|
(Cloud did not answer, so the last `veilio rules pull` is used, with its age),
|
|
87
100
|
or `none`.
|
|
88
101
|
|
|
102
|
+
### One restore rule, and what the server refuses to guess
|
|
103
|
+
|
|
104
|
+
`restore_text` resolves the team's maps first — aliases included — and this
|
|
105
|
+
project's map on top of them. Two kinds of placeholder are deliberately left in
|
|
106
|
+
the output, each named in a warning rather than substituted:
|
|
107
|
+
|
|
108
|
+
- one this project's store and the team use for **different** identifiers, and
|
|
109
|
+
- one this project **numbered on its own** while the team was out of reach.
|
|
110
|
+
|
|
111
|
+
Either could be restored to a name that is not the one a teammate meant, and a
|
|
112
|
+
confident wrong identifier is worse than a token the reader can see is
|
|
113
|
+
unresolved. They are also excluded from the "invented or altered" count, since
|
|
114
|
+
they were left for a stated reason.
|
|
115
|
+
|
|
116
|
+
When the team's maps *should* have been used and could not be — the key is
|
|
117
|
+
locked, or Cloud could not be read — the call comes back as an **error result**
|
|
118
|
+
saying which, even if some placeholders did restore. An older self-hosted Cloud
|
|
119
|
+
that merges the namespace server-side is used for anonymizing but never for
|
|
120
|
+
restoring: it cannot tell a disputed placeholder from a first-written one.
|
|
121
|
+
|
|
122
|
+
### After a lapse
|
|
123
|
+
|
|
124
|
+
Anonymizing while signed out, or while Cloud was unreachable, numbers new names
|
|
125
|
+
locally. Once the team's maps are back, an identifier the team already knows
|
|
126
|
+
takes the **team's** placeholder, and anything new is numbered above both the
|
|
127
|
+
team's highest and this project's own. The entries minted during the lapse stay
|
|
128
|
+
in the local store — text was already sent with them, so they are still needed
|
|
129
|
+
to restore it — but they are not handed to a teammate as the team's meaning.
|
|
130
|
+
|
|
89
131
|
## Design properties
|
|
90
132
|
|
|
91
133
|
- **Zero runtime dependencies.** JSON-RPC framing is implemented directly. Pulling a transitive tree into the component that reads your source would undercut the product's own claim.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@veilio-inc/mcp",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.2",
|
|
4
4
|
"description": "MCP server exposing the anonymizer to coding agents, so a model can work on masked code without the real identifiers ever entering its context.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -28,7 +28,7 @@
|
|
|
28
28
|
"license": "SEE LICENSE IN LICENSE",
|
|
29
29
|
"dependencies": {
|
|
30
30
|
"@veilio-inc/engine": "^1.7.0",
|
|
31
|
-
"@veilio-inc/cli": "^0.3.
|
|
31
|
+
"@veilio-inc/cli": "^0.3.2"
|
|
32
32
|
},
|
|
33
33
|
"scripts": {
|
|
34
34
|
"build": "tsc",
|