simplenote-mcp-server: Skill for Claude Code

.claude/skills/mcp-release-qa/SKILL.md

mcp-release-qa is a skill for Claude Code from docdyhr/simplenote-mcp-server. It costs 58 tokens per session (1,465 once invoked), scanned A, a copy of mcp-release-qa, MIT.

A release-testing workflow for an MCP server that exercises a real protocol session and compares its runtime behavior with its source code and public documentation.

In plain words
What is it for?
Use it before release to test initialization, discovery, tool or resource behavior, transports, failure paths, and reproducible evidence in a sandbox or fixture environment.
Why use it?
It catches differences between what the server claims to provide and what users can actually discover or invoke; a unit test is not proof that the running protocol works.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is docdyhr/simplenote-mcp-server's own configuration. It tells Claude Code how to work on simplenote-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything simplenote-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to docdyhr/simplenote-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/docdyhr/simplenote-mcp-server/main/.claude/skills/mcp-release-qa/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/docdyhr/simplenote-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for mcp-release-qa

README.md
[![agentmods](https://agentmods.dev/badge/skills/docdyhr/simplenote-mcp-server/mcp-release-qa/github.svg)](https://agentmods.dev/skills/docdyhr/simplenote-mcp-server/mcp-release-qa)
Your own site
<a href="https://agentmods.dev/skills/docdyhr/simplenote-mcp-server/mcp-release-qa"><img src="https://agentmods.dev/badge/skills/docdyhr/simplenote-mcp-server/mcp-release-qa/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.

agentmods 80×15 button for mcp-release-qa

Your own site · 80×15
<a href="https://agentmods.dev/skills/docdyhr/simplenote-mcp-server/mcp-release-qa"><img src="https://agentmods.dev/badge/skills/docdyhr/simplenote-mcp-server/mcp-release-qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
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.1 $0.00058 $0.01465
Opus 5.5 $0.00023 $0.00586
Sonnet 5.5 $0.00012 $0.00293
Haiku 4.5 $0.00006 $0.00146

Measured yesterday against content hash 36b5a18d8dde, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-release-qa 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.

Origin

This is a copy

100% identical to mcp-release-qa — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/mcp-release-qa/SKILL.md · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Release QA

Test the server that users will run. A schema review or a passing unit test is not runtime evidence.

This skill complements security review. It focuses on protocol behavior, published-contract drift, transport correctness, and reproducible release evidence.

Rules

  • Run checks against a fresh server process built from the candidate revision.
  • Keep initialize, notifications/initialized, discovery, and invocation in the same session. A new process is a new STDIO session.
  • Treat source registrations as implementation truth and public documentation as a contract that must match it.
  • Record exact commands and raw responses. Do not replace missing evidence with "looks correct."
  • Do not invoke mutation-capable tools against production data. Use fixtures, a sandbox, or stop and name the missing safe test environment.
  • Derive the expected capability inventory from the candidate source on every run.

1. Establish the release surface

Identify:

  • candidate commit and build command;
  • server entry point and transport: STDIO, Streamable HTTP, or SSE;
  • supported MCP protocol versions;
  • source files that register tools, resources, resource templates, and prompts;
  • generated catalogs, manifests, README tables, and install instructions;
  • existing protocol, integration, and smoke-test commands.

Prefer repository-native commands. Inspect package.json, pyproject.toml, Makefile, CI workflows, and contributor instructions before inventing a test harness.

2. Start a clean server

Build the candidate and start the documented entry point with test-safe configuration. Capture:

  • the exact command;
  • commit SHA;
  • environment variable names, with values redacted;
  • stdout, stderr, and exit status;
  • the endpoint or child-process transport used by the client.

For STDIO, stdout is protocol-only. Logs, banners, and stack traces belong on stderr. For HTTP transports, record the status, relevant MCP headers, and session identifier handling without printing credentials.

Read the full file on GitHub · 199 lines

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 · 199 lines · 58 tokens per session scan A 36b5a18d8dde

Subscribe to this mod's changes

mcp-release-qa is a skill published in the GitHub repository docdyhr/simplenote-mcp-server (21 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,465 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-release-qa, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories