payhero-mcp-server@0.2.0
VERIFIED· startup onlyPublisher claims: "MCP server for the PayHero payroll API" 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
PAYHERO_AUTH_URLPAYHERO_CLIENT_SECRETPAYHERO_HTTP_BEARER_TOKENConfiguration, not credentials: PAYHERO_API_URL, PAYHERO_CLIENT_ID, PAYHERO_COMPANY_CODE, PAYHERO_HTTP_ALLOWED_HOSTS, PAYHERO_HTTP_ALLOWED_ORIGINS, PAYHERO_HTTP_HOST, PAYHERO_HTTP_MAX_BODY_BYTES, PAYHERO_HTTP_PORT, PAYHERO_READWRITE, PAYHERO_TRANSPORT- Where it talks to
- no vendor host named in the codeAlso payhero.co.nz — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names payhero.co.nz as well as its own vendor. The guard injects PAYHERO_AUTH_URL, PAYHERO_CLIENT_SECRET, PAYHERO_HTTP_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-19 and scored it 91/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 · 26 s · 2 scenarios · 0 deviationsStatic findings
".env.example"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.No other findings across 619 lines in 18 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 @teamnetwork-nz/payhero-mcp-server@0.2.0 as of 12 h ago. This is the package itself, not its dependencies.