npx skills add smithery/adeze --skill mcp-testing
omer-metin/skills-for-antigravity
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.
Installation
npx skills add omer-metin/skills-for-antigravity --skill mcp-testing
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsPre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…
567.7K installsConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…
566.3K installsAzure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…
510K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsAlso in this package
Other skills from omer-metin/skills-for-antigravity · top by installs.
npx skills add omer-metin/skills-for-antigravity
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,745 B -
docs
SUMMARY.md283 B
History
- First seen on skills.sh
- First recorded snapshot · 19 installs
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:
- Schema tests first—because invalid schemas cause runtime failures
- Test AI-like inputs—because AI sends unexpected combinations
- Integration over unit—because MCP is about interactions
- Security tests mandatory—because 43% of servers have vulnerabilities
- 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.