Parse Connection String

Overview

You pass a JDBC URL or database URI and we return a safe structural summary: driver, host, port, database name, and non-secret options. Passwords are stripped structurally — they never appear in the response, even when present in the input. We do not open a connection or resolve hostnames. Do not use this when you need a live connectivity or authentication check.

Agents and tools often echo connection strings into logs — and passwords go with them. We give you structure without that risk.

When to use it

Scope

Non-goals

• Does not connect to the database
• Does not resolve or ping hostnames
• Does not return passwords or usernames
• Does not validate that credentials work

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"database.parse_connection_string","input":{"connectionString":"jdbc:postgresql://localhost:5432/app"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("database.parse_connection_string", {"connectionString":"jdbc:postgresql://user:[email protected]:5432/appdb?sslmode=require"});

Errors

Other limits

Limitations

• Does not connect to the database
• Does not resolve or ping hostnames
• Does not return passwords or usernames
• Does not validate that credentials work
• Live connectivity or authentication checks
• Secret rotation or credential validation

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "database.parse_connection_string",
  "input": {
    "connectionString": "jdbc:postgresql://user:[email protected]:5432/appdb?sslmode=require"
  }
}

Examples

{
  "connectionString": "jdbc:postgresql://user:[email protected]:5432/appdb?sslmode=require"
}

{
  "scheme": "jdbc:postgresql",
  "hasUsername": true,
  "findings": [
    {
      "details": {},
      "path": "/options/sslmode",
      "code": "CONNSTRING_TLS_NO_VERIFICATION",
      "message": "sslmode=require encrypts but does not verify the server certificate.",
      "severity": "warning"
    }
  ],
  "database": "appdb",
  "_meta": {
    "optionCount": 1,
    "redactedOptionCount": 0
  },
  "safeUri": "jdbc:postgresql://db.internal:5432/appdb?sslmode=require",
  "driver": "postgresql",
  "tls": {
    "requested": true,
    "verifiesCertificate": false,
    "mode": "require"
  },
  "hasPassword": true,
  "options": {
    "sslmode": "require"
  },
  "host": "db.internal",
  "port": 5432
}

{
  "connectionString": "jdbc:mysql://localhost:3306/billing"
}

{
  "scheme": "jdbc:mysql",
  "hasUsername": false,
  "findings": [],
  "database": "billing",
  "_meta": {
    "optionCount": 0,
    "redactedOptionCount": 0
  },
  "safeUri": "jdbc:mysql://localhost:3306/billing",
  "driver": "mysql",
  "tls": {
    "requested": false,
    "verifiesCertificate": false,
    "mode": "none"
  },
  "hasPassword": false,
  "options": {},
  "host": "localhost",
  "port": 3306
}

Recommended use cases

• Review a connection string before storing it in config
• Build a safe inventory of database endpoints
• Check TLS settings without leaking secrets into logs

Avoid for

• Live connectivity or authentication checks
• Secret rotation or credential validation

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags