cint MCP Server
Related Servers
Alternatives to cint MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables IDEs and coding agents to perform fast deterministic repository queries, symbol and dependency graph navigation, persistent memory recall, skill loading, security scanning, git inspection, and model routing with minimal token usage.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform hybrid code search, get explanations, analyze relations and impacts, retrieve context packs, and generate documentation across ~45 languages via 17 MCP tools, all powered by a local vector database and LLM.2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides local-first repository architecture analysis with file-level proof, enabling agents to map codebases, locate implementations, trace call paths, and assess change impact with deterministic evidence.4 npm7MIT
- AlicenseNot gradedqualityFmaintenanceEnables local-first codebase intelligence, allowing chat, search, and audit operations on any repository with file:line citations, and supports offline deterministic modes without an LLM.9 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to inspect files, search text, compare directories, read symbols, and apply structured edits against large codebases through bounded, local-first MCP tools.4Apache 2.0
- AlicenseBqualityBmaintenanceEnables coding agents to establish exact-release library identity, search provenance-tracked API, docs, example, source, and release evidence, compare releases, and test proposed invocations in isolated capsules for Rust and Python dependency environments.9Apache 2.0
TDQS
Scored across 8 tools
Each tool targets a distinct action on a distinct resource: check (compile only), eval (compile+run), test (run test blocks), lookup_diagnostic (explain codes), search_docs vs get_doc (find vs retrieve), get_recipe, list_curriculum. The descriptions explicitly disambiguate the easily confused compile/run/test trio and the search/get doc pair.
All tools share the cint_ prefix and snake_case, and most follow verb_noun (lookup_diagnostic, get_recipe, list_curriculum, search_docs, get_doc). The bare verbs check, eval, and test deviate slightly from the pattern but remain readable and unambiguous.
Eight tools is well-scoped for a language-tooling server: execution (check/eval/test), documentation discovery (search_docs/get_doc), diagnostics explanation, and curated assets (recipes/curriculum). Each tool earns its place with no filler.
The surface covers the full core workflow of compiling, running, testing, diagnosing, and looking up docs/recipes/lessons. Minor gaps exist (no version/environment info tool, no formatter or project scaffolding), but agents can work around these.