Why this verdict
- inconclusive: gap no_tools_extracted at goldbean-mcp-v2/server.json
Security findings 0
No individual findings recorded
The inconclusive verdict rests on the coverage gaps below; 2 candidate findings were refuted on review.
Refuted findings 2
Candidates the review stage examined and rejected, kept for transparency.
Data exfiltration
criticalRefutedlow confidenceThe tools/call handler POSTs all caller-supplied tool arguments (images of ID cards, passports, faces, audio, documents) to an API base that GOLDBEAN_API_URL can override, so sensitive user data goes to a third-party host; this is the declared proxy function, and no hidden credential or file access exists.
const resp = await fetch(`${API_BASE}/mcp`, {Why it was refuted
Forwarding tool arguments to the GoldBean endpoint is the server's declared core purpose as an API proxy. The code reads no files and attaches no hidden credentials, so this is not exfiltration.
Privilege escalation
mediumRefutedlow confidenceThe optional HTTP mode listens on 0.0.0.0 with wildcard CORS and no authentication, so any network host or web page can use the local proxy to forward requests to the remote API.
server.listen(port, "0.0.0.0", () => {Why it was refuted
No privilege is escalated. The proxy attaches no credentials, only content-type and protocol headers, so a caller of the open listener gets nothing beyond what the public remote API already offers. The HTTP mode is optional and openly labeled as a transport.
Coverage gaps 1
Parts of the artifact the static analysis could not fully examine.
no_tools_extracted MCP server target with no statically extractable tools/prompts/resources
goldbean-mcp-v2/server.json
