Individual skill

mcp-testing

Testing strategies for MCP servers including unit tests, integration tests, schema validation, and security testingUse when "mcp testing, test mcp server, mcp inspector, mcp validation, mcp, testing, unit-testing, integration-testing, schema-validation" mentioned.

skills/mcp-testing/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 206
Repository last updated: Jan 22, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
antigravity Repository topic
antigravity-ide Repository topic
skills Repository topic
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,745 bytes
SKILL.mdcore · 1,745 bytes
references/patterns.mddoc · 5,493 bytes
references/sharp_edges.mddoc · 5,295 bytes
references/validations.mddoc · 1,692 bytes

Read excerpt


# 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