io.github.dbsectrainer/mcp-data-pipeline-connector
NPM · MCP-DATA-PIPELINE-CONNECTOR
Universal data connector for CSV, Postgres, and REST APIs via DuckDB
Available components
Last scanned (1 day ago)
Scores higher than 30% of npm servers
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security48
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 37 of 122 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 527 tokens (~75/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +16
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 1.0.0 → 1.0.1 functional
- 12 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Security disclosure: pass → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Security disclosure: unverified → pass ▲ functional
- 20 Aug 26 0
- Security disclosure: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/mcp-data-pipeline-connector@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Deprecated | 1 |
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_health ~36
Check whether registered data sources are still reachable and responsive.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | Optional: name of a specific source to health-check |
No output schema declared.
No examples provided.
connect_source ~120
Register a data source (CSV file, Postgres database, or REST API). Credentials must be in environment variables or a YAML config file — never pass connection strings directly.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Unique name for this data source |
| path | string | – | File path for CSV/JSON sources |
| source_config_path | string | – | Path to a YAML config file. If provided, all sources in the file are registered. |
| type | string | yes | Type of the data source |
| url | string | – | Base URL for REST API sources |
No output schema declared.
No examples provided.
get_schema ~45
Return the column names and types for a specific table.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | Name of the source that contains the table |
| table | string | yes | Name of the table |
No output schema declared.
No examples provided.
list_sources ~18
List all registered data sources and their connection status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tables ~39
List available tables across all sources, or just the named source.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | Optional: name of a specific source to list tables for |
No output schema declared.
No examples provided.
query ~181
Execute a SQL query against a registered data source using DuckDB. Returns up to --max-rows rows (default 1000). In read-only mode (default), only SELECT statements are allowed. Use source='_all' to query across all CSV sources with cross-source joins. Supports limit and offset for pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of rows to return (pagination) |
| max_rows | number | – | Override the default max row limit for this query |
| offset | number | – | Number of rows to skip before returning results (pagination) |
| source | string | – | Name of the source to query, or '_all' for cross-source joins. Required if multiple sources are registered. |
| sources | array | – | Array of source names for cross-source queries (alternative to source='_all') |
| sql | string | yes | The SQL query to execute |
No output schema declared.
No examples provided.
transform ~88
Apply aggregations, filters, renaming, or column selection to a source table and return or save results.
| Name | Type | Req | Description |
|---|---|---|---|
| operations | array | yes | List of transform operations to apply in order |
| output_format | string | – | Output format (default: json) |
| source | string | yes | Name of the data source to transform |
| table | string | yes | Name of the table within the source to transform |
No output schema declared.
No examples provided.
How do I install the io.github.dbsectrainer/mcp-data-pipeline-connector server?
io.github.dbsectrainer/mcp-data-pipeline-connector runs locally as an npm package, launched with npx -y mcp-data-pipeline-connector. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-data-pipeline-connector
claude mcp add dbsectrainer-mcp-data-pipeline-connector -- npx -y mcp-data-pipeline-connector
What is the io.github.dbsectrainer/mcp-data-pipeline-connector server?
io.github.dbsectrainer/mcp-data-pipeline-connector is listed in the public MCP registry as io.github.dbsectrainer/mcp-data-pipeline-connector. Universal data connector for CSV, Postgres, and REST APIs via DuckDB. This page covers its npm package (mcp-data-pipeline-connector).
Is the io.github.dbsectrainer/mcp-data-pipeline-connector server safe to use?
io.github.dbsectrainer/mcp-data-pipeline-connector scores 55 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.dbsectrainer/mcp-data-pipeline-connector server expose?
io.github.dbsectrainer/mcp-data-pipeline-connector exposes 7 tools: connect_source, list_sources, list_tables, get_schema, query, and 2 more. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Is the io.github.dbsectrainer/mcp-data-pipeline-connector server still maintained?
io.github.dbsectrainer/mcp-data-pipeline-connector is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.dbsectrainer/mcp-data-pipeline-connector server under?
io.github.dbsectrainer/mcp-data-pipeline-connector declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.