mcp-inspector-verify

Validate MCP tool contracts, UI interactions, and D1 database persistence for CalDAV integrations.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/gigun-dev/caldav --skill mcp-inspector-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-inspector-verify
Source: https://github.com/gigun-dev/caldav/tree/main/.claude/skills/mcp-inspector-verify
Command: npx skills add https://github.com/gigun-dev/caldav --skill mcp-inspector-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of verifying complex MCP (Model Context Protocol) integrations by providing a structured, multi-layered E2E testing framework that validates server responses, UI interactions, and database persistence.

Core Features & Use Cases

  • Multi-Layer Validation: Verifies tool contracts, UI card interactions, and raw D1 database state.
  • OAuth & Security Testing: Ensures OAuth principals and scopes are correctly maintained across tool calls and app interactions.
  • Use Case: Use this when you need to confirm that a new CalDAV tool correctly updates the remote D1 database and that the corresponding MCP App UI reflects these changes accurately without manual database inspection.

Quick Start

Use the mcp-inspector-verify skill to perform an end-to-end validation of the CalDAV MCP server and its associated UI components.

Frequently Asked Questions about mcp-inspector-verify

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

FAQPage Schema
How do I verify CalDAV MCP tool contracts and UI interactions end-to-end?

End-to-end CalDAV MCP verification validates tool contracts, UI card interactions, and D1 database persistence using the Model Context Protocol inspector and Wrangler CLI. It ensures remote database states accurately reflect application behavior without manual inspection.

What does E2E testing for OAuth authentication in MCP servers involve?

E2E testing for OAuth in MCP servers ensures that OAuth principals and scopes are correctly maintained across callServerTool executions and app interactions. It validates security boundaries within the Model Context Protocol during live iCalendar data operations.

Can I use the MCP inspector to validate D1 database persistence for iCalendar data?

Yes, the MCP inspector performs live verification of remote D1 database states for iCalendar data. Combined with the Wrangler CLI, it confirms that CalDAV tool calls correctly persist data and that the MCP App UI reflects these changes accurately.

Do I need Wrangler CLI to test remote D1 database states in MCP apps?

Yes, Wrangler CLI is required to perform live verification of remote D1 database states. It works alongside the Model Context Protocol inspector to validate that CalDAV integrations correctly update database records during end-to-end testing scenarios.

What is the best way to test MCP server responses and UI card interactions together?

Multi-layer validation is the best way to test MCP server responses and UI card interactions together. It verifies tool contracts, UI behavior, and raw D1 database state in a single structured framework to ensure CalDAV integrations function correctly.