raindrop-rules

A set of development rules for building a Raindrop.io integration with the Model Context Protocol (MCP), including API references, debugging guidance, and Vitest testing. Raindrop.io is a service for saving and organising web bookmarks.

In plain words
What is it for?
Use it when developing, debugging, testing, or expanding the Raindrop.io MCP server and its API coverage.
Why use it?
It points the agent to the relevant documentation and testing approach instead of relying on incomplete assumptions.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/kazuph/mcp-raindrop/raindrop-rules
Clone the repo
git clone --depth 1 https://github.com/kazuph/mcp-raindrop

Made for: Cursor.

Per session 200 This file is loaded in full into every session.
When invoked 200 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin fork From a forked repository.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00200 $0.00200
Opus 5 $0.00100 $0.00100
Sonnet 5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

Measured yesterday against content hash ef5bbf7b07ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

raindrop-rules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/raindrop-rules.mdc · 16 lines

What it actually says

Refer to Raindrop.io API for API documentation. Refer to https://modelcontextprotocol.io/ Learn this: Model Context Protocol with LLMs Refer to https://github.com/modelcontextprotocol/typescript-sdk for mcp sdk example MCP servers repository is here https://github.com/modelcontextprotocol/servers with implementation examples.

MCP Debugging Instructions I am using the Inspeector and https://github.com/modelcontextprotocol/inspector is the repository for it. ensure API coverage is complete. I am using Vitest for testing

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 16 lines · 200 tokens per session scan A ef5bbf7b07ca

Subscribe to this mod's changes

raindrop-rules is a cursor rule published in the GitHub repository kazuph/mcp-raindrop (0 stars, last pushed 7mo ago), licensed MIT. It adds 200 tokens to every session, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.