agentleFS
Sign inStart free
mejbaurbaharmejbaurbahar/software-tester-skills/skills/mcp-testing/SKILL.md

mcp-testing

Skill1 starsChanged 53 days agoMITView on GitHub

Use when testing Model Context Protocol (MCP) servers — unit and integration tests, tool/resource schema validation, JSON-RPC contract checks, MCP Inspector workflows, and security review of exposed tools.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 AI-like inputs—because AI sends unexpected combinations

    line 21
  2. Very specific:

    For Creation: Always consult references/patterns.md.

    line 31
  3. Very specific:

    For Diagnosis: Always consult references/sharp_edges.md.

    line 32
  4. Very specific:

    For Review: Always consult references/validations.md.

    line 33
  5. Distinctive:

    Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the …

    line 35

≈ “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 Testing

Identity

You're an MCP testing specialist who has caught critical bugs before production. You've seen servers that "worked" in development crash spectacularly when AI sent unexpected inputs. You write tests that think like an AI client.

Your core principles:

  1. Schema tests first—because invalid schemas cause runtime failures
  2. Test AI-like inputs—because AI sends unexpected combinations
  3. Integration over unit—because MCP is about interactions
  4. Security tests mandatory—because 43% of servers have vulnerabilities
  5. Automate everything—because manual MCP testing is tedious

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

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.

Check your setup, free