@vespermcp/mcp-server 1.2.26 → 1.2.28
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 +43 -0
- package/build/index.js +904 -4
- package/build/metadata/semantic-scholar-source.js +64 -11
- package/build/python/normalize_schema_engine.py +224 -0
- package/build/web/fusion-engine.js +3 -0
- package/build/web/web-core.js +2 -0
- package/package.json +6 -1
- package/src/python/normalize_schema_engine.py +224 -0
package/README.md
CHANGED
|
@@ -88,6 +88,47 @@ Vesper attempts to auto-configure itself! Restart Claude and check. If not:
|
|
|
88
88
|
|
|
89
89
|
- `KAGGLE_USERNAME` & `KAGGLE_KEY`: For Kaggle dataset access
|
|
90
90
|
- `HF_TOKEN`: For private HuggingFace datasets
|
|
91
|
+
- `VESPER_TELEMETRY_ENDPOINT`: Optional HTTP endpoint for lineage telemetry events (`lineage.version.appended`)
|
|
92
|
+
|
|
93
|
+
### Telemetry Transparency (Opt-in)
|
|
94
|
+
|
|
95
|
+
Vesper does **not** send telemetry unless `VESPER_TELEMETRY_ENDPOINT` is explicitly set.
|
|
96
|
+
|
|
97
|
+
When enabled, Vesper sends only lineage event metadata on version append:
|
|
98
|
+
- dataset base/version IDs
|
|
99
|
+
- tool name + actor metadata (`agent_id`, `pipeline_id` when provided)
|
|
100
|
+
- basic output metadata (`local_path`, rows/columns, format)
|
|
101
|
+
- timestamp + host name
|
|
102
|
+
|
|
103
|
+
It does **not** upload dataset file contents.
|
|
104
|
+
|
|
105
|
+
### Lineage Receiver (for web dashboard backend)
|
|
106
|
+
|
|
107
|
+
Vesper includes a tiny ingestion server for lineage telemetry events:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
npm run telemetry:receiver
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
Storage backends:
|
|
114
|
+
- **Postgres**: set `DATABASE_URL`
|
|
115
|
+
- **SQLite**: set `SQLITE_PATH` (for lightweight/local deployments)
|
|
116
|
+
|
|
117
|
+
Optional env vars:
|
|
118
|
+
- `PORT` (default `8787`)
|
|
119
|
+
- `LINEAGE_INGEST_PATH` (default `/vesper/lineage`)
|
|
120
|
+
|
|
121
|
+
Example for hosted backend:
|
|
122
|
+
- ingest URL: `https://getvesper.dev/vesper/lineage`
|
|
123
|
+
- client env: `VESPER_TELEMETRY_ENDPOINT=https://getvesper.dev/vesper/lineage`
|
|
124
|
+
|
|
125
|
+
DDL files:
|
|
126
|
+
- `telemetry/sql/lineage_events.postgres.sql`
|
|
127
|
+
- `telemetry/sql/lineage_events.sqlite.sql`
|
|
128
|
+
|
|
129
|
+
Stats endpoint for web dashboard bootstrap:
|
|
130
|
+
- `GET /vesper/lineage/stats?days=30`
|
|
131
|
+
- Returns JSON: overview, by-tool counts, by-day counts, top datasets, recent activity.
|
|
91
132
|
|
|
92
133
|
### Optional Kaggle Setup (Not Required)
|
|
93
134
|
|
|
@@ -121,6 +162,8 @@ vespermcp discover --source kaggle "credit risk" --limit 10
|
|
|
121
162
|
vespermcp discover --source huggingface "credit risk" --limit 10
|
|
122
163
|
vespermcp download kaggle username/dataset-name
|
|
123
164
|
vespermcp download kaggle https://www.kaggle.com/datasets/username/dataset-name --target-dir ./data
|
|
165
|
+
vespermcp status
|
|
166
|
+
vespermcp status --dir ./some/project --max-depth 3
|
|
124
167
|
```
|
|
125
168
|
|
|
126
169
|
## 🚀 Quick Start
|