promptready-mcp@0.4.0
VERIFIED· not startedPublisher claims: "MCP server (stdio) for PromptReady — convert PDF/CSV to Markdown from AI agents." 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
PROMPTREADY_ACCESS_TOKENPROMPTREADY_CREDENTIALS_PATHPROMPTREADY_REFRESH_TOKENConfiguration, not credentials: PROMPTREADY_BASE_URL, PROMPTREADY_SETTINGS_PATH- Where it talks to
- promptready.space (its own)
- 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. It asks for PROMPTREADY_ACCESS_TOKEN, PROMPTREADY_CREDENTIALS_PATH, PROMPTREADY_REFRESH_TOKEN and talks to promptready.space. 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; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 85/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
Tokens are stored via token_store (chmod 600) and applied to the environment.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.<summary>Email login fallback</summary> If browser-based Google login is not an option, the same command accepts email and password: ```bash promptready-mcp-logFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.print(" credentials saved (chmod 600).", flush=True)Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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 promptready-mcp@0.4.0 as of 35 min ago. This is the package itself, not its dependencies.