agentleFS
docdyhrdocdyhr/simplenote-mcp-server/.claude/skills/mcp-release-qa/SKILL.md

mcp-release-qa

Skill21 starsChanged 27 days agoMITView on GitHub

Verify an MCP server before release by exercising a real protocol session, comparing runtime capabilities with source and documentation, testing failure paths, and recording reproducible evidence. Use when shipping or reviewing an MCP server, tool, resource, prompt, catalog, or install path.

2 other projects use a version of this, 1 of them edited; 1 new project in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 15 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test the server that users will run.

    line 8
  2. Distinctive:

    Run checks against a fresh server process built from the candidate revision.

    line 17
  3. Very specific:

    Keep initialize, notifications/initialized, discovery, and invocation in the same session.

    line 18
  4. Distinctive:

    Treat source registrations as implementation truth and public documentation as a contract that must match it.

    line 20
  5. Distinctive:

    Do not invoke mutation-capable tools against production data.

    line 24
  6. Very specific:

    Prefer repository-native commands.

    line 40
  7. Distinctive:

    If the server cannot start from its documented instructions, report that as a release failure and preserve the startup error verbatim.

    line 59
  8. Distinctive:

    Run this sequence through a real MCP client or the repository's integration harness:

    line 64
  9. Distinctive:

    Call each supported discovery method:

    line 71
  10. Distinctive:

    Follow pagination until no cursor remains when a list method is paginated.

    line 78
  11. Distinctive:

    Do not send post-initialization requests through separate one-shot processes.

    line 80
  12. Distinctive:

    Verify that each response has the correct request ID, a useful error message, and no successful side effect.

    line 146
  13. Distinctive:

    When the project publishes an install command:

    line 153
  14. Distinctive:

    Create a temporary destination outside the source checkout.

    line 155
  15. Distinctive:

    Run the public install command exactly as documented.

    line 156
  16. Distinctive:

    Start the installed artifact without relying on files from the source tree.

    line 157
  17. Distinctive:

    Remove the temporary destination after preserving the command output.

    line 159
  18. Very specific:

    Use FAIL for a server that cannot start, complete a valid session, keep the transport parseable, or safely reject invalid input.

    line 195

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

If the server cannot start from its documented instructions, report that as a release failure and preserve the startup error verbatim.

3. Exercise one complete session

Run this sequence through a real MCP client or the repository's integration harness:

  1. initialize with a protocol version the server claims to support.
  2. Confirm the negotiated version and advertised capabilities.
  3. Send notifications/initialized.
  4. Call ping.
  5. Call each supported discovery method:
    • tools/list
    • resources/list
    • resources/templates/list
    • prompts/list
  6. Exercise at least one representative read-only item from every advertised capability class.
  7. Follow pagination until no cursor remains when a list method is paginated.

Do not send post-initialization requests through separate one-shot processes. That accidentally tests several incomplete sessions instead of one valid session.

4. Prove inventory parity

Build four inventories from current evidence:

SurfaceEvidence
SourceRegistered tool, resource, template, and prompt definitions
RuntimeResults from the live discovery methods
Generated metadataCatalogs, manifests, or generated indexes
DocumentationREADME, reference pages, and install output

Compare by stable identifier. Report:

  • source entries missing at runtime;
  • runtime entries absent from metadata or documentation;
  • stale names, descriptions, arguments, URIs, or prompt parameters;
  • documented install commands that do not start the candidate server.

Regenerate derived files with the repository's own build command, then fail if the working tree still contains unexplained generated changes.

5. Check published contracts

For every discovered item, verify the runtime definition against its source:

Tools

  • Name and description are stable and specific.
  • inputSchema defines types, required fields, enums, and bounds where needed.
  • Unknown properties are rejected when the tool contract is closed.
  • Mutation, idempotence, read-only, and open-world annotations match behavior.
  • Successful calls conform to outputSchema when one is published.
  • Errors are protocol errors or structured tool failures, not leaked stack traces.

Resources and templates

  • URIs and MIME types match the registered definitions.
  • Static resources are readable.
  • Template parameters are validated before resolution.
  • Missing or forbidden resources fail explicitly.

Prompts

  • Required and optional arguments match discovery output.
  • prompts/get returns usable messages for valid arguments.
  • Missing required arguments and unknown prompt names fail explicitly.

6. Test failure paths

At minimum, probe:

  • a request before initialization completes;
  • malformed JSON or an invalid JSON-RPC envelope;
  • an unknown method;
  • an unsupported protocol version;
  • repeated initialization;
  • unknown tool, resource, and prompt names;
  • missing, extra, wrong-type, and out-of-bounds arguments;
  • a request at the documented transport-size limit and one beyond it;
  • a controlled internal failure with credentials and stack traces redacted.

Verify that each response has the correct request ID, a useful error message, and no successful side effect. For STDIO, also confirm every stdout line is a complete protocol message and a healthy session leaves stderr clean unless the server explicitly documents diagnostic output.

7. Smoke-test installation

When the project publishes an install command:

  1. Create a temporary destination outside the source checkout.
  2. Run the public install command exactly as documented.
  3. Start the installed artifact without relying on files from the source tree.
  4. Repeat initialization, discovery, and one read-only invocation.
  5. Remove the temporary destination after preserving the command output.

An install string that was only inspected is unverified.

8. Report the evidence

Use this format:

# MCP Release QA

Candidate: [commit]
Transport: [STDIO | Streamable HTTP | SSE]
Verdict: PASS | PASS WITH CAVEATS | FAIL

## Commands and results
- `[exact command]` — [exit status and result]

## Session transcript
- initialize: [result]
- discovery: [result]
- representative calls: [result]
- negative paths: [result]

## Parity
| Identifier | Source | Runtime | Metadata | Docs | Result |
|---|---|---|---|---|---|

## Findings
| Severity | Evidence | Impact | Narrowest fix |
|---|---|---|---|

## Missing evidence
- [check that could not run and why]

Use FAIL for a server that cannot start, complete a valid session, keep the transport parseable, or safely reject invalid input. Use PASS WITH CAVEATS only for bounded documentation or metadata drift that does not misrepresent a dangerous capability. Otherwise use PASS.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.