vizier-mcp-proxy@0.5.17
VERIFIED· startup onlyPublisher claims: "Deterministic authorization proxy for MCP (Model Context Protocol) servers and AI agents." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
VIZIER_API_KEYVIZIER_PROXY_CLIENT_TOKENVIZIER_PROXY_UPSTREAM_BEARER_TOKENor--upstream-tokenConfiguration, not credentials: VIZIER_BASE_URL, VIZIER_PROXY_AGENT_ID, VIZIER_PROXY_AGENT_OWNER, VIZIER_PROXY_ALLOWED_TOOLS, VIZIER_PROXY_GRANT_FILE, VIZIER_PROXY_GRANT_MODE, VIZIER_PROXY_HOST, VIZIER_PROXY_INTEGRATION_ID, VIZIER_PROXY_PORT, VIZIER_PROXY_PRINCIPAL_ID, VIZIER_PROXY_UPSTREAM_ID, VIZIER_PROXY_UPSTREAM_URL- Where it talks to
- no vendor host named in the codeAlso dpdns.org — 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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names dpdns.org as well as its own vendor. The guard injects VIZIER_API_KEY, VIZIER_PROXY_CLIENT_TOKEN, VIZIER_PROXY_UPSTREAM_BEARER_TOKEN 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; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 93/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 · 23 s · 2 scenarios · 0 deviationsStatic findings
No findings across 1,027 lines in 7 files.
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 @agenda-intelligence/vizier-mcp-proxy@0.5.17 as of 10 h ago. This is the package itself, not its dependencies.