mcp-pavoot@0.7.23
VERIFIED· not startedPublisher claims: "MCP server that exposes the Pavoot event-planning API" 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
PAVOOT_API_KEYPYPI_API_TOKENConfiguration, not credentials: PAVOOT_API_URL, PAVOOT_APP_URL- Where it talks to
- pavoot.com (its own)Also whatwg.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
- 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 whatwg.org as well as its own vendor. The guard injects PAVOOT_API_KEY, PYPI_API_TOKEN only into requests to pavoot.com (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-08 and scored it 87/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
# Reads PYPI_API_TOKEN from .env (or the environment). Uploads the versionFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.load_dotenv(_HERE.parent.parent / ".env", override=False)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [[ -f .env ]]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo " 2) Paste it into mcp-pavoot/.env as PYPI_API_TOKEN=pypi-..."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load `.env` from the MCP folder itself so users can keep config alongsideFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.source .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# ── Load .env (if present) without exporting unrelated vars ─────────────────Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- running from an empty directory, so a relative `.env` resolves toFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""The suite must never load `.env` — see conftest.py."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Keep the test run away from `.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."in mcp-pavoot/.env."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.(`get_app_page_link('mailbox')`), and a platform-wide kill switch canFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.settings read `.env` from the working directory — so merely importing theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."mcp_pavoot was imported before the dotenv stub — .env may have been read"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`mcp_pavoot.http` calls `load_dotenv(<repo>/.env)` at import, and MCPServer'sFix: 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 mcp-pavoot@0.7.23 as of 6d ago. This is the package itself, not its dependencies.