A
licenseA
qualityC
maintenanceProvides tools for managing tasks, searching docs, and running a heuristic quality gate to check agent output for common issues before human review.
6
MIT
QVAC-MCP
Related Servers
Alternatives to QVAC-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides AI agents with version-pinned NVIDIA CUDA-Q documentation, API reference, and runnable examples via MCP, using offline SQLite full-text search. It resolves docs to match the installed cudaq package to avoid version skew.527 PyPI1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides tools to slice documentation by headers, append git-verified session entries, and retrieve the current phase to manage context for AI coding agents.MIT
- AlicenseBqualityCmaintenanceProvides read-only RAG retrieval, document access, source auditing, status, and health checks for CUMCM optimization and decision modeling contexts.6Apache 2.0
- AlicenseAqualityDmaintenanceProvides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.715 npm1MIT
- FlicenseNot gradedqualityDmaintenanceProvides tools for ingesting documents into a local vector database and retrieving relevant information via semantic search, enabling retrieval-augmented generation for MCP clients.6-
TDQS
B3.4/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a clearly distinct role: qvac_index/fetch/search form a browse-retrieve-filter flow, track_brief/track_detail are explicitly tiered summaries, and the remaining tools (rules, compliance, planning, feedback) target separate workflow stages. Even the two discovery-ish tools (qvac_index and qvac_search) are differentiated by map vs. keyword filter.
Naming Consistency3/5
All names use snake_case and are readable, but they follow multiple conventions: qvac_* for one group, track_* for another, hackathon_* for another, and a lone judge_feedback. There is no uniform verb_noun pattern, though the prefix grouping helps orient an agent.
Tool Count5/5
Nine tools is well within the ideal 3-15 range and each tool earns its place. The count covers knowledge retrieval, track details, hackathon rules, compliance checking, planning, and self-assessment without redundancy or bloat.
Completeness5/5
The surface is complete for its apparent purpose: an agent can discover QVAC resources, fetch content, search, get track summaries/details, access rules, verify compliance, generate a plan, and run a final judging self-evaluation. There are no dead ends, and the tool chain supports a full hackathon workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues