stackhint
Related Servers
Alternatives to stackhint
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect and diagnose their own MCP setup by exposing read-only tools that audit configured servers, report which coding agents have configs, surface misplaced or duplicated registrations, and list curated preset packs. It also powers CLI workflows for checking handshake, tool lint, and tool-surface quality scores of any stdio server.14 npmMIT
- AlicenseNot gradedqualityAmaintenancePrivacy-first, read-only repo intelligence for AI coding agents: scans local codebases and recommends MCP servers, repos, and research without sending data to the cloud.1Apache 2.0

wellwornofficial
FlicenseNot gradedqualityDmaintenanceProvides coding agents with verified recommendations, version-specific breakage traps, design systems, and installable skills over MCP, enabling safer stack and dependency decisions without requiring an API key.1-- AlicenseNot gradedqualityAmaintenanceLocal repository intelligence MCP server that builds a reusable graph of code structure for AI coding agents, providing 34 network-free tools for understanding, searching, and analyzing repositories without data leaving the machine.49 npmMIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.33 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and other MCP clients to interrogate a repository — or a frontend and backend pair — returning a single JSON document of findings such as which calls reach which routes, what is dead, and where to refactor first. Exposes tools like analyze_repo, cross_repo, check_endpoint, and check_coverage, along with contract resources for authoring adapters and rule packs, entirely over local stdio with no network access.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: recommendation, keyword search, per-entry explanation, environment status, and install preview. While search and recommend both surface tools, their inputs and outputs are distinct enough to avoid meaningful misselection.
Most names follow a verb_noun pattern in snake_case: recommend_tools, explain_tool, search_tools, plan_install. tooling_status is the one deviation, using a noun phrase rather than a verb, but it is still readable and consistent in casing.
Five tools is well-scoped for a local tooling advisor: search, recommend, explain, plan, and status each earn their place. The surface is neither thin nor bloated.
The set covers discovery, evaluation, install planning, and configuration status, which are the core workflows for an advisory MCP server. It intentionally omits applying installs or managing removal/update operations, which is a minor gap but consistent with its safety-focused design.