pgvector-mcp-server@1.0.6
VERIFIED· not startedPublisher claims: "Model Context Protocol server for PostgreSQL vector database management with pgvector extension" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
DASHSCOPE_API_KEYDATABASE_URLConfiguration, not credentials: DASHSCOPE_BASE_URL- Where it talks to
- no vendor host named in the codeAlso aliyuncs.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names aliyuncs.com as well as its own vendor. The guard injects DASHSCOPE_API_KEY, DATABASE_URL only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 82/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
- `DEBUG`: Enable debug mode (default: false)Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.result = subprocess.run(cmd, cwd=Path(__file__).parent.parent)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.binary_content = b'\x00\x01\x02\x03\xff\xfe\xfd'Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.rm -f /tmp/manual_additions_$$Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.rm -f /tmp/agent_update_*_$$Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- Set DASHSCOPE_API_KEY in .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Create `.env` file in project root for environment variables:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.binary_content = b'\xff\xfe\x48\x00\x65\x00\x6c\x00\x6c\x00\x6f\x00' # UTF-16 LEFix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for pgvector-mcp-server@1.0.6 as of 2 h ago. This is the package itself, not its dependencies.