feat(mcp): implement standalone MCP test harness binary

- Create self-contained binary independent of CodePrism codebase
- Support multiple transport types: stdio, HTTP, WebSocket
- Universal MCP server configuration system
- Comprehensive validation engine with pattern matching
- Performance benchmarking and monitoring capabilities
- Cross-platform build scripts and Docker support
- Template system for common MCP server types
- Command-line interface with validation, testing, and discovery

Key Features:
- Zero CodePrism dependencies, pure MCP testing
- Works with any MCP server implementation
- Built-in configuration templates (filesystem, database, API, custom)
- Rich output formats (table, JSON, YAML)
- Automatic server discovery and profiling
- Comprehensive protocol compliance validation
- One-command installation via cargo install

closes #102

Author: milliondreams

mcp-test-harness-standalone/Cargo.toml

@@ -0,0 +1,61 @@
+[package]
+name = "mcp-test-harness"
+version = "0.1.0"
+edition = "2021"
+description = "Standalone test harness for Model Context Protocol (MCP) servers"
+license = "MIT OR Apache-2.0"
+repository = "https://github.com/rustic-ai/codeprism"
+keywords = ["mcp", "testing", "protocol", "ai", "llm"]
+categories = ["development-tools::testing", "command-line-utilities"]
+authors = ["CodePrism Team <team@codeprism.ai>"]
+readme = "README.md"
+
+[[bin]]
+name = "mcp-test-harness"
+path = "src/main.rs"
+
+[dependencies]
+# Core dependencies - minimal and focused
+tokio = { version = "1.0", features = ["full"] }
+serde = { version = "1.0", features = ["derive"] }
+serde_json = "1.0"
+serde_yaml = "0.9"
+clap = { version = "4.0", features = ["derive"] }
+anyhow = "1.0"
+thiserror = "1.0"
+tracing = "0.1"
+tracing-subscriber = { version = "0.3", features = ["env-filter"] }
+chrono = { version = "0.4", features = ["serde"] }
+
+# HTTP and JSON-RPC for MCP communication
+reqwest = { version = "0.12", features = ["json"] }
+jsonrpc-core = "18.0"
+
+# Process management for server lifecycle
+process_control = "4.0"
+which = "6.0"
+
+# Configuration and validation
+jsonschema = "0.18"
+uuid = { version = "1.0", features = ["v4"] }
+
+# Performance and monitoring
+instant = "0.1"
+
+# Optional features for advanced functionality
+regex = "1.0"
+walkdir = "2.0"
+
+[dev-dependencies]
+tempfile = "3.0"
+assert_cmd = "2.0"
+predicates = "3.0"
+
+[features]
+default = ["performance-monitoring"]
+performance-monitoring = []
+docker-support = []
+extended-validation = []
+
+[workspace]
+# This is a standalone package, not part of the parent workspace

mcp-test-harness-standalone/README.md

