Skip to content

Commit 8b6d9ce

Browse files
committed
shoring up the repo for release
1 parent 5761301 commit 8b6d9ce

File tree

5 files changed

+134
-4
lines changed

5 files changed

+134
-4
lines changed

.gitignore

+1
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ plan.md
77
plan_pip.md
88
SERVER_COMPATIBILITY.md
99
mcp_testing/server_configs/*
10+
opensource_plan.md
1011

1112
# Virtual environment
1213
.venv/

CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Please be respectful and considerate of others when contributing to this project
1212

1313
If you find a bug or have a suggestion for improvement:
1414

15-
1. Check if the issue already exists in the [GitHub Issues](https://github.com/your-username/mcp-protocol-validator/issues)
15+
1. Check if the issue already exists in the [GitHub Issues](https://github.com/Janix-ai/mcp-protocol-validator/issues)
1616
2. If not, create a new issue using the appropriate template
1717
3. Provide as much detail as possible, including steps to reproduce, expected behavior, and your environment
1818

README.md

+81
Original file line numberDiff line numberDiff line change
@@ -303,6 +303,87 @@ pytest
303303
pytest mcp_testing/tests/base_protocol/
304304
```
305305

306+
## Quick Start
307+
308+
### Quickest Way to Test a Server
309+
310+
For quick validation of MCP server implementations, you can use these minimal testing commands:
311+
312+
#### For STDIO Servers:
313+
314+
```bash
315+
# Basic interaction - simplest test to verify server works
316+
python -m mcp_testing.scripts.basic_interaction --server-command "./minimal_mcp_server/minimal_mcp_server.py"
317+
318+
# Run a full compliance test
319+
python -m mcp_testing.scripts.compliance_report --server-command "./minimal_mcp_server/minimal_mcp_server.py" --protocol-version 2025-03-26
320+
```
321+
322+
#### For HTTP Servers:
323+
324+
```bash
325+
# Quick HTTP test
326+
python -m mcp_testing.scripts.http_test --server-url http://localhost:8000/mcp --protocol-version 2025-03-26
327+
328+
# Simple connectivity check
329+
python minimal_http_server/check_server.py http://localhost:8000/mcp
330+
```
331+
332+
### Advanced Testing Options
333+
334+
For more comprehensive testing with detailed options:
335+
336+
#### STDIO Testing:
337+
338+
```bash
339+
# Generate a detailed compliance report
340+
python -m mcp_testing.scripts.compliance_report \
341+
--server-command "./minimal_mcp_server/minimal_mcp_server.py" \
342+
--protocol-version 2025-03-26 \
343+
--output-dir "./reports"
344+
345+
# Test with timeout settings for better stability
346+
python -m mcp_testing.scripts.compliance_report \
347+
--server-command "./minimal_mcp_server/minimal_mcp_server.py" \
348+
--test-timeout 30 \
349+
--tools-timeout 15
350+
351+
# Test only tool functionality
352+
python -m mcp_testing.scripts.compliance_report \
353+
--server-command "./minimal_mcp_server/minimal_mcp_server.py" \
354+
--test-mode tools
355+
```
356+
357+
#### HTTP Testing:
358+
359+
```bash
360+
# Comprehensive HTTP test with debug output
361+
python -m mcp_testing.scripts.http_test \
362+
--server-url http://localhost:8000/mcp \
363+
--protocol-version 2025-03-26 \
364+
--debug
365+
366+
# Generate an HTTP test report
367+
python -m mcp_testing.scripts.http_test \
368+
--server-url http://localhost:8000/mcp \
369+
--protocol-version 2025-03-26 \
370+
--output-dir "./reports"
371+
```
372+
373+
For testing pip-installed servers, ensure you're in the same virtual environment:
374+
375+
```bash
376+
# Install server and testing framework in the same environment
377+
pip install mcp-server-fetch sseclient-py==1.7.2
378+
379+
# Test a pip-installed server
380+
python -m mcp_testing.scripts.basic_interaction \
381+
--server-command "python -m mcp_server_fetch" \
382+
--protocol-version 2024-11-05
383+
```
384+
385+
See the [Testing Pip-Installed MCP Servers](#testing-pip-installed-mcp-servers) section for more details.
386+
306387
## License
307388

308389
SPDX-License-Identifier: AGPL-3.0-or-later

SECURITY.md

+48
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
We currently provide security updates for the following versions of the MCP Protocol Validator:
6+
7+
| Version | Supported |
8+
| ------- | ------------------ |
9+
| 1.0.x | :white_check_mark: |
10+
11+
## Reporting a Vulnerability
12+
13+
The MCP Protocol Validator team takes security seriously. If you believe you've found a security vulnerability, please follow these steps:
14+
15+
1. **Do not disclose the vulnerability publicly**
16+
2. **Email us directly** at [[email protected]](mailto:[email protected]) with details about the vulnerability
17+
3. Include the following information in your report:
18+
- Type of issue
19+
- Full paths of source file(s) related to the issue
20+
- Location of the affected source code
21+
- Any special configuration required to reproduce the issue
22+
- Step-by-step instructions to reproduce the issue
23+
- Proof-of-concept or exploit code (if possible)
24+
- Impact of the issue, including how an attacker might exploit it
25+
26+
## Response Process
27+
28+
We are committed to the following response process:
29+
30+
- We will acknowledge receipt of your vulnerability report within 3 business days
31+
- We will provide an initial assessment of the report within 10 business days
32+
- We will keep you informed of our progress throughout the process
33+
- We will notify you when the vulnerability has been fixed
34+
35+
## Security Best Practices
36+
37+
When using the MCP Protocol Validator in your own projects, we recommend the following security best practices:
38+
39+
1. **Keep your dependencies updated**: Regularly update the MCP Protocol Validator and its dependencies to benefit from security patches
40+
2. **Use caution with file operations**: When using the file operation tools in the MCP servers, be aware of potential security implications in your specific environment
41+
3. **Control network access**: When using the HTTP MCP server, ensure it's only accessible to trusted clients or over secure networks
42+
43+
## Responsible Disclosure
44+
45+
We follow responsible disclosure principles. After a fix has been developed and released, we encourage security researchers to disclose the vulnerability in a responsible manner, giving users time to update their installations. We will credit security researchers who report valid vulnerabilities and work with us through the entire process.
46+
47+
48+
Thank you for helping to keep the MCP Protocol Validator and its users secure!

setup.py

+3-3
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,13 @@
77
name="mcp-protocol-validator",
88
version="1.0.0",
99
author="Scott Wilcox",
10-
author_email="[email protected]", # Replace with actual email
10+
author_email="[email protected]", # Updated email
1111
description="Testing framework and reference implementations for the Model Conversation Protocol (MCP)",
1212
long_description=long_description,
1313
long_description_content_type="text/markdown",
14-
url="https://github.com/scottwilcox/mcp-protocol-validator",
14+
url="https://github.com/Janix-ai/mcp-protocol-validator",
1515
project_urls={
16-
"Bug Tracker": "https://github.com/scottwilcox/mcp-protocol-validator/issues",
16+
"Bug Tracker": "https://github.com/Janix-ai/mcp-protocol-validator/issues",
1717
},
1818
classifiers=[
1919
"Programming Language :: Python :: 3",

0 commit comments

Comments
 (0)