[UC-MCP] Complete MCP server: JSON-RPC 2.0 protocol → Implemented TOO…

[kupakwash]

RAG-to-MCP — Submission PR
Name: Kupakwashe T Mapuranga
City / Group: Pune
Date: April 17, 2026
AI tool(s) used: GitHub Copilot

Submission Checklist
uc-0a/agents.md — present and updated
uc-0a/skills.md — present and updated
uc-0a/classifier.py — runs without crash
uc-0a/results_pune.csv — output present
uc-rag/agents.md — present and updated
uc-rag/skills.md — present and updated
uc-rag/rag_server.py — not the stub, my implementation
uc-mcp/agents.md — present and updated
uc-mcp/skills.md — present and updated
uc-mcp/mcp_server.py — passes at least one test_client.py test
3+ commits with meaningful messages, one per UC
UC-0A — Complaint Classifier
Failure mode: Keyword matching missed edge cases
Enforcement rule: Severity keywords (injury/child/school/hospital) → Urgent
Commit: [UC-0A] Complete classifier: keyword-based severity detection
UC-RAG — RAG Server
Failure mode: Threshold too strict (0.6), no results
Chunking: Fixed-size 500 chars with overlap
Enforcement rule: "Only answer using retrieved context"
Commit: [UC-RAG] Complete RAG server: ChromaDB integration with threshold 0.3
UC-MCP — MCP Server
Tool description: "Answers questions about CMC HR Leave Policy, IT Acceptable Use Policy, and Finance Reimbursement Policy only..."
test_client.py result: All tests pass (tool discovery, in-scope, out-of-scope)
Commit: [UC-MCP] Complete MCP server: JSON-RPC 2.0 protocol
GitHub PR Link: https://github.com/kupakwash/rag-to-mcp/pull/new/participant/kupakwashe-pune

[github-actions]

Hi there, participant! Thanks for joining our RAG-to-MCP Workshop!

We're reviewing your PR for the 3 Use Cases (UC-0A, UC-RAG, UC-MCP). Once your submission is validated and merged, you'll be awarded your completion badge!

Next Steps:

• Make sure all 3 UCs are finished.
• Ensure your commit messages match the required format.
• Fill out every section of the PR template.
• Good luck!