io.github.Optisol-Business/db-metadata-extractor-mcp
OCI · DOCKER.IO/OPTISOLBUSINESSSOL/DB-METADATA-EXTRACTOR-MCP:0.1.6 · 2 COMPONENTS · SCANNED AUG 3
Extract database metadata from PostgreSQL, Snowflake, SQL Server, BigQuery, and Oracle.
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 →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency-health data not yet available.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 108 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability49
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 746 tokens (~373/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
oci · docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6
claude mcp add optisol-business-db-metadata-extractor-mcp -- docker run --rm -i docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6
codex mcp add optisol-business-db-metadata-extractor-mcp -- docker run --rm -i docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"optisol-business-db-metadata-extractor-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6"
],
"enabled": true
}
}
} mcp_servers:
optisol-business-db-metadata-extractor-mcp:
command: "docker"
args: ["run", "--rm", "-i", "docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6"] {
"mcpServers": {
"optisol-business-db-metadata-extractor-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 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 Jul 26 30
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 3 Aug 2026 · Analysed oci/docker.io/optisolbusinesssol/db-metadata-extractor-mcp:0.1.6
Provenance none
Ecosystem: oci · Outcome: none
Reason: no_attestation
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.
extract_metadata ~563
Extract schema metadata from a live database and save the full JSON to a local folder. Returns a lightweight summary (never the full JSON). The output_path MUST be an absolute directory path where the JSON file will be written. If the directory does not exist it will be created. Args: db_type: Database type — one of: 'postgres', 'snowflake', 'sqlserver', 'bigquery', 'oracle' output_path: Absolute directory path to save the extracted JSON. Example: /Users/you/project/outputs or C:\Users\you\project\outputs database_name: Database / catalog name host: Hostname or IP (postgres, sqlserver, oracle) port: Port number (postgres=5432, sqlserver=1433, oracle=1521) username: Login username password: Login password schema_name: Schema to extract (postgres default 'public', sqlserver default 'dbo') tables: Optional list of table names to limit extraction account: Snowflake account identifier warehouse: Snowflake warehouse name role_name: Snowflake role name project_id: BigQuery GCP project ID service_account_key: BigQuery service-account JSON key (as string) Example — PostgreSQL: { "db_type": "postgres", "output_path": "/home/user/metadata_output", "host": "10.0.0.5", "port": 5432, "username": "admin", "password": "secret", "database_name": "mydb", "schema_name": "public" } Example — Oracle: { "db_type": "oracle", "output_path": "C:\\metadata_output", "host": "20.168.23.183", "port": 152…
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | — | — |
| database_name | string | — | — |
| db_type | string | yes | — |
| host | string | — | — |
| output_path | string | yes | — |
| password | string | — | — |
| port | integer | — | — |
| project_id | string | — | — |
| role_name | string | — | — |
| schema_name | string | — | — |
| service_account_key | string | — | — |
| tables | — | — | — |
| username | string | — | — |
| warehouse | string | — | — |
No output schema declared.
No examples provided.
query_metadata ~139
Query a previously-saved metadata JSON file on disk without loading everything into context. Args: filepath: Absolute path to the JSON file saved by extract_metadata table_name: Filter by table name (substring match, optional) field_name: Filter by column/field name (substring match, optional) page: Page number (default 1) page_size: Records per page (default 20)
| Name | Type | Req | Description |
|---|---|---|---|
| field_name | string | — | — |
| filepath | string | yes | — |
| page | integer | — | — |
| page_size | integer | — | — |
| table_name | string | — | — |
No output schema declared.
No examples provided.