raindrop-mcp@0.2.4
VERIFIED· not startedPublisher claims: "Raindrop instrumentation for Python MCP servers: one event per turn, one tool span per call, for any FastMCP / MCPServer." 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
RAINDROP_API_KEYConfiguration, not credentials: MCP_E2E_DEBUG, MCP_E2E_USER, RAINDROP_ENDPOINT, RAINDROP_PROJECT_ID, RAINDROP_WRITE_KEY- Where it talks to
- raindrop.ai (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 RAINDROP_API_KEY and talks to raindrop.ai. 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 90/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
conn.incoming(_req(1, "resources/read", {"uri": "https://u:pw@host/a?token=secret#frag"}))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose._redact_url_secrets("see https://bob:p@[email protected]/v1?token=abc&q=cats&X-Amz-Signature=s1#frag")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert _redact_url_secrets("see https://user:p@[email protected]/x?sig=abc&page=2") == "see https://[REDACTED]@h.test/x?sig=[REDACTED]&page=2"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.args = {"url": "https://u:[email protected]/x?api_key=abcdefghijklmnop"}Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.conn.outgoing(_err(1, -32002, "Unknown resource: https://u:pw@host/a?token=secret#frag"))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.secret_url = "https://bob:hunter2@host/x?api_key=k1&q=cats"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 raindrop-mcp@0.2.4 as of 55 min ago. This is the package itself, not its dependencies.