DBConvert Streams (Federated SQL)
OCI · DOCKER.IO/SLOTIX/STREAM-MCP:2.7.3 · 3 COMPONENTS · SCANNED SEP 20
Read-only SQL across your PostgreSQL, MySQL, S3 buckets and local data files, in one query.
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 392 tokens (~196/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
How do I install the DBConvert Streams (Federated SQL) MCP server?
DBConvert Streams (Federated SQL) runs locally as a container image, launched with docker run --rm -i docker.io/slotix/stream-mcp:2.7.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/slotix/stream-mcp:2.7.3
claude mcp add com-dbconvert-streams -- docker run --rm -i docker.io/slotix/stream-mcp:2.7.3
{
"mcpServers": {
"com-dbconvert-streams": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/slotix/stream-mcp:2.7.3"
]
}
}
} {
"servers": {
"com-dbconvert-streams": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/slotix/stream-mcp:2.7.3"
]
}
}
} codex mcp add com-dbconvert-streams -- docker run --rm -i docker.io/slotix/stream-mcp:2.7.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dbconvert-streams": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"docker.io/slotix/stream-mcp:2.7.3"
],
"enabled": true
}
}
} mcp_servers:
com-dbconvert-streams:
command: "docker"
args: ["run", "--rm", "-i", "docker.io/slotix/stream-mcp:2.7.3"] {
"McpServers": {
"com-dbconvert-streams": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"docker.io/slotix/stream-mcp:2.7.3"
]
}
}
} {
"mcpServers": {
"com-dbconvert-streams": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/slotix/stream-mcp:2.7.3"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 31 Aug 26 39
First indexed and scored.
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 20 Sept 2026 · Analysed oci/docker.io/slotix/stream-mcp:2.7.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
dbconvert_get_connection ~95
Get credential-free details for one connection: host, port, username, default database, SSL/SSH topology, cloud provider. Passwords, SSH private keys, and cloud access keys/tokens are never included — they are structurally absent, not redacted, so there is no way to retrieve them through MCP. Report only the fields present in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| connectionId | string | yes | Stored DBConvert connection ID |
| Name | Type | Req | Description |
|---|---|---|---|
| cloudProvider | string | – | – |
| created | integer | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| spec | null|object | – | – |
| ssh | null|object | – | – |
| ssl | null|object | – | – |
| type | string | yes | – |
No examples provided.
dbconvert_list_data_sources ~103
List DBConvert Streams connections. Each item has exactly id, name, type, and (optionally) cloudProvider — nothing else. For host/port/username and other connection details use get_connection. Passwords and cloud keys are never exposed by any tool. Report connections using only the fields present; do not add invented fields like used_for or row_counts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum items to return, default 100, max 500 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | null|array | yes | – |
| limitApplied | integer | yes | – |
| truncated | boolean | yes | – |
No examples provided.
What is the DBConvert Streams (Federated SQL) MCP server?
DBConvert Streams (Federated SQL) is an MCP server listed in the public MCP registry as com.dbconvert/streams. Read-only SQL across your PostgreSQL, MySQL, S3 buckets and local data files, in one query. This page covers its container image (docker.io/slotix/stream-mcp:2.7.3).
Is the DBConvert Streams (Federated SQL) MCP server safe to use?
DBConvert Streams (Federated SQL) scores 48 out of 100 on VerifyMCP. 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 DBConvert Streams (Federated SQL) MCP server expose?
DBConvert Streams (Federated SQL) exposes 2 tools: dbconvert_get_connection, dbconvert_list_data_sources. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded.
Is the DBConvert Streams (Federated SQL) MCP server still maintained?
DBConvert Streams (Federated SQL) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.