@@ -0,0 +1,276 @@
+# MCP Test Harness
+
+A universal testing tool for Model Context Protocol (MCP) servers. Test any MCP server implementation for protocol compliance, performance, and reliability.
+
+[![Crate](https://img.shields.io/crates/v/mcp-test-harness.svg)](https://crates.io/crates/mcp-test-harness)
+[![Documentation](https://docs.rs/mcp-test-harness/badge.svg)](https://docs.rs/mcp-test-harness)
+[![License](https://img.shields.io/badge/license-MIT%2FApache--2.0-blue.svg)](LICENSE)
+
+## Features
+
+- 🔧 **Universal MCP Server Testing** - Works with any MCP server implementation
+- 🚀 **Multiple Transport Support** - stdio, HTTP, WebSocket
+- 📊 **Performance Monitoring** - Built-in benchmarking and regression detection
+- 🛡️ **Protocol Compliance** - Comprehensive MCP protocol validation
+- 🐳 **Docker Ready** - Containerized testing for CI/CD pipelines
+- 📋 **Flexible Configuration** - YAML/JSON configuration with templates
+- �� **Auto-Discovery** - Automatic MCP server detection
+- 📈 **Rich Reporting** - Table, JSON, YAML output formats
+
+## Quick Start
+
+### Installation
+
+```bash
+# Install from crates.io
+cargo install mcp-test-harness
+
+# Or build from source
+git clone https://github.com/rustic-ai/codeprism
+cd prism/mcp-test-harness-standalone
+cargo install --path .
+```
+
+### Basic Usage
+
+```bash
+# Test a stdio MCP server
+mcp-test-harness test \
+  --config configs/examples/basic-mcp-server.yaml \
+  --server-cmd "node my-mcp-server.js"
+
+# Test an HTTP MCP server
+mcp-test-harness test \
+  --config my-http-server-config.yaml
+
+# Generate a configuration template
+mcp-test-harness template --server-type filesystem --output my-config.yaml
+
+# Discover running MCP servers
+mcp-test-harness discover --port-range "3000-3010"
+
+# Run performance benchmarks
+mcp-test-harness benchmark \
+  --config my-config.yaml \
+  --iterations 1000 \
+  --duration 60
+```
+
+### Docker Usage
+
+```bash
+# Pull the image
+docker pull mcp-test-harness:latest
+
+# Run tests with Docker
+docker run --rm -v $(pwd)/configs:/configs \
+  mcp-test-harness test --config /configs/my-server.yaml
+
+# Use in CI/CD
+docker run --rm -v $(pwd):/workspace -w /workspace \
+  mcp-test-harness test --config test-config.yaml --output json
+```
+
+## Configuration
+
+### Basic Configuration Structure
+
+```yaml
+global:
+  max_global_concurrency: 2
+  timeout_seconds: 30
+  fail_fast: false
+
+server:
+  transport: "stdio"  # or "http", "websocket"
+  command: "node server.js"
+  args: ["--port", "3000"]
+  working_dir: "/path/to/server"
+  env:
+    NODE_ENV: "test"
+
+performance:
+  enable_monitoring: true
+  baseline_storage_path: "baselines/"
+  regression_detection:
+    warning_threshold_percent: 25.0
+    error_threshold_percent: 50.0
+
+test_suites:
+  - name: "MCP Protocol Compliance"
+    test_cases:
+      - id: "initialize"
+        tool_name: "initialize"
+        enabled: true
+        input_params:
+          protocolVersion: "2024-11-05"
+        expected:
+          patterns:
+            - key: "protocolVersion"
+              validation: { type: "exists" }
+              required: true
+```
+
+### Server Types
+
+#### stdio Server
+```yaml
+server:
+  transport: "stdio"
+  command: "node"
+  args: ["server.js"]
+```
+
+#### HTTP Server
+```yaml
+server:
+  transport: "http"
+  url: "http://localhost:3000"
+  connection_timeout: 10
+```
+
+#### WebSocket Server
+```yaml
+server:
+  transport: "websocket"
+  url: "ws://localhost:3000"
+```
+
+## Validation Patterns
+
+The test harness supports comprehensive response validation:
+
+```yaml
+expected:
+  patterns:
+    # Check if field exists
+    - key: "status"
+      validation: { type: "exists" }
+      required: true
+    
+    # Check exact value
+    - key: "status"
+      validation: { type: "equals", value: "ok" }
+      required: true
+    
+    # Check numeric range
+    - key: "count"
+      validation: { type: "range", min: 1.0, max: 100.0 }
+      required: true
+    
+    # Check array structure
+    - key: "items"
+      validation: { type: "array" }
+      required: true
+    
+    # Check array length
+    - key: "items"
+      validation: { type: "array_min_length", min_length: 1 }
+      required: true
+    
+    # Check boolean value
+    - key: "enabled"
+      validation: { type: "boolean", value: true }
+      required: true
+```
+
+## Performance Testing
+
+### Basic Performance Requirements
+
+```yaml
+performance_requirements:
+  max_execution_time_ms: 5000
+  max_memory_usage_mb: 64
+```
+
+### Benchmarking
+
+```bash
+# Run benchmarks
+mcp-test-harness benchmark \
+  --config server-config.yaml \
+  --iterations 1000 \
+  --duration 60 \
+  --output json > benchmark-results.json
+```
+
+## Templates
+
+Generate configuration templates for common server types:
+
+```bash
+# Filesystem server template
+mcp-test-harness template --server-type filesystem --output fs-config.yaml
+
+# Database server template
+mcp-test-harness template --server-type database --output db-config.yaml
+
+# API wrapper template
+mcp-test-harness template --server-type api --output api-config.yaml
+
+# List available templates
+mcp-test-harness list
+```
+
+## CI/CD Integration
+
+### GitHub Actions
+
+```yaml
+name: MCP Server Tests
+on: [push, pull_request]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Test MCP Server
+        run: |
+          docker run --rm -v $(pwd):/workspace -w /workspace \
+            mcp-test-harness test \
+            --config .github/mcp-test-config.yaml \
+            --output json > test-results.json
+      - name: Upload Results
+        uses: actions/upload-artifact@v3
+        with:
+          name: test-results
+          path: test-results.json
+```
+
+### GitLab CI
+
+```yaml
+mcp-tests:
+  image: mcp-test-harness:latest
+  script:
+    - mcp-test-harness test --config ci-config.yaml --output junit > results.xml
+  artifacts:
+    reports:
+      junit: results.xml
+```
+
+## Contributing
+
+1. Fork the repository
+2. Create your feature branch (`git checkout -b feature/amazing-feature`)
+3. Commit your changes (`git commit -m 'Add amazing feature'`)
+4. Push to the branch (`git push origin feature/amazing-feature`)
+5. Open a Pull Request
+
+## License
+
+This project is licensed under either of
+
+* Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
+* MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)
+
+at your option.
+
+## Support
+
+- 📖 [Documentation](https://docs.rs/mcp-test-harness)
+- 🐛 [Issue Tracker](https://github.com/rustic-ai/codeprism/issues)
+- 💬 [Discussions](https://github.com/rustic-ai/codeprism/discussions)
+- �� [Email Support](mailto:team@codeprism.ai)