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.
npx agentmods add instructions/adeze/raindrop-mcp/gemini-mdgit clone --depth 1 https://github.com/adeze/raindrop-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/adeze/raindrop-mcp/gemini-md)<a href="https://agentmods.dev/instructions/adeze/raindrop-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/adeze/raindrop-mcp/gemini-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01175 | $0.01175 |
| Opus 5 | $0.00588 | $0.00588 |
| Sonnet 5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
raindrop-mcp GEMINI.md 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 4d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Raindrop MCP Server - Project Context
Project Overview
This project is a Model Context Protocol (MCP) server for Raindrop.io, a bookmark management service. It allows AI assistants (like Claude or Gemini) to interact with a user's Raindrop bookmarks, collections, tags, and highlights using natural language.
The server supports both STDIO (standard input/output) and HTTP/SSE (Server-Sent Events) transports, making it compatible with various MCP clients including Claude Desktop and custom integrations.
Core Technologies
- Runtime: Bun (primary) / Node.js
- Language: TypeScript
- Frameworks:
@modelcontextprotocol/sdk: For MCP protocol implementation.zod: For input/output schema validation.express/node:http: For the HTTP/SSE transport layer.axios/openapi-fetch: For Raindrop.io API communication.
- Testing:
bun test(Vitest compatible)
Architecture
The project follows a modular service-oriented architecture:
- Entry Points:
src/index.ts: Main entry point for the STDIO transport server.src/server.ts: Entry point for the HTTP/SSE server with session management and OAuth support.
- Core Service (
src/services/raindropmcp.service.ts):- Manages the
McpServerinstance. - Registers tools, resources, and prompts.
- Handles dynamic resource resolution.
- Manages the
- API Service (
src/services/raindrop.service.ts):- Encapsulates direct communication with the Raindrop.io API.
- Handles authentication (Access Token or OAuth).
- Tools (
src/tools/):- Modular tool definitions using
defineTool. - Categories:
bookmarks,collections,tags,highlights,diagnostics,bulk.
- Modular tool definitions using
- Resources:
- Dynamic resources for individual bookmarks (
mcp://raindrop/{id}) and collections (mcp://collection/{id}). - Static resources for user profile and server diagnostics.
- Dynamic resources for individual bookmarks (
- Prompts:
- Built-in prompts for complex workflows like "organize_by_topic" or "find_duplicates".
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.
- 4d ago First seen · 119 lines · 1,175 tokens per session scan A 46f7d22ff5c9
raindrop-mcp GEMINI.md is an instructions file published in the GitHub repository adeze/raindrop-mcp (183 stars, last pushed 1mo ago), licensed MIT. It adds 1,175 tokens to every session, about $0.0059 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
mcp AGENTS.md
AGENTS.md instructions for Teamwork/mcp, covering agents.md, this repository is public, project overview, setup commands and build and run.
mcpscore AGENTS.md
Instructions for mcp-box/mcpscore, covering agent instructions for mcpscore and gotchas (learned the hard way).
obsidian-vault-mcp CLAUDE.md
Claude Code instructions for ebullient/obsidian-vault-mcp, covering obsidian vault mcp, code style and qa.
slivingdoc AGENTS.md
AGENTS.md instructions for baalimago/slivingdoc, covering agents.md — slivingdoc, architecture, package map, event flow and startup wiring (main.go).
Orbiads-GAM-MCP AGENTS.md
Instructions for OrbiAds/Orbiads-GAM-MCP, covering orbiads — ai agent instructions, quick reference, connect, mcp server (recommended for chat agents) and cli (recommended for scripts / ci / headless).
pixabay-mcp-server CLAUDE.md
Claude Code instructions for hanoak/pixabay-mcp-server, covering claude.md, project overview, tech stack (decided — do not relitigate without discussion), architecture & folder conventions and coding standards.