Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/dist/tools/db.js b/dist/tools/db.js
--- a/dist/tools/db.js
+++ b/dist/tools/db.js
@@ -12,1 +12,0 @@
-const { resolveDatabaseTunnel, requestDatabaseProxyToken, resolveDatabaseControlPlaneDomain } = dbRequire('../../vendor/db-tunnel.js');
@@ -315,1 +314,0 @@
-mutation CreateDatabaseProxyToken(
@@ -320,1 +318,0 @@
-createDatabaseProxyToken(where: $where, ttlMinutes: $ttlMinutes, accessMode: $accessMode) {
@@ -397,1 +394,0 @@
-return 'Scaly could not mint a database proxy token in time. Retry; if it persists, run scaly_doctor and contact support with the resource ID.';
@@ -425,1 +421,0 @@
-const data = await requestDatabaseProxyToken((query, variables) => (0, client_js_1.oidcQuery)(query, variables), CREATE_DB_PROXY_TOKEN, {

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.71. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: mcp-server: Credential pass-through configuration (KillerSkills verdict caution 70)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 70/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/mcp-server/0.1.71

## Findings with a location
- `dist/tools/db.js:425` · Credential pass-through configuration — dist/tools/db.js:425 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/tools/db.js:397` · Credential pass-through configuration — dist/tools/db.js:397 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/tools/db.js:315` · Credential pass-through configuration — dist/tools/db.js:315 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/tools/db.js:12` · Credential pass-through configuration — dist/tools/db.js:12 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/tools/db.js:320` · Credential pass-through configuration — dist/tools/db.js:320 · Credential pass-through configuration — agent relays sensitive credentials

## Proposed change
The attached patch removes the 5 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._