mcp-tester

Test and evaluate MCP server tools through discovery, quality analysis, and structured test execution.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill mcp-tester-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tester
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/mcp-tester
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill mcp-tester-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? MCP server tools often ship with unclear descriptions, weak schemas, and untested error paths, making it hard to know whether they will behave correctly in a Claude Code session. This Skill provides a systematic six-phase workflow to audit, test, and rate every MCP tool available in the current session. ## Core Features & Use Cases - Tool Discovery & Inventory: Lists all tools with the mcp__ prefix, groups them by server, and reports parameter counts and description previews. - Quality Analysis: Scores naming conventions, description quality, and parameter efficiency with severity indicators (critical, warning, suggestion). - AAA Test Generation & Execution: Creates Arrange-Act-Assert test cases covering happy paths, invalid inputs, and edge cases, with mandatory confirmation before running mutating tools. - Cross-Tool Analysis: Detects redundant tools, consolidation opportunities, and missing CRUD capabilities across servers. - Use Case: After adding a new MCP server, ask for a full audit to receive a report rating each tool, flagging a silent failure on wrong-type input, and recommending enum constraints for free-text parameters. ## Quick Start Ask the assistant to test all MCP tools in the current session and generate a full quality report.

Frequently Asked Questions about mcp-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test MCP server tools in Claude Code?

Invoke the testing workflow to discover all tools with the mcp__ prefix, grouped by server. The process generates test cases per tool, executes read-only tools directly, asks confirmation for mutating tools, and produces a rated report.

What makes a good MCP tool description?

A good description explains what the tool does, when to use it, and includes example scenarios and edge cases. Descriptions are scored from Excellent to Poor, with verbose descriptions flagged when token cost outweighs the information conveyed.

Can I test MCP tools outside a Claude Code session?

Yes, use the MCP Inspector via npx @modelcontextprotocol/inspector for standalone testing. It provides an interactive UI for tool calling, schema validation display, and request/response inspection against stdio or HTTP servers.

Why do MCP tool tests pass locally but fail against the real server?

Mocks often diverge from real server behavior in response size, error format, latency, and schema keys. Run integration tests against the actual MCP server with realistic fixtures and verify error paths, not just happy paths.

What are the limitations of testing MCP tools this way?

Only tools configured in the current session can be tested, and no direct HTTP requests are made to server URLs. Tools requiring interactive mid-flow authentication cannot be tested, and response time measurements are approximate.