MCPSense
Related Servers
Alternatives to MCPSense
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides code intelligence by indexing source code into SQLite and offering MCP tools for symbol search, flow tracing, and context retrieval to assist with code navigation and understanding.-
- AlicenseNot gradedqualityAmaintenanceA desktop launcher and local MCP workspace server that enables ChatGPT and other MCP clients to securely read, edit, search, run commands, and show changes in selected local project folders.1MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP runtime for macOS and Windows that enables ChatGPT to read, edit, search, run tests, and capture screenshots in your local project folder while keeping your source code on your machine.164-
- AlicenseBqualityCmaintenanceMCP server for searching, browsing, and analyzing decompiled Minecraft source code locally. Supports symbol lookup, text search, reference lookup, and lightweight RAG.11Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for local codebase analysis, enabling semantic code search, impact analysis, and pack-scoped retrieval with cited file:line results.81 PyPI1Apache 2.0
- AlicenseBqualityDmaintenanceProvides comprehensive access to MCP documentation through structured guides, full-text search, and interactive development workflows for building servers and clients.343 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: status reports environment/version, checks enumerates scanner checks, discover locates config paths, scan performs the inspection, and verify compares two reports. The boundaries are explicit and reinforced by descriptions noting what each does not do (e.g. discover returns paths only, does not read contents). No two tools appear to do the same thing.
All five tools use the same mcpsense_ prefix with a single lowercase verb/noun convention (status, checks, discover, scan, verify). The pattern is fully predictable with no mixing of styles.
Five tools is well-scoped for a scanner: a meta/status tool, two discovery/informational tools, the core scan, and verification. Each earns its place with no redundancy or filler.
The surface covers the core lifecycle: environment check, check registry, path discovery, scanning, and report verification. Minor gaps exist around baseline creation/management (scan explicitly avoids baseline writes) and explicit report export, but agents can work around these.