open-mcp-server@1.0.9
VERIFIED· startup onlyPublisher claims: "alipay openplatform mcp server" 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
- Needs
- --appPrivateKey, --appAuthToken — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
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
AP_INVOKE_AUTH_TOKENConfiguration, not credentials: AP_APP_ID, AP_APP_KEY, AP_CURRENT_ENV, AP_LOG_ENABLED, SSE_URL, X_TOOLS_DEFAULT_VAL- Where it talks to
- alipaydev.com, alipay.com (its own)
- What we saw when it ran
- 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. It asks for AP_INVOKE_AUTH_TOKEN and talks to alipaydev.com, alipay.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-19 and scored it 89/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 (it asks for --appPrivateKey, --appAuthToken); 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 · 37 s · 2 scenarios · 0 deviationsStatic findings
"inspector:prod": "npx @modelcontextprotocol/inspector $(grep -v '^#' .env | grep -v '^$' | sed 's/^\\(.*\\)=\\(.*\\)/-e \\1=\\2/' | tr '\\n' ' ') npx @alipay/open-mcp-server",Fix: Pin versions and sources; vendor anything fetched at install time."inspector:prod": "npx @modelcontextprotocol/inspector $(grep -v '^#' .env | grep -v '^$' | sed 's/^\\(.*\\)=\\(.*\\)/-e \\1=\\2/' | tr '\\n' ' ') npx @alipay/open-mcp-server",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."inspector": "npm run build && npx @modelcontextprotocol/inspector $(grep -v '^#' .env | grep -v '^$' | sed 's/^\\(.*\\)=\\(.*\\)/-e \\1=\\2/' | tr '\\n' ' ') node dist/index.js",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 @alipay/open-mcp-server@1.0.9 as of 14 h ago. This is the package itself, not its dependencies.