mcp-verify

Verify MCP tools against a running server via inspector and JSON-RPC calls.

5|1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill mcp-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-verify
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/mcp-verify
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill mcp-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying MCP tool behavior and tool interactions can be error-prone when using ad-hoc methods; this skill provides a structured approach to inspect, invoke, and validate MCP server tools.

Core Features & Use Cases

  • MCP Inspector offers a web UI for interactive tool testing.
  • Direct Tool Invocation demonstrates programmatic tool calls via the MCP protocol.
  • Session Options enable locking to specific profiles and environments for reliable reproduction.
  • Response Validation ensures outputs conform to expected formats and error messages are meaningful.
  • Common Failure Modes helps diagnose issues like missing active profiles or forbidden environments.

Quick Start

Run the MCP Inspector against the server, then invoke a tool with the provided JSON-RPC commands.

Frequently Asked Questions about mcp-verify

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

FAQPage Schema
How do I verify MCP tool behavior against a running server?

To verify MCP tools, run the MCP Inspector against your running MCP server and invoke tools using JSON-RPC commands. This structured approach replaces ad-hoc testing by validating behavior across both interactive inspector sessions and direct programmatic tool calls.

What is the best way to test JSON-RPC tool calls in a guarded environment?

Testing JSON-RPC tool calls in a guarded environment requires using session options to lock to specific profiles. This session locking ensures reliable reproduction of tool invocations and validates that tooling correctly supports guarded environments.

How do I validate MCP server responses and ensure errors are descriptive?

Validating MCP server responses involves checking that outputs conform to expected formats and error messages are meaningful. Response validation ensures well-formed outputs by testing behavior across both interactive inspector sessions and direct programmatic tool invocations.

Why does my MCP Inspector tool invocation fail with missing active profiles?

MCP Inspector tool invocation fails with missing active profiles because session options require a locked profile for reliable reproduction. This common failure mode occurs when tooling lacks the necessary environment configuration to execute guarded JSON-RPC tool calls.

Can I use direct tool invocation instead of the MCP Inspector web UI for testing?

Yes, direct tool invocation demonstrates programmatic tool calls via the MCP protocol as an alternative to the MCP Inspector web UI. Both methods validate tool behavior, but direct invocation tests JSON-RPC calls without relying on interactive web UI sessions.