mcp-server-suite
Related Servers
Alternatives to mcp-server-suite
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables AI agents to safely interact with GitHub, query Postgres read-only, check deployment status, and search/read files within an allowlisted sandbox—all with dry-run writes and SQL/path safety gates.8-
- FlicenseNot gradedqualityBmaintenanceEnables read-only discovery and retrieval of allowlisted catalog datasets with host-assigned roles, strict tool validation, SQLite read-only enforcement, and audit hash chaining. It supports querying bounded daily aggregates while preventing arbitrary SQL, file access, shell commands, credential use, or role escalation.-
- AlicenseAqualityBmaintenanceEnables coding agents to safely investigate PostgreSQL runtime state through bounded, read-oriented MCP tools for row-and-foreign-key neighborhood inspection, schema and statistics lookup, and table listing, with truncation, redaction, timeouts, and audit logging.437 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI models to securely analyze SQLite datasets and read local text documents through a local stdio interface. It provides read-only querying, schema discovery, pagination, and timeout protections to prevent data leaks or destructive changes.MIT
- AlicenseAqualityCmaintenanceEnables read-only document retrieval and SQLite exploration through tools over stdio, enforcing a safety gate before SQL execution.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to inspect and query a shared PostgreSQL database safely, running one read-only statement per call with bounded rows and timeouts. Write tools appear only when explicitly enabled, and the database connection is supplied through the environment rather than command-line arguments.146 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose (host health snapshot) is stated clearly and unambiguously.
The single name system_metrics is snake_case, descriptive, and resource-oriented, with no competing conventions to clash with. Consistency cannot be violated with one tool, and the name reads predictably.
A one-tool server is too thin for a general 'mcp-server-suite' scope; everything is crammed into a single snapshot call. It is well-scoped for what it does, but the surface is minimal.
CPU, load, core count, memory, and optional disk cover the core host-health snapshot, but there is no history/time-series, network, process, uptime, or multi-host coverage. Agents needing anything beyond a point-in-time sample hit a dead end.