Borrowing it
Nothing to install: this file belongs to adeze/raindrop-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adeze/raindrop-mcp/master/.github/skills/mcp-testing/SKILL.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/skills/adeze/raindrop-mcp/mcp-testing)<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/mcp-testing"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/mcp-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/mcp-testing"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/mcp-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00017 | $0.01531 |
| Opus 5.5 | $0.00007 | $0.00612 |
| Sonnet 5.5 | $0.00003 | $0.00306 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
mcp-testing 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 1mo 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Testing Skill
Modern testing strategies for Model Context Protocol (MCP) servers developed in VS Code using TypeScript, Bun, and Vitest.
Unit Testing with Vitest & In-Memory Transport
Setup Minimal Test Environment
import { describe, it, expect, beforeEach } from "vitest";
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { InMemoryTransport } from "@modelcontextprotocol/sdk/testing/inMemoryTransport.js";
import { RaindropMCPService } from "../src/services/raindropmcp.service.js";
describe("RaindropMCPService Tools", () => {
let service: RaindropMCPService;
let transport: InMemoryTransport;
let client: Client;
beforeEach(async () => {
service = new RaindropMCPService();
transport = new InMemoryTransport(service.getServer());
client = new Client(
{
name: "test-client",
version: "1.0.0",
},
{ capabilities: {} },
);
await client.connect(transport);
});
it("should list available tools", async () => {
const tools = await client.listTools();
expect(tools.tools.length).toBeGreaterThan(0);
expect(tools.tools.map((t) => t.name)).toContain("collection_list");
});
it("should call a tool with valid input", async () => {
const result = await client.callTool({
name: "collection_list",
arguments: {},
});
expect(result).toBeDefined();
expect(result.content).toBeDefined();
});
});
Key Testing Patterns
- In-Memory Transport: Use for unit tests—no subprocess overhead, direct method invocation
- Server Capabilities: Verify manifest before running tool tests
- Mock Context: Provide mock
RaindropServicefor isolated tool testing - Error Handling: Test both success and error paths with Zod validation
Integration Testing with MCP Inspector
Launch Inspector in VS Code
- Terminal > Run Task > "Debug HTTP Server with Inspector" (or STDIO variant)
- Opens Inspector at
http://localhost:3000(or via auto-opened browser) - Live tool/resource exploration with bidirectional message capture
- Opens Inspector at
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.
- 1mo ago First seen · 245 lines · 17 tokens per session scan A 5c1fd6b0b4fd
mcp-testing is a skill published in the GitHub repository adeze/raindrop-mcp (189 stars, last pushed 10d ago), licensed MIT. It adds 17 tokens to every session and 1,531 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
test-generator
Generate comprehensive unit, integration, and end-to-end tests. Use when adding test coverage, writing tests for new features, or improving existing test suites.
testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.
generate-e2e-tests
Walk a flow in the browser and write end-to-end tests (Playwright, Cypress, etc.) that reproduce it. Use when asked to create e2e coverage for a user flow.
smoke-test
Smoke-test a user flow end to end in a browser (login, checkout, signup, etc.) and verify the expected result. Use when asked to walk through a flow and confirm it still works.
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
testing-strategies
Use when writing tests, setting up test frameworks, implementing mocking strategies, or establishing testing best practices (unit, integration, E2E) across any technology stack.